[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220124072208.GA21441@lst.de>
Date: Mon, 24 Jan 2022 08:22:08 +0100
From: Christoph Hellwig <hch@....de>
To: Heiko Stuebner <heiko@...ech.de>
Cc: palmer@...belt.com, paul.walmsley@...ive.com,
aou@...s.berkeley.edu, linux-riscv@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
robh+dt@...nel.org, wefu@...hat.com, liush@...winnertech.com,
guoren@...nel.org, atishp@...shpatra.org, anup@...infault.org,
drew@...gleboard.org, hch@....de, arnd@...db.de, wens@...e.org,
maxime@...no.tech, dlustig@...dia.com, gfavor@...tanamicro.com,
andrea.mondelli@...wei.com, behrensj@....edu, xinhaoqu@...wei.com,
huffman@...ence.com, mick@....forth.gr,
allen.baum@...erantotech.com, jscheid@...tanamicro.com,
rtrauben@...il.com, samuel@...lland.org, cmuellner@...ux.com,
philipp.tomsich@...ll.eu
Subject: Re: [PATCH v5 00/14] riscv: support for svpbmt and D1 memory types
On Fri, Jan 21, 2022 at 05:36:04PM +0100, Heiko Stuebner wrote:
> So this is my try at implementing svpbmt (and the diverging D1 memory
> types using the alternatives framework).
Please spell out what it does. While I can remember the original single
letter extensions very well, the new priviliged extension naming is
just letter salad.
You might also want to explain in more detail what it does and why you
want to support it.
Powered by blists - more mailing lists