Re: [PATCH v14 04/10] set_memory: allow querying whether set_direct_map_*() is actually enabled

2020-12-06 Thread Mike Rapoport
On Thu, Dec 03, 2020 at 03:36:10PM -0800, Andrew Morton wrote: > On Thu, 3 Dec 2020 08:29:43 +0200 Mike Rapoport wrote: > > > From: Mike Rapoport > > > > On arm64, set_direct_map_*() functions may return 0 without actually > > changing the linear map. This behaviour can be controlled using

Re: [PATCH v14 04/10] set_memory: allow querying whether set_direct_map_*() is actually enabled

2020-12-03 Thread Andrew Morton
On Thu, 3 Dec 2020 08:29:43 +0200 Mike Rapoport wrote: > From: Mike Rapoport > > On arm64, set_direct_map_*() functions may return 0 without actually > changing the linear map. This behaviour can be controlled using kernel > parameters, so we need a way to determine at runtime whether calls

[PATCH v14 04/10] set_memory: allow querying whether set_direct_map_*() is actually enabled

2020-12-02 Thread Mike Rapoport
From: Mike Rapoport On arm64, set_direct_map_*() functions may return 0 without actually changing the linear map. This behaviour can be controlled using kernel parameters, so we need a way to determine at runtime whether calls to set_direct_map_invalid_noflush() and