Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <palmer@rivosinc.com>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] RISC-V: Add support for Ztso
Date: Fri, 16 Sep 2022 10:00:35 +0000	[thread overview]
Message-ID: <c8004a8f-235e-083c-2dcb-7fa746bad421@microchip.com> (raw)
In-Reply-To: <20220902034352.8825-1-palmer@rivosinc.com>

On 02/09/2022 04:43, Palmer Dabbelt wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> The Ztso extension was recently frozen, this adds support for running
> binaries that depend on TSO on systems that support Ztso.
> 
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

>   /*
> - * This is used to ensure we don't load something for the wrong architecture.
> + * Binaries that assume TSO cannot be correctly run on non-TSO systems, so
> + * prevent them from even being loaded.
> + */
> +#define EF_RISCV_TSO   0x0010

My only comment, and I asked this on the other patch too, is why is this
not s/EF/ELF like the other defines in the file?

Thanks,
Conor.

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

  parent reply	other threads:[~2022-09-16 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02  3:43 [PATCH] RISC-V: Add support for Ztso Palmer Dabbelt
2022-09-02  6:39 ` Andreas Schwab
2022-09-16 14:09   ` Palmer Dabbelt
2022-09-02  6:50 ` Anup Patel
2022-09-16 14:15   ` Palmer Dabbelt
2022-09-16 10:00 ` Conor.Dooley [this message]
2022-09-16 14:09   ` Palmer Dabbelt
2022-09-16 14:13     ` Conor.Dooley

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=c8004a8f-235e-083c-2dcb-7fa746bad421@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox