public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel•org>
To: Oliver Upton <oliver.upton@linux•dev>
Cc: kvmarm@lists•linux.dev, James Morse <james.morse@arm•com>,
	Suzuki K Poulose <suzuki.poulose@arm•com>,
	Zenghui Yu <yuzenghui@huawei•com>, Will Deacon <will@kernel•org>,
	Catalin Marinas <catalin.marinas@arm•com>,
	linux-arm-kernel@lists•infradead.org,
	Darren Hart <darren@os•amperecomputing.com>,
	D Scott Phillips <scott@os•amperecomputing.com>
Subject: Re: [PATCH 0/3] KVM: arm64: Work around Ampere1 erratum AC03_CPU_38
Date: Thu, 15 Jun 2023 10:51:42 +0100	[thread overview]
Message-ID: <87a5x1qci9.wl-maz@kernel.org> (raw)
In-Reply-To: <20230609220104.1836988-1-oliver.upton@linux.dev>

On Fri, 09 Jun 2023 23:01:01 +0100,
Oliver Upton <oliver.upton@linux•dev> wrote:
> 
> Hi folks,
> 
> Small series to work around a CPU erratum on AmpereOne. While the
> implementation does not advertise support for FEAT_HAFDBS (due to
> another erratum), the associated control bits do not have RES0 behavior
> as required by the architecture.
> 
> Usage of HAFDBS at stage-1 is unaffected, since HA and HD are only
> enabled on implementations that advertise the feature. However, KVM
> relies on HA having RES0 semantics if the feature isn't implemented. The
> end result is that KVM enables a broken hardware access flag
> implementation that could lead to correctness issues.
> 
> Applies to 6.4-rc1. Tested with access_tracking_perf_test, verifying
> that KVM is indeed taking Access Flag faults.

For the series:

Reviewed-by: Marc Zyngier <maz@kernel•org>

	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

  parent reply	other threads:[~2023-06-15  9:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 22:01 [PATCH 0/3] KVM: arm64: Work around Ampere1 erratum AC03_CPU_38 Oliver Upton
2023-06-09 22:01 ` [PATCH 1/3] arm64: errata: Mitigate Ampere1 erratum AC03_CPU_38 at stage-2 Oliver Upton
2023-06-14 16:58   ` Catalin Marinas
2023-06-14 17:15   ` D Scott Phillips
2023-06-09 22:01 ` [PATCH 2/3] KVM: arm64: Refactor HFGxTR configuration into separate helpers Oliver Upton
2023-06-09 22:01 ` [PATCH 3/3] KVM: arm64: Prevent guests from enabling HA/HD on Ampere1 Oliver Upton
2023-06-14 16:57 ` [PATCH 0/3] KVM: arm64: Work around Ampere1 erratum AC03_CPU_38 Catalin Marinas
2023-06-14 23:06   ` Oliver Upton
2023-06-15  8:36     ` Catalin Marinas
2023-06-15  9:51 ` Marc Zyngier [this message]
2023-06-20 13:15 ` Oliver Upton

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=87a5x1qci9.wl-maz@kernel.org \
    --to=maz@kernel$(echo .)org \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=darren@os$(echo .)amperecomputing.com \
    --cc=james.morse@arm$(echo .)com \
    --cc=kvmarm@lists$(echo .)linux.dev \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=oliver.upton@linux$(echo .)dev \
    --cc=scott@os$(echo .)amperecomputing.com \
    --cc=suzuki.poulose@arm$(echo .)com \
    --cc=will@kernel$(echo .)org \
    --cc=yuzenghui@huawei$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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