All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH] vfio: VFIO PCI driver for Qemu
Date: Sat, 28 Jul 2012 12:55:56 +1000	[thread overview]
Message-ID: <501354BC.9060405@ozlabs.ru> (raw)
In-Reply-To: <CAAu8pHvwT4SJrtGUh4abARcXe5f9aWL5+7dCpdPhQrED6G4hBA@mail.gmail.com>

On 28/07/12 05:22, Blue Swirl wrote:
> On Wed, Jul 25, 2012 at 5:03 PM, Alex Williamson
>> +
>> +static void vfio_enable_intx_kvm(VFIODevice *vdev)
>> +{
>> +#ifdef CONFIG_KVM
>
> These shouldn't be needed. The device will not be useful without KVM,
> so the file shouldn't be compiled for non-KVM case at all.

It compiles without --enable-kvm and works in ppc64 full emulation though. 
Not very practical but it still can be used for debugging ppc64 drivers on 
real PCI hardware on x86 machine.


-- 
Alexey

      parent reply	other threads:[~2012-07-28  2:55 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 17:03 [RFC PATCH] vfio: VFIO PCI driver for Qemu Alex Williamson
2012-07-25 17:03 ` [Qemu-devel] " Alex Williamson
2012-07-25 19:30 ` Avi Kivity
2012-07-25 19:30   ` [Qemu-devel] " Avi Kivity
2012-07-25 19:53   ` Alex Williamson
2012-07-25 19:53     ` [Qemu-devel] " Alex Williamson
2012-07-26  8:35     ` Avi Kivity
2012-07-26  8:35       ` [Qemu-devel] " Avi Kivity
2012-07-26  9:28       ` Andreas Hartmann
2012-07-26  9:40         ` Avi Kivity
2012-07-26 13:45           ` Andreas Hartmann
2012-07-26 14:56       ` Alex Williamson
2012-07-26 14:56         ` [Qemu-devel] " Alex Williamson
2012-07-26 15:59         ` Avi Kivity
2012-07-26 15:59           ` [Qemu-devel] " Avi Kivity
2012-07-26 16:33           ` Alex Williamson
2012-07-26 16:33             ` [Qemu-devel] " Alex Williamson
2012-07-26 16:40             ` Avi Kivity
2012-07-26 16:40               ` [Qemu-devel] " Avi Kivity
2012-07-26 19:11               ` Alex Williamson
2012-07-26 21:23                 ` Andreas Hartmann
2012-07-26 21:37                   ` Alex Williamson
2012-07-26 16:06         ` Avi Kivity
2012-07-26 16:06           ` [Qemu-devel] " Avi Kivity
2012-07-26 16:40           ` Alex Williamson
2012-07-26 16:40             ` [Qemu-devel] " Alex Williamson
2012-07-26 16:47             ` Avi Kivity
2012-07-26 16:47               ` [Qemu-devel] " Avi Kivity
2012-07-26 15:09 ` Alex Williamson
2012-07-26 15:09   ` [Qemu-devel] " Alex Williamson
2012-07-26 16:34 ` Avi Kivity
2012-07-26 16:34   ` [Qemu-devel] " Avi Kivity
2012-07-26 17:40   ` Alex Williamson
2012-07-26 17:40     ` Alex Williamson
2012-07-29 13:47     ` Avi Kivity
2012-07-29 13:47       ` [Qemu-devel] " Avi Kivity
2012-07-30 22:29       ` Alex Williamson
2012-07-30 22:29         ` Alex Williamson
2012-07-31 12:34         ` Avi Kivity
2012-07-31 16:56           ` Alex Williamson
2012-07-31 16:56             ` [Qemu-devel] " Alex Williamson
2012-07-27 19:22 ` Blue Swirl
2012-07-27 19:22   ` Blue Swirl
2012-07-27 20:28   ` Alex Williamson
2012-07-27 20:28     ` Alex Williamson
2012-07-28  2:55   ` Alexey Kardashevskiy [this message]

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=501354BC.9060405@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=blauwirbel@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.