From: john cooper <john.cooper@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>, john.cooper@redhat.com
Subject: Re: [ANNOUNCE] kvm-78 release
Date: Tue, 04 Nov 2008 21:00:40 -0500 [thread overview]
Message-ID: <4910FE48.3030503@redhat.com> (raw)
Avi Kivity wrote:
> A fairly boring bunch of changes; most visible is that we can boot
> paravirt Linux kernels again, after kvm-77 broke it.
Looks like vtd.c isn't being built when CONFIG_DMAR
is enabled.
-john
=================================================================
--- a/kernel/x86/Kbuild
+++ b/kernel/x86/Kbuild
@@ -9,6 +9,9 @@ kvm-objs := kvm_main.o x86.o mmu.o x86_e
ifeq ($(EXT_CONFIG_KVM_TRACE),y)
kvm-objs += kvm_trace.o
endif
+ifeq ($(CONFIG_DMAR),y)
+kvm-objs += vtd.o
+endif
kvm-intel-objs := vmx.o vmx-debug.o ../external-module-compat.o
kvm-amd-objs := svm.o ../external-module-compat.o
=================================================================
--
john.cooper@redhat.com
next reply other threads:[~2008-11-05 2:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 2:00 john cooper [this message]
2008-11-05 9:09 ` [ANNOUNCE] kvm-78 release Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-11-02 7:39 Avi Kivity
2008-11-02 20:52 ` Alberto Treviño
2008-11-06 16:11 ` Avi Kivity
2008-11-06 16:20 ` Anthony Liguori
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=4910FE48.3030503@redhat.com \
--to=john.cooper@redhat.com \
--cc=avi@redhat.com \
--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