From: Alex Williamson <alex.williamson@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
KVM <kvm@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 29 (kvm)
Date: Mon, 29 Apr 2013 11:01:50 -0600 [thread overview]
Message-ID: <1367254910.16887.101.camel@ul30vt.home> (raw)
In-Reply-To: <517EA3DA.3070706@redhat.com>
On Mon, 2013-04-29 at 18:46 +0200, Paolo Bonzini wrote:
> Il 29/04/2013 18:31, Gleb Natapov ha scritto:
> >> > arch/x86/kvm/x86.c: In function 'kvm_dev_ioctl_check_extension':
> >> > arch/x86/kvm/x86.c:2547:22: error: 'pci_bus_type' undeclared (first use in this function)
> >> >
> >> >
> >> > Oops, CONFIG_PCI is not enabled.
> > Alex, can you look at this please. Before "kvm: Allow build-time configuration
> > of KVM device assignment" commit KVM depended on PCI to be enabled.
> >
>
> KVM_CAP_IOMMU probably should depend on device assignment. It doesn't
> really belong in KVM at all, and is only there for device assignment.
Yep, exactly.
next prev parent reply other threads:[~2013-04-29 17:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 9:17 linux-next: Tree for Apr 29 Stephen Rothwell
2013-04-29 15:52 ` linux-next: Tree for Apr 29 (kvm) Randy Dunlap
2013-04-29 16:31 ` Gleb Natapov
2013-04-29 16:46 ` Paolo Bonzini
2013-04-29 17:01 ` Alex Williamson [this message]
2013-04-29 16:49 ` Alex Williamson
2013-04-29 16:05 ` [PATCH -next] proc_fs.h: fix build error when PROC_FS is not enabled Randy Dunlap
2013-04-30 16:36 ` David Rientjes
2013-04-30 17:40 ` Randy Dunlap
2013-04-29 16:05 ` [PATCH -next] tty.h: fix build errors " Randy Dunlap
2013-04-30 16:39 ` David Rientjes
2013-04-29 16:17 ` linux-next: Tree for Apr 29 (include/linux/proc_fs.h: proc_net_mkdir) Randy Dunlap
2013-04-29 16:25 ` linux-next: Tree for Apr 29 (kconfig) Randy Dunlap
2013-04-29 17:42 ` Yann E. MORIN
2013-04-29 16:42 ` linux-next: Tree for Apr 29 (staging/gdm72xx) Randy Dunlap
2013-04-29 16:51 ` linux-next: Tree for Apr 29 (sound/soc) Randy Dunlap
2013-04-29 17:13 ` linux-next: Tree for Apr 29 (many build errors when PROC_FS is not set -- part 1) Randy Dunlap
2013-04-29 20:05 ` linux-next: Tree for Apr 29 Randy Dunlap
2013-04-29 21:03 ` Randy Dunlap
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=1367254910.16887.101.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).