From: Alexander Graf <agraf@suse.de>
To: kvm@vger.kernel.org
Subject: [PATCH] KVM on VMI
Date: Wed, 09 Jul 2008 09:57:55 +0200 [thread overview]
Message-ID: <48746F83.2020702@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
Hi,
I more or less accidently stumbled across a problem when compiling KVM
on the VMI-enabled kernel. Even though that's pretty much useless right
now, I think there might be a day, VMware will emulate VM extensions, in
VMs, so we should probably not keep KVM from running under VMI.
The problem is that usually load_ldt is #defined, while in VMI it's a
static void function. This clashes with the way KVM detects if load_ldt
is defined already. To circumvent this, I just extended the check so
we're not redefining load_ldt when VMI is activated.
Signed-off-by: Alexander Graf <agraf@suse.de>
[-- Attachment #2: kvm-vmi.patch --]
[-- Type: text/x-patch, Size: 354 bytes --]
--- kernel/include/asm-x86/kvm_host.h 2008-07-09 08:02:20.000000000 +0000
+++ kernel/include/asm-x86/kvm_host.h 2008-07-09 08:02:58.000000000 +0000
@@ -597,7 +597,7 @@
asm("mov %0, %%gs" : : "rm"(sel));
}
-#ifndef load_ldt
+#if !(defined(load_ldt) || defined(CONFIG_X86_VMI))
static inline void load_ldt(u16 sel)
{
asm("lldt %0" : : "rm"(sel));
next reply other threads:[~2008-07-09 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 7:57 Alexander Graf [this message]
2008-07-10 13:55 ` [PATCH] KVM on VMI Avi Kivity
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=48746F83.2020702@suse.de \
--to=agraf@suse.de \
--cc=kvm@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