All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	Richard Henderson <richard.henderson@linaro.org>,
	Vincent Donnefort <vdonnefort@google.com>,
	James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] KVM: arm64: Trap access to SMPRI_EL1 and TPIDR2 in VHE mode
Date: Tue, 01 Nov 2022 19:35:59 +0000	[thread overview]
Message-ID: <86a65aeacg.wl-maz@kernel.org> (raw)
In-Reply-To: <Y2EtcQSnu5R/Frhj@sirena.org.uk>

On Tue, 01 Nov 2022 14:30:09 +0000,
Mark Brown <broonie@kernel.org> wrote:
> 
> On Tue, Nov 01, 2022 at 01:33:16PM +0000, Marc Zyngier wrote:
> > Date: Tue, 1 Nov 2022 12:19:51 +0000
> > Subject: [PATCH] KVM: arm64: Fix SMPRI_EL1/TPIDR2_EL0 trapping on VHE
> > 
> > The trapping of SMPRI_EL1 and TPIDR2_EL0 currently only really
> > work on nVHE, as only this mode uses the fine-grained trapping
> > that controls these two registers.
> > 
> > Move the trapping enable/disable code into
> > __{de,}activate_traps_common(), allowing it to be called when it
> > actually matters on VHE, and remove the flipping of EL2 control
> > for TPIDR2_EL0, which only affects the host access of this
> > register.
> > 
> > Fixes: 861262ab8627 ("KVM: arm64: Handle SME host state when running guests")
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > Cc: stable@vger.kernel.org
> 
> Reported-by: Mark Brown <broonie@kernel.org>
> Reviewed-by: Mark Brown <broonie@kernel.org>

Thanks. I've now applied the first patch and this one to kvmarm/fixes.

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	Richard Henderson <richard.henderson@linaro.org>,
	Vincent Donnefort <vdonnefort@google.com>,
	James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] KVM: arm64: Trap access to SMPRI_EL1 and TPIDR2 in VHE mode
Date: Tue, 01 Nov 2022 19:35:59 +0000	[thread overview]
Message-ID: <86a65aeacg.wl-maz@kernel.org> (raw)
In-Reply-To: <Y2EtcQSnu5R/Frhj@sirena.org.uk>

On Tue, 01 Nov 2022 14:30:09 +0000,
Mark Brown <broonie@kernel.org> wrote:
> 
> On Tue, Nov 01, 2022 at 01:33:16PM +0000, Marc Zyngier wrote:
> > Date: Tue, 1 Nov 2022 12:19:51 +0000
> > Subject: [PATCH] KVM: arm64: Fix SMPRI_EL1/TPIDR2_EL0 trapping on VHE
> > 
> > The trapping of SMPRI_EL1 and TPIDR2_EL0 currently only really
> > work on nVHE, as only this mode uses the fine-grained trapping
> > that controls these two registers.
> > 
> > Move the trapping enable/disable code into
> > __{de,}activate_traps_common(), allowing it to be called when it
> > actually matters on VHE, and remove the flipping of EL2 control
> > for TPIDR2_EL0, which only affects the host access of this
> > register.
> > 
> > Fixes: 861262ab8627 ("KVM: arm64: Handle SME host state when running guests")
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > Cc: stable@vger.kernel.org
> 
> Reported-by: Mark Brown <broonie@kernel.org>
> Reviewed-by: Mark Brown <broonie@kernel.org>

Thanks. I've now applied the first patch and this one to kvmarm/fixes.

	M.

-- 
Without deviation from the norm, progress is not possible.

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

  reply	other threads:[~2022-11-01 19:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 11:27 [PATCH v2 0/2] arm64/sme: Fix SMPRI_EL1 traps for KVM guests Mark Brown
2022-11-01 11:27 ` Mark Brown
2022-11-01 11:27 ` [PATCH v2 1/2] arm64: booting: Document our requirements for fine grained traps with SME Mark Brown
2022-11-01 11:27   ` Mark Brown
2022-11-01 11:27 ` [PATCH v2 2/2] KVM: arm64: Trap access to SMPRI_EL1 and TPIDR2 in VHE mode Mark Brown
2022-11-01 11:27   ` Mark Brown
2022-11-01 13:33   ` Marc Zyngier
2022-11-01 13:33     ` Marc Zyngier
2022-11-01 14:30     ` Mark Brown
2022-11-01 14:30       ` Mark Brown
2022-11-01 19:35       ` Marc Zyngier [this message]
2022-11-01 19:35         ` Marc Zyngier
2022-11-01 19:34 ` (subset) [PATCH v2 0/2] arm64/sme: Fix SMPRI_EL1 traps for KVM guests Marc Zyngier
2022-11-01 19:34   ` Marc Zyngier

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=86a65aeacg.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=oliver.upton@linux.dev \
    --cc=peter.maydell@linaro.org \
    --cc=richard.henderson@linaro.org \
    --cc=stable@vger.kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=vdonnefort@google.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.