mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Ayush Ranjan <ayushranjan@google.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: 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 10:43:50 +0100	[thread overview]
Message-ID: <45a6395e-63f3-12b2-e6d1-52ccf00272e7@redhat.com> (raw)
In-Reply-To: <20220123195337.509882-1-ayushranjan@google.com>

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.

Paolo


  reply	other threads:[~2022-01-24  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 19:53 Ayush Ranjan
2022-01-24  9:43 ` Paolo Bonzini [this message]
2022-01-24 17:04   ` Sean Christopherson
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=45a6395e-63f3-12b2-e6d1-52ccf00272e7@redhat.com \
    --to=pbonzini@redhat.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=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

Powered by JetHome