public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: broonie@kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [boot-wrapper PATCH 2/2] aarch64: Enable use of SME by EL2 and below
Date: Fri, 4 Feb 2022 10:59:20 +0000	[thread overview]
Message-ID: <Yf0HCAzLCoZXQffI@FVFF77S0Q05N> (raw)
In-Reply-To: <Yfl5Gic2Y3TixXpW@FVFF77S0Q05N>

On Tue, Feb 01, 2022 at 06:16:58PM +0000, Mark Rutland wrote:
> Hi Mark,
> 
> On Tue, Feb 01, 2022 at 05:21:32PM +0000, broonie@kernel.org wrote:
> > From: Mark Brown <broonie@kernel.org>
> > 
> > Allow lower ELs to use SME when booted on a system that support it. This
> > requires us to set two new bits, one in each of SCR_EL3 and CPTR_EL3, set
> > the maximum vector length in a similar fashion to SVE and if the optional
> > FA64 feature is present then set another feature bit in the new SMCR
> > register.
> 
> This looks good to me. I'll wait a day or so to allow others to review, but if
> no-one shouts I'll apply this (along with patch 1) before the end of the week.

I've applied both patches now.

Thanks,
Mark.

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

      parent reply	other threads:[~2022-02-04 11:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 17:21 [boot-wrapper PATCH 1/2] aarch64: Document what we're doing when setting ZCR_EL3.LEN broonie
2022-02-01 17:21 ` [boot-wrapper PATCH 2/2] aarch64: Enable use of SME by EL2 and below broonie
2022-02-01 18:16   ` Mark Rutland
2022-02-01 18:22     ` Mark Brown
2022-02-02 10:30       ` Mark Rutland
2022-02-04 10:59     ` Mark Rutland [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=Yf0HCAzLCoZXQffI@FVFF77S0Q05N \
    --to=mark.rutland@arm.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox