[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2103222037450.21463@angie.orcam.me.uk>
Date: Mon, 22 Mar 2021 20:39:07 +0100 (CET)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Tiezhu Yang <yangtiezhu@...ngson.cn>
cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
linux-mips@...r.kernel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org, Xuefeng Li <lixuefeng@...ngson.cn>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v2] MIPS/bpf: Enable bpf_probe_read{, str}() on MIPS
again
On Mon, 22 Mar 2021, Tiezhu Yang wrote:
> > > --- a/arch/mips/Kconfig
> > > +++ b/arch/mips/Kconfig
> > > @@ -6,6 +6,7 @@ config MIPS
> > > select ARCH_BINFMT_ELF_STATE if MIPS_FP_SUPPORT
> > > select ARCH_HAS_FORTIFY_SOURCE
> > > select ARCH_HAS_KCOV
> > > + select ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE
> > Hmm, documentation on ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE seems rather
> > scarce, but based on my guess shouldn't this be "if !EVA"?
>
> I do not quite know what the effect if MIPS EVA (Enhanced Virtual Addressing)
> is set, I saw that ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE should be restricted
> to archs with non-overlapping address ranges.
>
> I wonder whether MIPS EVA will generate overlapping address ranges?
The architecture specification has it all.
Maciej
Powered by blists - more mailing lists