All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Kossifidis <mick@ics.forth.gr>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>
Cc: "Nick Kossifidis" <mick@ics.forth.gr>,
	"Anup Patel" <anup@brainfault.org>, "Guo Ren" <guoren@kernel.org>,
	"Anup Patel" <anup.patel@wdc.com>,
	"Atish Patra" <atish.patra@wdc.com>,
	"Palmer Dabbelt" <palmerdabbelt@google.com>,
	"Christoph Müllner" <christoph.muellner@vrull.eu>,
	"Christoph Hellwig" <hch@lst.de>, liush <liush@allwinnertech.com>,
	wefu@redhat.com, "Wei Wu (吴伟)" <lazyparser@gmail.com>,
	"Drew Fustini" <drew@beagleboard.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	"linux-kernel@vger.kernel.org List"
	<linux-kernel@vger.kernel.org>,
	taiten.peng@canonical.com, aniket.ponkshe@canonical.com,
	"Heinrich Schuchardt" <heinrich.schuchardt@canonical.com>,
	gordan.markus@canonical.com, "Guo Ren" <guoren@linux.alibaba.com>,
	"Arnd Bergmann" <arnd@arndb.de>, "Chen-Yu Tsai" <wens@csie.org>,
	"Maxime Ripard" <maxime@cerno.tech>,
	"Daniel Lustig" <dlustig@nvidia.com>,
	"Greg Favor" <gfavor@ventanamicro.com>,
	"Andrea Mondelli" <andrea.mondelli@huawei.com>,
	"Jonathan Behrens" <behrensj@mit.edu>,
	Xinhaoqu <xinhaoqu@huawei.com>,
	"Bill Huffman" <huffman@cadence.com>,
	"Allen Baum" <allen.baum@esperantotech.com>,
	"Josh Scheid" <jscheid@ventanamicro.com>,
	"Richard Trauben" <rtrauben@gmail.com>
Subject: Re: [PATCH] riscv: Add RISC-V svpbmt extension
Date: Thu, 23 Sep 2021 13:09:45 +0300	[thread overview]
Message-ID: <88696248a0c19a5dff660354b837514d@mailhost.ics.forth.gr> (raw)
In-Reply-To: <CAAeLtUDu0yaDBcuC06nX1WUQC9k4eNuWjvAFrpkP_h0nf5BZAw@mail.gmail.com>

Στις 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.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Nick Kossifidis <mick@ics.forth.gr>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>
Cc: "Nick Kossifidis" <mick@ics.forth.gr>,
	"Anup Patel" <anup@brainfault.org>, "Guo Ren" <guoren@kernel.org>,
	"Anup Patel" <anup.patel@wdc.com>,
	"Atish Patra" <atish.patra@wdc.com>,
	"Palmer Dabbelt" <palmerdabbelt@google.com>,
	"Christoph Müllner" <christoph.muellner@vrull.eu>,
	"Christoph Hellwig" <hch@lst.de>, liush <liush@allwinnertech.com>,
	wefu@redhat.com, "Wei Wu (吴伟)" <lazyparser@gmail.com>,
	"Drew Fustini" <drew@beagleboard.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	"linux-kernel@vger.kernel.org List"
	<linux-kernel@vger.kernel.org>,
	taiten.peng@canonical.com, aniket.ponkshe@canonical.com,
	"Heinrich Schuchardt" <heinrich.schuchardt@canonical.com>,
	gordan.markus@canonical.com, "Guo Ren" <guoren@linux.alibaba.com>,
	"Arnd Bergmann" <arnd@arndb.de>, "Chen-Yu Tsai" <wens@csie.org>,
	"Maxime Ripard" <maxime@cerno.tech>,
	"Daniel Lustig" <dlustig@nvidia.com>,
	"Greg Favor" <gfavor@ventanamicro.com>,
	"Andrea Mondelli" <andrea.mondelli@huawei.com>,
	"Jonathan Behrens" <behrensj@mit.edu>,
	Xinhaoqu <xinhaoqu@huawei.com>,
	"Bill Huffman" <huffman@cadence.com>,
	"Allen Baum" <allen.baum@esperantotech.com>,
	"Josh Scheid" <jscheid@ventanamicro.com>,
	"Richard Trauben" <rtrauben@gmail.com>
Subject: Re: [PATCH] riscv: Add RISC-V svpbmt extension
Date: Thu, 23 Sep 2021 13:09:45 +0300	[thread overview]
Message-ID: <88696248a0c19a5dff660354b837514d@mailhost.ics.forth.gr> (raw)
In-Reply-To: <CAAeLtUDu0yaDBcuC06nX1WUQC9k4eNuWjvAFrpkP_h0nf5BZAw@mail.gmail.com>

Στις 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.

  parent reply	other threads:[~2021-09-23 10:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  7:27 [PATCH] riscv: Add RISC-V svpbmt extension guoren
2021-09-23  7:27 ` guoren
2021-09-23  9:13 ` Anup Patel
2021-09-23  9:13   ` Anup Patel
2021-09-23 11:53   ` Guo Ren
2021-09-23 11:53     ` Guo Ren
2021-09-23  9:24 ` Nick Kossifidis
2021-09-23  9:24   ` Nick Kossifidis
2021-09-23  9:37   ` Anup Patel
2021-09-23  9:37     ` Anup Patel
2021-09-23  9:42     ` Nick Kossifidis
2021-09-23  9:42       ` Nick Kossifidis
2021-09-23  9:48       ` Nick Kossifidis
2021-09-23  9:48         ` Nick Kossifidis
2021-09-23  9:57         ` Anup Patel
2021-09-23  9:57           ` Anup Patel
2021-09-23 10:07         ` Philipp Tomsich
2021-09-23 10:07           ` Philipp Tomsich
2021-09-23 10:36           ` Anup Patel
2021-09-23 10:36             ` Anup Patel
     [not found]         ` <CAAeLtUDu0yaDBcuC06nX1WUQC9k4eNuWjvAFrpkP_h0nf5BZAw@mail.gmail.com>
2021-09-23 10:09           ` Nick Kossifidis [this message]
2021-09-23 10:09             ` Nick Kossifidis
2021-09-23 11:50             ` Alexandre Ghiti
2021-09-23 11:50               ` Alexandre Ghiti
2021-09-23 12:05               ` Anup Patel
2021-09-23 12:05                 ` Anup Patel
2021-09-23 12:05             ` Guo Ren
2021-09-23 12:05               ` Guo Ren
2021-09-23 12:04   ` Guo Ren
2021-09-23 12:04     ` Guo Ren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=88696248a0c19a5dff660354b837514d@mailhost.ics.forth.gr \
    --to=mick@ics.forth.gr \
    --cc=allen.baum@esperantotech.com \
    --cc=andrea.mondelli@huawei.com \
    --cc=aniket.ponkshe@canonical.com \
    --cc=anup.patel@wdc.com \
    --cc=anup@brainfault.org \
    --cc=arnd@arndb.de \
    --cc=atish.patra@wdc.com \
    --cc=behrensj@mit.edu \
    --cc=christoph.muellner@vrull.eu \
    --cc=dlustig@nvidia.com \
    --cc=drew@beagleboard.org \
    --cc=gfavor@ventanamicro.com \
    --cc=gordan.markus@canonical.com \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=hch@lst.de \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=huffman@cadence.com \
    --cc=jscheid@ventanamicro.com \
    --cc=lazyparser@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=liush@allwinnertech.com \
    --cc=maxime@cerno.tech \
    --cc=palmerdabbelt@google.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=rtrauben@gmail.com \
    --cc=taiten.peng@canonical.com \
    --cc=wefu@redhat.com \
    --cc=wens@csie.org \
    --cc=xinhaoqu@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.