Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Sebastian Ott <sebott@redhat.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev
Subject: Re: writable ID_AA64MMFR0_EL1.TGRAN*_2 ?
Date: Mon, 03 Mar 2025 19:39:40 +0000	[thread overview]
Message-ID: <86h649q4xv.wl-maz@kernel.org> (raw)
In-Reply-To: <597411b1-ff60-edc3-d6f2-1b21ce2e34e9@redhat.com>

On Fri, 28 Feb 2025 15:19:06 +0000,
Sebastian Ott <sebott@redhat.com> wrote:
> 
> Hi,
> 
> I'm looking into the possibility of migrating between 2 (Graviton) hosts
> and the only ID register diffs that are not yet writable are TGRAN*_2.
> Both hosts support the same sizes for S2 but express that differently
> (2==supported vs 0=="look at TGRAN*").
> 
> One idea would be to either set the guest view for these to NI (for the
> "normal" / not nested guest) or allow to convert between the 2 values
> (and maybe also allow to write NI for good measure).

I think we can allow any value to be written to any of the TGRAN*_2 in
a non-NV context. For NV, we must be fairly strict, by enforcing that
NI is the floor limit for the feature (we cannot let 0 be written for
any of them).

Thanks,

	M.

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

      reply	other threads:[~2025-03-03 19:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 15:19 writable ID_AA64MMFR0_EL1.TGRAN*_2 ? Sebastian Ott
2025-03-03 19:39 ` 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=86h649q4xv.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox