From: Nick Desaulniers <nick.desaulniers@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Josh Triplett" <josh@joshtriplett.org>,
kay@vrfy.org, avi@redhat.com,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: VMX: check match table
Date: Sat, 30 Sep 2017 16:22:34 -0700 [thread overview]
Message-ID: <20170930232234.ue665ojgjkegjpag@lostoracle.net> (raw)
In-Reply-To: <498ed7dc-41b2-a075-cdce-e63a80842d39@redhat.com>
On Wed, Sep 27, 2017 at 02:36:03PM +0200, Paolo Bonzini wrote:
> On 26/09/2017 19:12, Josh Triplett wrote:
> > Does this make any other checks redundant and removable?
>
> It would make sense to place it in cpu_has_kvm_support instead
cpu_has_kvm_support() or cpu_has_vmx()?
>, and the same in svm.c's has_svm.
I don't follow (but I also don't know what any of these three letter
acryonyms acronyms stand for), does svm depend on vmx or vice-versa?
next prev parent reply other threads:[~2017-09-30 23:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 3:07 unneeded internal declaration Nick Desaulniers
2017-09-26 3:35 ` Josh Triplett
2017-09-26 4:15 ` Nick Desaulniers
2017-09-26 4:25 ` [PATCH] KVM: VMX: check match table Nick Desaulniers
2017-09-26 17:12 ` Josh Triplett
2017-09-27 12:36 ` Paolo Bonzini
2017-09-30 23:22 ` Nick Desaulniers [this message]
2017-10-03 9:42 ` Paolo Bonzini
2017-10-04 2:54 ` Nick Desaulniers
2017-10-04 2:58 ` Nick Desaulniers
2017-09-27 14:14 ` kbuild test robot
2017-09-27 12:38 ` unneeded internal declaration Paolo Bonzini
[not found] ` <CAK5g=XOWn=nUpa1Q0Oc4CntRX0LbJjbatJKLUgQOCsaba_3hNw@mail.gmail.com>
2017-09-27 12:50 ` 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=20170930232234.ue665ojgjkegjpag@lostoracle.net \
--to=nick.desaulniers@gmail.com \
--cc=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=josh@joshtriplett.org \
--cc=kay@vrfy.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®