From: Sean Christopherson <seanjc@google.com>
To: Jim Mattson <jmattson@google.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com
Subject: Re: [PATCH] KVM: VMX: Fix header file dependency of asm/vmx.h
Date: Fri, 25 Feb 2022 01:32:44 +0000 [thread overview]
Message-ID: <YhgxvA4KBEZc/4VG@google.com> (raw)
In-Reply-To: <20220225012959.1554168-1-jmattson@google.com>
On Thu, Feb 24, 2022, Jim Mattson wrote:
> From: Jacob Xu <jacobhxu@google.com>
>
> Include a definition of WARN_ON_ONCE() before using it.
>
> Fixes: bb1fcc70d98f ("KVM: nVMX: Allow L1 to use 5-level page walks for nested EPT")
> Cc: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Jacob Xu <jacobhxu@google.com>
> [reworded commit message; changed <asm/bug.h> to <linux/bug.h>]
> Signed-off-by: Jim Mattson <jmattson@google.com>
> ---
> 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 0ffaa3156a4e..447b97296400 100644
> --- a/arch/x86/include/asm/vmx.h
> +++ b/arch/x86/include/asm/vmx.h
> @@ -14,6 +14,7 @@
>
> #include <linux/bitops.h>
> #include <linux/types.h>
> +#include <linux/bug.h>
Paolo, any chance you want to put these in alphabetical order when applying? :-)
Reviewed-by: Sean Christopherson <seanjc@google.com>
> #include <uapi/asm/vmx.h>
> #include <asm/vmxfeatures.h>
>
> --
> 2.35.1.574.g5d30c73bfb-goog
>
next prev parent reply other threads:[~2022-02-25 1:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 1:29 [PATCH] KVM: VMX: Fix header file dependency of asm/vmx.h Jim Mattson
2022-02-25 1:32 ` Sean Christopherson [this message]
2022-02-25 1:34 ` Jim Mattson
2022-04-08 21:07 ` Jim Mattson
2023-05-16 21:40 ` Jim Mattson
2023-05-16 23:11 ` Sean Christopherson
2023-05-19 17:42 ` Paolo Bonzini
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=YhgxvA4KBEZc/4VG@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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 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.