All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64: Don't allow SVE to be used with BROKEN_GAS_INST
Date: Wed, 2 Mar 2022 16:04:39 +0000	[thread overview]
Message-ID: <Yh+Vly2GL3ykEpR/@sirena.org.uk> (raw)
In-Reply-To: <Yh939U9dn7fvhKPz@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 739 bytes --]

On Wed, Mar 02, 2022 at 01:58:13PM +0000, Catalin Marinas wrote:

> It looks like it's not just SVE affected here. A grep for "\.inst\>"
> shows a few places in the crypto code as well. How hard is it to use
> __emit_inst() in these places?

TBH given the indeterminate existance of a userbase I'm not sure it's
even worth it - they're for v8.2 instructions and there's arguments
being encoded in there so I'd be more inclined to do the same as SVE and
shove some dependencies in there for now rather than make those macros
even longer.  I'd be astonished if there were anyone using a toolchain
old enough to have the issue with hardware new enough to be impacted,
the fact that we didn't hear about it thus far suggests that there isn't.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

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

      reply	other threads:[~2022-03-02 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 18:40 [PATCH] arm64: Don't allow SVE to be used with BROKEN_GAS_INST Mark Brown
2022-03-02 13:58 ` Catalin Marinas
2022-03-02 16:04   ` Mark Brown [this message]

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=Yh+Vly2GL3ykEpR/@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=will@kernel.org \
    /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.