Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	Marc Zyngier <maz@kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	Joey Gouly <joey.gouly@arm.com>,
	James Morse <james.morse@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [PATCH] KVM: arm64: nv: Fix RESx behaviour of disabled FGTs with negative polarity
Date: Fri, 14 Jun 2024 20:24:51 +0000	[thread overview]
Message-ID: <171839668434.686757.6430070893119235107.b4-ty@linux.dev> (raw)
In-Reply-To: <20240614125858.78361-1-maz@kernel.org>

On Fri, 14 Jun 2024 13:58:58 +0100, Marc Zyngier wrote:
> The Fine Grained Trap extension is pretty messy as it doesn't
> consistently use the same polarity for all trap bits. A bunch
> of them, added later in the life of the architecture, have a
> *negative* priority.
> 
> So if these bits are disabled, they must be RES1 and not RES0.
> But that's not what the code implements, making the traps for
> these negative trap bits being always on instead of disabled.
> 
> [...]

Applied to kvmarm/next, thanks!

[1/1] KVM: arm64: nv: Fix RESx behaviour of disabled FGTs with negative polarity
      https://git.kernel.org/kvmarm/kvmarm/c/eb9d53d4a949

--
Best,
Oliver

  reply	other threads:[~2024-06-14 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 12:58 [PATCH] KVM: arm64: nv: Fix RESx behaviour of disabled FGTs with negative polarity Marc Zyngier
2024-06-14 20:24 ` Oliver Upton [this message]
2024-07-05 12:08   ` Marc Zyngier
2024-07-08 19:59     ` 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=171839668434.686757.6430070893119235107.b4-ty@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=yuzenghui@huawei.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