lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 Sep 2021 17:35:52 +0530 From: Anup Patel <anup@...infault.org> To: Alexandre Ghiti <alexandre.ghiti@...onical.com> Cc: Nick Kossifidis <mick@....forth.gr>, Philipp Tomsich <philipp.tomsich@...ll.eu>, Guo Ren <guoren@...nel.org>, Anup Patel <anup.patel@....com>, Atish Patra <atish.patra@....com>, Palmer Dabbelt <palmerdabbelt@...gle.com>, Christoph Müllner <christoph.muellner@...ll.eu>, Christoph Hellwig <hch@....de>, liush <liush@...winnertech.com>, wefu@...hat.com, Wei Wu (吴伟) <lazyparser@...il.com>, Drew Fustini <drew@...gleboard.org>, linux-riscv <linux-riscv@...ts.infradead.org>, "linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>, taiten.peng@...onical.com, Aniket Ponkshe <aniket.ponkshe@...onical.com>, Heinrich Schuchardt <heinrich.schuchardt@...onical.com>, Gordan Markus <gordan.markus@...onical.com>, Guo Ren <guoren@...ux.alibaba.com>, Arnd Bergmann <arnd@...db.de>, Chen-Yu Tsai <wens@...e.org>, Maxime Ripard <maxime@...no.tech>, Daniel Lustig <dlustig@...dia.com>, Greg Favor <gfavor@...tanamicro.com>, Andrea Mondelli <andrea.mondelli@...wei.com>, Jonathan Behrens <behrensj@....edu>, Xinhaoqu <xinhaoqu@...wei.com>, Bill Huffman <huffman@...ence.com>, Allen Baum <allen.baum@...erantotech.com>, Josh Scheid <jscheid@...tanamicro.com>, Richard Trauben <rtrauben@...il.com> Subject: Re: [PATCH] riscv: Add RISC-V svpbmt extension On Thu, Sep 23, 2021 at 5:21 PM Alexandre Ghiti <alexandre.ghiti@...onical.com> wrote: > > On Thu, Sep 23, 2021 at 12:11 PM Nick Kossifidis <mick@....forth.gr> wrote: > > > > Στις 2021-09-23 13:04, Philipp Tomsich έγραψε: > > > > > > How if we expand this to a mmu subnode in cpu@x and add a booleans for > > > adornments like svnapot and svpbmt? > > > The older mmu-type could then treated to indicate a mmu w/o any > > > adornments specified. I am aware that this generates an additional > > > parsing-path that will be maintained, but it will allow future > > > properties to be grouped. > > > > > > cpu@0 { > > > ... > > > mmu { > > > type = "riscv,sv39"; > > > supports-svpbmt; > > > } > > > ... > > > } > > > > I was about to propose the same thing, we can do this now without > > breaking backwards compatibility, we don't really use mmu-type property > > at this point, we are either sv39 or nommu. > > Indeed, this property is only informative and not useful since we can > directly "ask" the hw what it supports (cf sv48 patchset). And it > cannot actually be used to force a certain svXX since reading the > device tree happens way too late in the boot process (I have this > issue with my sv48 patchset where I used to read the device tree to > set the size of the address space, but it actually breaks KASAN). > > Isn't there a way to know if it supports svPBMT at runtime? Unfortunately, we can't detect Svpmbt through CSR read/write or traps. A DT property seems to be the only way for Svpmbt. Regards, Anup > > Alex > > > > > _______________________________________________ > > linux-riscv mailing list > > linux-riscv@...ts.infradead.org > > http://lists.infradead.org/mailman/listinfo/linux-riscv
Powered by blists - more mailing lists