All of lore.kernel.org
 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>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH 0/2] KVM: arm64: Fixes and clarifications for FEAT_S1POE
Date: Wed, 23 Jul 2025 23:49:16 -0700	[thread overview]
Message-ID: <175333974801.2689259.7241226036667570185.b4-ty@linux.dev> (raw)
In-Reply-To: <20250701151648.754785-1-maz@kernel.org>

On Tue, 01 Jul 2025 16:16:46 +0100, Marc Zyngier wrote:
> I (almost accidentally) spotted a couple of issues with the current NV
> support for S1POE:
> 
> - wi->{e0,}poe and wr->{p,u}ov are used interchangeably, and sometimes
>   in conjunction -- none of that makes much sense
> 
> - The two rules describing WXN are not exactly been applied to the
>   correct state
> 
> [...]

Applied to next, thanks!

[1/2] KVM: arm64: Remove the wi->{e0,}poe vs wr->{p,u}ov confusion
      https://git.kernel.org/kvmarm/kvmarm/c/a508d5afb708
[2/2] KVM: arm64: Follow specification when implementing WXN
      https://git.kernel.org/kvmarm/kvmarm/c/5152977340b6

--
Best,
Oliver

      parent reply	other threads:[~2025-07-24  6:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 15:16 [PATCH 0/2] KVM: arm64: Fixes and clarifications for FEAT_S1POE Marc Zyngier
2025-07-01 15:16 ` [PATCH 1/2] KVM: arm64: Remove the wi->{e0,}poe vs wr->{p,u}ov confusion Marc Zyngier
2025-07-01 15:16 ` [PATCH 2/2] KVM: arm64: Follow specification when implementing WXN Marc Zyngier
2025-07-24  6:49 ` Oliver Upton [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=175333974801.2689259.7241226036667570185.b4-ty@linux.dev \
    --to=oliver.upton@linux.dev \
    --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 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.