All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Sebastian Ott <sebott@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Oliver Upton <oliver.upton@linux.dev>
Subject: Re: [RFC] [PATCH 0/4] KVM: arm64: emulation for CTR_EL0
Date: Mon, 18 Mar 2024 15:24:44 +0000	[thread overview]
Message-ID: <86y1afzhoj.wl-maz@kernel.org> (raw)
In-Reply-To: <20240318111636.10613-1-sebott@redhat.com>

On Mon, 18 Mar 2024 11:16:32 +0000,
Sebastian Ott <sebott@redhat.com> wrote:
> 
> Hej folks,
> 
> I'm looking into supporting migration between 2 Ampere Altra (Max)
> machines (using Neoverse-N1). They are almost identical regarding
> their feature id register state except for CTR_EL0.DIC which is set
> on one machine but not the other.
> 
> For a complete picture it's worth noting that the machine with
> CTR_EL0.DIC = 1 also suffers from erratum 1542419 meaning for
> userspace we trap the access and fake DIC=0. A KVM guest still sees
> the original host value for that register (I assume that this is
> intentional so that a guest OS can apply its own workaround to the
> erratum).

Indeed.

The intention is that the EL1 guest will hide DIC for EL0, while EL3
will trap IC instructions from EL0 and replace them with a TLBI.
That's of course assuming that the machine has received an updated
firmware, something that cannot be probed AFAICT.

	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:[~2024-03-18 15:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 11:16 [RFC] [PATCH 0/4] KVM: arm64: emulation for CTR_EL0 Sebastian Ott
2024-03-18 11:16 ` [PATCH 1/4] KVM: arm64: add emulation for CTR_EL0 register Sebastian Ott
2024-03-18 11:45   ` Marc Zyngier
2024-03-18 11:45     ` Marc Zyngier
2024-03-18 11:16 ` [PATCH 2/4] KVM: arm64: ensure guest access to CTR_EL0 is trapped Sebastian Ott
2024-03-18 11:47   ` Marc Zyngier
2024-03-18 11:16 ` [PATCH 3/4] KVM: arm64: show writable masks for feature registers Sebastian Ott
2024-03-18 12:03   ` Marc Zyngier
2024-03-18 18:20     ` Sebastian Ott
2024-03-19  9:50       ` Marc Zyngier
2024-03-18 18:22     ` Sebastian Ott
2024-03-18 11:16 ` [PATCH 4/4] KVM: selftests: aarch64: add tool to dump registers Sebastian Ott
2024-03-18 15:24 ` Marc Zyngier [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=86y1afzhoj.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=oliver.upton@linux.dev \
    --cc=sebott@redhat.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.