From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Lai Jiangshan <jiangshanlai@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Lai Jiangshan <jiangshan.ljs@antgroup.com>,
Jonathan Corbet <corbet@lwn.net>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH V3 2/4] KVM: X86: Introduce role.glevel for level expanded pagetable
Date: Wed, 13 Apr 2022 10:38:26 +0200 [thread overview]
Message-ID: <caffa434-5644-ee73-1636-45a87517bae2@redhat.com> (raw)
In-Reply-To: <YlXvtMqWpyM9Bjox@google.com>
On 4/12/22 23:31, Sean Christopherson wrote:
>> + unsigned glevel:4;
> We don't need 4 bits for this. Crossing our fingers that we never had to shadow
> a 2-level guest with a 6-level host, we can do:
>
> unsigned passthrough_delta:2;
>
> Where the field is ignored if direct=1, '0' for non-passthrough, and 1-3 to handle
> shadow_root_level - guest_root_level. Basically the same idea as Paolo's smushing
> of direct+passthrough into mapping_level, just dressed up differently.
Basically, your passthrough_delta is level - glevel in Jiangshan's
patches. You'll need 3 bits anyway when we remove direct later (that
would be passthrough_delta == level).
Regarding the naming:
* If we keep Jiangshan's logic, I don't like the glevel name very much,
any of mapping_level, target_level or direct_level would be clearer?
* If we go with yours, I would call the field "passthrough_levels".
Paolo
next prev parent reply other threads:[~2022-04-13 8:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220330132152.4568-1-jiangshanlai@gmail.com>
2022-03-30 13:21 ` [RFC PATCH V3 2/4] KVM: X86: Introduce role.glevel for level expanded pagetable Lai Jiangshan
2022-03-30 16:01 ` Lai Jiangshan
2022-04-12 21:31 ` Sean Christopherson
2022-04-13 4:13 ` Lai Jiangshan
2022-04-13 8:38 ` Paolo Bonzini [this message]
2022-04-13 14:42 ` Sean Christopherson
2022-04-13 14:46 ` Paolo Bonzini
2022-04-13 15:32 ` Sean Christopherson
2022-04-13 16:03 ` Paolo Bonzini
2022-04-14 15:51 ` Sean Christopherson
2022-04-14 16:32 ` Lai Jiangshan
2022-03-30 13:21 ` [RFC PATCH V3 3/4] KVM: X86: Alloc role.pae_root shadow page Lai Jiangshan
2022-04-12 21:14 ` Sean Christopherson
2022-04-14 9:07 ` Lai Jiangshan
2022-04-14 9:08 ` Paolo Bonzini
2022-04-14 9:32 ` Lai Jiangshan
2022-04-14 10:04 ` Paolo Bonzini
2022-04-14 11:06 ` Lai Jiangshan
2022-04-14 14:12 ` Paolo Bonzini
2022-04-14 14:42 ` Sean Christopherson
2022-04-14 13:35 ` Lai Jiangshan
2022-04-14 14:52 ` 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=caffa434-5644-ee73-1636-45a87517bae2@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jiangshan.ljs@antgroup.com \
--cc=jiangshanlai@gmail.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).