From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Ayush Ranjan <ayushranjan@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ben Gardon <bgardon@google.com>,
Jim Mattson <jmattson@google.com>,
Andrei Vagin <avagin@gmail.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Davidson <md@google.com>
Subject: Re: [PATCH] gvisor: add some missing definitions to vmx.h
Date: Mon, 24 Jan 2022 17:04:52 +0000 [thread overview]
Message-ID: <Ye7cNMZku7jlRHa+@google.com> (raw)
In-Reply-To: <45a6395e-63f3-12b2-e6d1-52ccf00272e7@redhat.com>
On Mon, Jan 24, 2022, Paolo Bonzini wrote:
> On 1/23/22 20:53, Ayush Ranjan wrote:
> > From: Michael Davidson <md@google.com>
> >
> > gvisor needs definitions for some additional secondary exec controls.
> >
> > Tested: builds
> > Signed-off-by: Ayush Ranjan <ayushranjan@google.com>
> > Signed-off-by: Michael Davidson <md@google.com>
>
> Incorrect order of the Signed-off-by header (author goes first, submitter
> goes last).
>
> > ---
> > arch/x86/include/asm/vmx.h | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/x86/include/asm/vmx.h b/arch/x86/include/asm/vmx.h
> > index c77ad687cdf7..df40dc568eb9 100644
> > --- a/arch/x86/include/asm/vmx.h
> > +++ b/arch/x86/include/asm/vmx.h
> > @@ -67,6 +67,7 @@
> > #define SECONDARY_EXEC_ENCLS_EXITING VMCS_CONTROL_BIT(ENCLS_EXITING)
> > #define SECONDARY_EXEC_RDSEED_EXITING VMCS_CONTROL_BIT(RDSEED_EXITING)
> > #define SECONDARY_EXEC_ENABLE_PML VMCS_CONTROL_BIT(PAGE_MOD_LOGGING)
> > +#define SECONDARY_EXEC_EPT_VE VMCS_CONTROL_BIT(EPT_VIOLATION_VE)
> > #define SECONDARY_EXEC_PT_CONCEAL_VMX VMCS_CONTROL_BIT(PT_CONCEAL_VMX)
> > #define SECONDARY_EXEC_XSAVES VMCS_CONTROL_BIT(XSAVES)
> > #define SECONDARY_EXEC_MODE_BASED_EPT_EXEC VMCS_CONTROL_BIT(MODE_BASED_EPT_EXEC)
>
> I'm not sure why gvisor would care about an internal Linux header. gvisor
> should only use arch/x86/include/uapi headers.
It's Google-internal kernel crud, this patch should not be merged. Though with a
bit of patience, an equivalent patch will come with TDX support. If we do merge
something before TDX, I'd strongly prefer to take that "complete" version with a
rewritten changelog.
[*] https://lore.kernel.org/all/e519d6ae1e75a4bea494bb3940e1272e935ead18.1625186503.git.isaku.yamahata@intel.com
next prev parent reply other threads:[~2022-01-24 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 19:53 [PATCH] gvisor: add some missing definitions to vmx.h Ayush Ranjan
2022-01-24 9:43 ` Paolo Bonzini
2022-01-24 17:04 ` Sean Christopherson [this message]
2022-01-25 8:50 ` Ayush Ranjan
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=Ye7cNMZku7jlRHa+@google.com \
--to=seanjc@google.com \
--cc=avagin@gmail.com \
--cc=ayushranjan@google.com \
--cc=bgardon@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@google.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
/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).