mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoffer Dall <Christoffer.Dall@arm.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Alexander Graf <graf@amazon.com>, Priscilla Lam <prl@amazon.com>,
	Marc Zyngier <maz@kernel.org>,
	"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
	"gurugubs@amazon.com" <gurugubs@amazon.com>,
	"jgrall@amazon.co.uk" <jgrall@amazon.co.uk>,
	Joey Gouly <Joey.Gouly@arm.com>,
	"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Suzuki Poulose <Suzuki.Poulose@arm.com>,
	"yuzenghui@huawei.com" <yuzenghui@huawei.com>
Subject: Re: [PATCH] KVM: arm64: Implement KVM_TRANSLATE ioctl for arm64
Date: Tue, 23 Sep 2025 18:05:15 +0000	[thread overview]
Message-ID: <71A90F04-2CF2-4FC6-B1D2-AE921BE3802B@arm.com> (raw)
In-Reply-To: <c8a8ddbc4b1c53429748d239f2a8461f180a5133.camel@infradead.org>



> On 23 Sep 2025, at 11.02, David Woodhouse <dwmw2@infradead.org> wrote:
> 
> On Tue, 2025-09-23 at 10:39 +0200, Alexander Graf wrote:
>> 
>> All modern OSs constrain themselves to only ISV enabled MMIO 
>> instructions.
> 
> Why? Such does not appear to be required by the architecture, AFAICT?


FYI, we are in the process of clarifying this area of limitation the architecture’s support for virtualization.

There is a note on the expectations for LDP and STP here:
https://developer.arm.com/documentation/102374/0103/Loads-and-stores---load-pair-and-store-pair?lang=en


Thanks,
Christoffer


  reply	other threads:[~2025-09-23 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 20:24 Priscilla Lam
2025-09-22 23:27 ` Oliver Upton
2025-09-23  8:03 ` Marc Zyngier
2025-09-23  8:29   ` Priscilla Lam
2025-09-23  8:39     ` Alexander Graf
2025-09-23  9:02       ` David Woodhouse
2025-09-23 18:05         ` Christoffer Dall [this message]
2025-09-23  9:25     ` Marc Zyngier
2025-09-25  5:21       ` Priscilla Lam

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=71A90F04-2CF2-4FC6-B1D2-AE921BE3802B@arm.com \
    --to=christoffer.dall@arm.com \
    --cc=Joey.Gouly@arm.com \
    --cc=Suzuki.Poulose@arm.com \
    --cc=dwmw2@infradead.org \
    --cc=graf@amazon.com \
    --cc=gurugubs@amazon.com \
    --cc=jgrall@amazon.co.uk \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=prl@amazon.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
all inboxes | Powered by JetHome®