From: Alex Williamson <alex.williamson@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: aik@ozlabs.ru, aliguori@us.ibm.com, qemu-devel@nongnu.org,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 3/3] vfio: Enable vfio-pci and mark supported
Date: Wed, 01 Aug 2012 13:40:47 -0600 [thread overview]
Message-ID: <1343850047.6698.42.camel@bling.home> (raw)
In-Reply-To: <1343844888.6698.8.camel@bling.home>
On Wed, 2012-08-01 at 12:14 -0600, Alex Williamson wrote:
> On Wed, 2012-08-01 at 09:15 +0200, Jan Kiszka wrote:
> > On 2012-08-01 07:18, Alex Williamson wrote:
> > > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> > > ---
> > >
> > > MAINTAINERS | 5 +++++
> > > configure | 12 ++++++++++++
> > > hw/i386/Makefile.objs | 1 +
> > > 3 files changed, 18 insertions(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 2d219d2..9680d69 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -460,6 +460,11 @@ M: Gerd Hoffmann <kraxel@redhat.com>
> > > S: Maintained
> > > F: hw/usb*
> > >
> > > +VFIO
> > > +M: Alex Williamson <alex.williamson@redhat.com>
> > > +S: Supported
> > > +F: hw/vfio*
> > > +
> > > vhost
> > > M: Michael S. Tsirkin <mst@redhat.com>
> > > S: Supported
> > > diff --git a/configure b/configure
> > > index c65b5f6..81108dc 100755
> > > --- a/configure
> > > +++ b/configure
> > > @@ -143,6 +143,7 @@ attr=""
> > > libattr=""
> > > xfs=""
> > >
> > > +vfio_pci="no"
> > > vhost_net="no"
> > > kvm="no"
> > > gprof="no"
> > > @@ -489,6 +490,7 @@ Haiku)
> > > usb="linux"
> > > kvm="yes"
> > > vhost_net="yes"
> > > + vfio_pci="yes"
> > > if [ "$cpu" = "i386" -o "$cpu" = "x86_64" ] ; then
> > > audio_possible_drivers="$audio_possible_drivers fmod"
> > > fi
> > > @@ -824,6 +826,10 @@ for opt do
> > > ;;
> > > --disable-guest-agent) guest_agent="no"
> > > ;;
> > > + --disable-vfio-pci) vfio_pci="no"
> > > + ;;
> > > + --enable-vfio-pci) vfio_pci="yes"
> > > + ;;
> >
> > Do we need this level of control? Open question I'm just wondering every
> > time a new feature gets added together with --disable/--enable switches.
>
> Well, I could certainly understand if some downstream wanted to ship a
> qemu that didn't enable device assignment. I'm sure they'd rather have
> a config option to do that instead of needing to modify code. I
> generally find --enable useful to force an error and tell me what I'm
> missing when I specifically want a feature rather than having it
> silently disabled.
>
> > > *) echo "ERROR: unknown option $opt"; show_help="yes"
> > > ;;
> > > esac
> > > @@ -1112,6 +1118,8 @@ echo " --disable-guest-agent disable building of the QEMU Guest Agent"
> > > echo " --enable-guest-agent enable building of the QEMU Guest Agent"
> > > echo " --with-coroutine=BACKEND coroutine backend. Supported options:"
> > > echo " gthread, ucontext, sigaltstack, windows"
> > > +echo " --disable-vfio-pci disable vfio pci device assignement support"
> > > +echo " --enable-vfio-pci enable vfio pci device assignment support"
> > > echo ""
> > > echo "NOTE: The object files are built at the place where configure is launched"
> > > exit 1
> > > @@ -3072,6 +3080,7 @@ echo "OpenGL support $opengl"
> > > echo "libiscsi support $libiscsi"
> > > echo "build guest agent $guest_agent"
> > > echo "coroutine backend $coroutine_backend"
> > > +echo "VFIO PCI support $vfio_pci"
> > >
> > > if test "$sdl_too_old" = "yes"; then
> > > echo "-> Your SDL version is too old - please upgrade to have SDL support"
> > > @@ -3754,6 +3763,9 @@ case "$target_arch2" in
> > > *)
> > > echo "CONFIG_NO_XEN=y" >> $config_target_mak
> > > esac
> > > +if test "$vfio_pci" = "yes" -a "$target_softmmu" = "yes" ; then
> > > + echo "CONFIG_VFIO_PCI=y" >> $config_target_mak
> > > +fi
> >
> > Does this already somehow depend on host == Linux? If not, you may break
> > the others.
>
> Hmm, probably missing that, I'll look where to add it. Thanks,
Or I'm just forgetful. This is handled by the vfio_pci="yes" in the
second chunk of configure above. Thanks,
Alex
next prev parent reply other threads:[~2012-08-01 19:40 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 5:18 [Qemu-devel] [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2 Alex Williamson
2012-08-01 5:18 ` [Qemu-devel] [PATCH 1/3] vfio: Import vfio kernel header Alex Williamson
2012-08-01 7:13 ` Jan Kiszka
2012-08-01 18:09 ` Alex Williamson
2012-08-02 9:02 ` Jan Kiszka
2012-08-02 16:37 ` Alex Williamson
2012-08-02 16:45 ` Jan Kiszka
2012-08-01 5:18 ` [Qemu-devel] [PATCH 2/3] vfio: vfio-pci device assignment driver Alex Williamson
2012-08-13 22:18 ` Anthony Liguori
2012-08-14 5:25 ` Alex Williamson
2012-08-14 7:12 ` Stefan Hajnoczi
2012-08-14 13:51 ` Alex Williamson
2012-08-14 15:53 ` Avi Kivity
2012-08-14 17:23 ` Alex Williamson
2012-08-15 8:56 ` Avi Kivity
2012-08-01 5:18 ` [Qemu-devel] [PATCH 3/3] vfio: Enable vfio-pci and mark supported Alex Williamson
2012-08-01 7:15 ` Jan Kiszka
2012-08-01 18:14 ` Alex Williamson
2012-08-01 19:40 ` Alex Williamson [this message]
2012-08-02 9:03 ` Jan Kiszka
2012-08-13 22:19 ` Anthony Liguori
2012-08-14 5:27 ` Alex Williamson
2012-08-14 14:35 ` Avi Kivity
2012-08-13 13:27 ` [Qemu-devel] [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2 Anthony Liguori
2012-08-13 13:58 ` Avi Kivity
2012-08-13 14:04 ` Jan Kiszka
2012-08-13 19:31 ` Anthony Liguori
2012-08-14 7:19 ` Jan Kiszka
2012-08-14 14:42 ` Avi Kivity
2012-08-14 14:53 ` Cole Robinson
2012-08-14 15:04 ` Jan Kiszka
2012-08-14 15:28 ` Cole Robinson
2012-08-13 14:23 ` Alex Williamson
2012-08-13 15:48 ` Andreas Hartmann
2012-08-13 16:14 ` Alex Williamson
2012-08-13 16:36 ` Andreas Hartmann
2012-08-13 16:57 ` Alex Williamson
2012-08-13 18:32 ` Andreas Hartmann
2012-08-13 19:33 ` Anthony Liguori
2012-08-13 20:48 ` Blue Swirl
2012-08-13 20:56 ` Alex Williamson
2012-08-13 20:55 ` [Qemu-devel] VFIO: Call for reviewers (was Re: [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2) Alex Williamson
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=1343850047.6698.42.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).