Re: [RFC PATCH] physmem: Do not allow unprivileged device map privileged memory

2021-09-07 Thread Peter Maydell
On Fri, 3 Sept 2021 at 16:38, Philippe Mathieu-Daudé wrote: > > Since commits cc05c43ad94..42874d3a8c6 ("memory: Define API for > MemoryRegionOps to take attrs and return status") the Memory API > returns a zero (MEMTX_OK) response meaning success, anything else > indicating a failure. > > In comm

Re: [RFC PATCH] physmem: Do not allow unprivileged device map privileged memory

2021-09-03 Thread Peter Xu
On Fri, Sep 03, 2021 at 05:38:20PM +0200, Philippe Mathieu-Daudé wrote: > Since commits cc05c43ad94..42874d3a8c6 ("memory: Define API for > MemoryRegionOps to take attrs and return status") the Memory API > returns a zero (MEMTX_OK) response meaning success, anything else > indicating a failure. >

[RFC PATCH] physmem: Do not allow unprivileged device map privileged memory

2021-09-03 Thread Philippe Mathieu-Daudé
Since commits cc05c43ad94..42874d3a8c6 ("memory: Define API for MemoryRegionOps to take attrs and return status") the Memory API returns a zero (MEMTX_OK) response meaning success, anything else indicating a failure. In commits c874dc4f5e8..2f7b009c2e7 ("Make address_space_map() take a MemTxAttrs