public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson@rivosinc.com>
To: "Christoph Müllner" <christoph.muellner@vrull.eu>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	binutils@sourceware.org, kito.cheng@sifive.com,
	 Jim Wilson <jim.wilson.gcc@gmail.com>,
	philipp.tomsich@vrull.eu,  apatel@ventanamicro.com
Subject: Re: [PATCH] riscv: Add AIA extension support (Smaia, Ssaia)
Date: Fri, 26 Aug 2022 17:53:28 +0800	[thread overview]
Message-ID: <CAPpQWtCfe8fU-oYrMKumtPExe2+3zkn6PLMrHoFkY2Bs4o5RgQ@mail.gmail.com> (raw)
In-Reply-To: <CAEg0e7i5SgHrhY6yL9GN-o0_ZoZXmjBsqOqW=hjAn7xaK92fGw@mail.gmail.com>

On Fri, Aug 26, 2022 at 3:11 AM Christoph Müllner
<christoph.muellner@vrull.eu> wrote:
>
> This patch needs a v2 anyway because I missed the Hypervisor and VS CSRs.

Yeah, reviewed in advance, except the missing Hypervisor AIA CSRs and
the spec frozen issue which mentioned by Palmer, otherwise LGTM.  Just
curious that will we add something like "Shaia" or "Zhaia" for the
Hypervisor and VS AIA CSRs?  If no, then seems like they will belong
to the single h extension directly?  Anyway, this patch just support
Ssaia and Smaia extensions, so missing the hypervisor and VS AIA CSRs
seems reasonable...  Anyway, all of us agree to wait for the AIA spec
frozen before merging, so I think you can just merge this after that
time, since the Ssaia and Smaia don't include the Hypervisor AIA in
fact...

> > >> @@ -947,7 +956,12 @@ riscv_csr_address (const char *csr_name,
> > >>                       || csr_class == CSR_CLASS_SMSTATEEN_AND_H_32);
> > >>        extension = "smstateen";
> > >>        break;
> > >> -    case CSR_CLASS_SSCOFPMF_32:
> > >> +    case CSR_CLASS_SSAIA:
> > >> +    case CSR_CLASS_SSAIA_32:
> > >> +      is_rv32_only = (csr_class == CSR_CLASS_SSAIA_32);
> > >> +      extension = "ssaia";
> > >> +      break;
> > >> +     case CSR_CLASS_SSCOFPMF_32:

Here should be a minor indent issue.

Thanks
Nelson

  parent reply	other threads:[~2022-08-26  9:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 14:54 Christoph Muellner
2022-08-25 14:54 ` Christoph Muellner
2022-08-25 15:16 ` Christoph Müllner
2022-08-25 18:05   ` Palmer Dabbelt
2022-08-25 19:11     ` Christoph Müllner
2022-08-25 20:49       ` Palmer Dabbelt
2022-08-25 21:49         ` Philipp Tomsich
2022-08-26  9:53       ` Nelson Chu [this message]
2022-11-18  0:35         ` Christoph Müllner
2022-11-18  0:32 Christoph Muellner
2022-11-18  5:07 ` Tsukasa OI
2022-11-18  8:33   ` Christoph Müllner
2022-11-18  8:44     ` Tsukasa OI
2022-11-18  9:11       ` Christoph Müllner
2022-11-18  8:12 ` Nelson Chu
2022-11-18  9:08   ` Christoph Müllner
2022-11-18  9:34     ` Nelson Chu
2022-11-22  9:51       ` Christoph Müllner
2022-11-19  5:59     ` Tsukasa OI

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=CAPpQWtCfe8fU-oYrMKumtPExe2+3zkn6PLMrHoFkY2Bs4o5RgQ@mail.gmail.com \
    --to=nelson@rivosinc.com \
    --cc=apatel@ventanamicro.com \
    --cc=binutils@sourceware.org \
    --cc=christoph.muellner@vrull.eu \
    --cc=jim.wilson.gcc@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=palmer@dabbelt.com \
    --cc=philipp.tomsich@vrull.eu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).