Re: [PATCH 2/2] riscv: Support CONFIG_STRICT_DEVMEM

2020-07-09 Thread Zong Li
On Fri, Jul 10, 2020 at 4:08 AM Palmer Dabbelt wrote: > > On Tue, 16 Jun 2020 00:45:47 PDT (-0700), zong...@sifive.com wrote: > > Implement the 'devmem_is_allowed()' interface for RISC-V, like some of > > other architectures have done. It will be called from range_is_allowed() > > when userpsace a

Re: [PATCH 2/2] riscv: Support CONFIG_STRICT_DEVMEM

2020-07-09 Thread Palmer Dabbelt
On Tue, 16 Jun 2020 00:45:47 PDT (-0700), zong...@sifive.com wrote: Implement the 'devmem_is_allowed()' interface for RISC-V, like some of other architectures have done. It will be called from range_is_allowed() when userpsace attempts to access /dev/mem. In fact, it's exactly the same (down to

Re: [PATCH 2/2] riscv: Support CONFIG_STRICT_DEVMEM

2020-06-16 Thread Zong Li
On Wed, Jun 17, 2020 at 1:28 PM Nick Kossifidis wrote: > > Στις 2020-06-17 04:56, Zong Li έγραψε: > > On Tue, Jun 16, 2020 at 8:27 PM Nick Kossifidis > > wrote: > >> > >> Στις 2020-06-16 10:45, Zong Li έγραψε: > >> > Implement the 'devmem_is_allowed()' interface for RISC-V, like some of > >> > ot

Re: [PATCH 2/2] riscv: Support CONFIG_STRICT_DEVMEM

2020-06-16 Thread Nick Kossifidis
Στις 2020-06-17 04:56, Zong Li έγραψε: On Tue, Jun 16, 2020 at 8:27 PM Nick Kossifidis wrote: Στις 2020-06-16 10:45, Zong Li έγραψε: > Implement the 'devmem_is_allowed()' interface for RISC-V, like some of > other architectures have done. It will be called from > range_is_allowed() > when user

Re: [PATCH 2/2] riscv: Support CONFIG_STRICT_DEVMEM

2020-06-16 Thread Zong Li
On Tue, Jun 16, 2020 at 8:27 PM Nick Kossifidis wrote: > > Στις 2020-06-16 10:45, Zong Li έγραψε: > > Implement the 'devmem_is_allowed()' interface for RISC-V, like some of > > other architectures have done. It will be called from > > range_is_allowed() > > when userpsace attempts to access /dev/m

Re: [PATCH 2/2] riscv: Support CONFIG_STRICT_DEVMEM

2020-06-16 Thread Nick Kossifidis
Στις 2020-06-16 10:45, Zong Li έγραψε: Implement the 'devmem_is_allowed()' interface for RISC-V, like some of other architectures have done. It will be called from range_is_allowed() when userpsace attempts to access /dev/mem. Access to exclusive IOMEM and kernel RAM is denied unless CONFIG_ST