From: Prarit Bhargava <prarit@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, Avi Kivity <avi@redhat.com>,
Gleb Natapov <gleb@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH] kvm, Add x86_hyper_kvm to complete detect_hypervisor_platform check
Date: Thu, 28 Jun 2012 07:11:31 -0400 [thread overview]
Message-ID: <4FEC3BE3.8050802@redhat.com> (raw)
In-Reply-To: <20120628012419.GA8956@phenom.dumpdata.com>
On 06/27/2012 09:24 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Jun 27, 2012 at 05:42:18PM -0400, Prarit Bhargava wrote:
>> While debugging I noticed that unlike all the other hypervisor code in the
>> kernel, kvm does not have an entry for x86_hyper which is used in
>> detect_hypervisor_platform(), and results in a nice message about the
>> hypervisor being used. This is only really a stub function and it makes
>> kvm more consistent with the other hypervisors (and it makes debugging
>> a little easier).
>>
>> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
>> Cc: Avi Kivity <avi@redhat.com>
>> Cc: Gleb Natapov <gleb@redhat.com>
>> Cc: Alex Williamson <alex.williamson@redhat.com>
>> ---
>> arch/x86/include/asm/hypervisor.h | 1 +
>> arch/x86/kernel/cpu/hypervisor.c | 1 +
>> arch/x86/kernel/kvm.c | 6 ++++++
>> 3 files changed, 8 insertions(+)
>>
>> diff --git a/arch/x86/include/asm/hypervisor.h b/arch/x86/include/asm/hypervisor.h
>> index 7a15153..b518c75 100644
>> --- a/arch/x86/include/asm/hypervisor.h
>> +++ b/arch/x86/include/asm/hypervisor.h
>> @@ -49,6 +49,7 @@ extern const struct hypervisor_x86 *x86_hyper;
>> extern const struct hypervisor_x86 x86_hyper_vmware;
>> extern const struct hypervisor_x86 x86_hyper_ms_hyperv;
>> extern const struct hypervisor_x86 x86_hyper_xen_hvm;
>> +extern const struct hypervisor_x86 x86_hyper_kvm;
>>
>> static inline bool hypervisor_x2apic_available(void)
>> {
>> diff --git a/arch/x86/kernel/cpu/hypervisor.c b/arch/x86/kernel/cpu/hypervisor.c
>> index 755f64f..6d6dd7a 100644
>> --- a/arch/x86/kernel/cpu/hypervisor.c
>> +++ b/arch/x86/kernel/cpu/hypervisor.c
>> @@ -37,6 +37,7 @@ static const __initconst struct hypervisor_x86 * const hypervisors[] =
>> #endif
>> &x86_hyper_vmware,
>> &x86_hyper_ms_hyperv,
>> + &x86_hyper_kvm,
>> };
>>
>> const struct hypervisor_x86 *x86_hyper;
>> diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c
>> index e554e5a..0a38b68 100644
>> --- a/arch/x86/kernel/kvm.c
>> +++ b/arch/x86/kernel/kvm.c
>> @@ -39,6 +39,7 @@
>> #include <asm/desc.h>
>> #include <asm/tlbflush.h>
>> #include <asm/idle.h>
>> +#include <asm/hypervisor.h>
>>
>> static int kvmapf = 1;
>>
>> @@ -432,6 +433,11 @@ void __init kvm_guest_init(void)
>> #endif
>> }
>>
>> +const struct hypervisor_x86 x86_hyper_kvm __refconst = {
>> + .name = "KVM",
>> +};
>> +EXPORT_SYMBOL(x86_hyper_kvm);
>
> EXPORT_SYMBOL_GPL version. ?
Hey Konrad, thanks for the review.
The other hypervisor_x86 structs are only EXPORT_SYMBOL, so I maintained that
convention here.
If I'm mistaken in that assumption, please let me know.
Thanks again,
P.
next prev parent reply other threads:[~2012-06-28 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 21:42 [PATCH] kvm, Add x86_hyper_kvm to complete detect_hypervisor_platform check Prarit Bhargava
2012-06-27 23:55 ` Prarit Bhargava
2012-06-28 1:24 ` Konrad Rzeszutek Wilk
2012-06-28 11:11 ` Prarit Bhargava [this message]
2012-06-28 14:06 ` Konrad Rzeszutek Wilk
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=4FEC3BE3.8050802@redhat.com \
--to=prarit@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.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).