From: Sean Christopherson <seanjc@google.com>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: Itaru Kitayama <itaru.kitayama@linux.dev>,
kvmarm@lists.linux.dev, Jim Mattson <jmattson@google.com>,
Yosry Ahmed <yosry.ahmed@linux.dev>
Subject: Re: RFC KVM: arm64: selftest: stage 2 mapping helpers
Date: Wed, 22 Oct 2025 06:34:58 -0700 [thread overview]
Message-ID: <aPjdgqHlxFOyjSKT@google.com> (raw)
In-Reply-To: <aPbL8NCPCfLHIB3w@linux.dev>
+Yosry and Jim
On Mon, Oct 20, 2025, Oliver Upton wrote:
> > +void virt_arch_s2_map(struct kvm_vm *vm, u64 ipa, u64 paddr);
> > +
> > +static inline void virt_s2_map(struct kvm_vm *vm, u64 ipa, u64 paddr)
> > +{
> > + virt_arch_s2_map(vm, ipa, paddr);
> > +}
>
> This is all going to be arm64-specific, no need for indirection through
> something pretending to be arch-generic.
I was going to ask about that. Do we want to try and provide a generic interface?
Yosry (and Jim) are working on unifying as much of the AMD vs. Intel logic as
possible, and if my wishes come true, unifying stage-1 and stage-2 mapping code
as well. I.e. if we envision any arch-agnositic tests that can do nested things,
now's the time. E.g. running dirty logging tests in L2 maybe?
next prev parent reply other threads:[~2025-10-22 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 9:08 RFC KVM: arm64: selftest: stage 2 mapping helpers Itaru Kitayama
2025-10-20 23:55 ` Oliver Upton
2025-10-22 5:25 ` Itaru Kitayama
2025-10-22 9:05 ` Oliver Upton
2025-10-25 0:24 ` Itaru Kitayama
2025-10-22 13:34 ` Sean Christopherson [this message]
2025-10-22 16:57 ` Yosry Ahmed
2025-10-22 17:47 ` Oliver Upton
2025-10-22 17:50 ` Yosry Ahmed
2025-10-23 15:46 ` Sean Christopherson
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=aPjdgqHlxFOyjSKT@google.com \
--to=seanjc@google.com \
--cc=itaru.kitayama@linux.dev \
--cc=jmattson@google.com \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=yosry.ahmed@linux.dev \
/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.