All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Amit Shah <amit.shah@redhat.com>,
	kvm@vger.kernel.org, weidong.han@intel.com,
	allen.m.kay@intel.com, muli@il.ibm.com, benami@il.ibm.com
Subject: Re: [PATCH 5/6] KVM/userspace: Device Assignment: Support for assigning PCI devices to guests
Date: Sun, 26 Oct 2008 14:54:02 +0200	[thread overview]
Message-ID: <4904686A.9030705@redhat.com> (raw)
In-Reply-To: <4901F658.5080501@codemonkey.ws>

Anthony Liguori wrote:
>
> I don't think having a kvm_enabled() check here is very useful.  I 
> think device-assignment.c should be conditional on USE_KVM, and the 
> only kvm_enabled() check should be when creating the initial device 
> assignment.  Practically speaking, QEMU is never going to support 
> device assignment outside of the context of KVM because I strongly 
> doubt anything like irqhook will make it upstream.

Userspace interrupt handlers are actually possible with MSI; we should 
see if uio is open to adding support for that.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-10-26 12:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 15:26 [v7] Userspace patches for PCI device assignment Amit Shah
2008-10-24 15:26 ` [PATCH 1/6] KVM/userspace: Device Assignment: Add ioctl wrappers needed for assigning devices Amit Shah
2008-10-24 15:26   ` [PATCH 2/6] qemu: Introduce pci_map_irq to get irq nr from pin number for a PCI device Amit Shah
2008-10-24 15:26     ` [PATCH 3/6] qemu: piix: Introduce functions to get pin number from irq and vice versa Amit Shah
2008-10-24 15:26       ` [PATCH 4/6] KVM/userspace: Build vtd.c for Intel IOMMU support Amit Shah
2008-10-24 15:26         ` [PATCH 5/6] KVM/userspace: Device Assignment: Support for assigning PCI devices to guests Amit Shah
2008-10-24 15:26           ` [PATCH 6/6] KVM/userspace: Device Assignment: Support for hot plugging PCI devices Amit Shah
2008-10-24 16:22           ` [PATCH 5/6] KVM/userspace: Device Assignment: Support for assigning PCI devices to guests Anthony Liguori
2008-10-26 12:54             ` Avi Kivity [this message]
2008-10-28 10:11             ` Muli Ben-Yehuda
2008-10-27  1:28           ` Su, Disheng
2008-10-27  6:32             ` Han, Weidong
2008-10-28 10:12               ` Muli Ben-Yehuda
2008-10-26 13:31       ` [PATCH 3/6] qemu: piix: Introduce functions to get pin number from irq and vice versa Avi Kivity
2008-10-28 10:12         ` Muli Ben-Yehuda
2008-10-28 10:46           ` Avi Kivity
2008-10-28 15:44             ` Muli Ben-Yehuda
2008-10-28 16:21               ` Avi Kivity
2008-10-28 16:45                 ` Muli Ben-Yehuda
2008-10-26 13:29   ` [PATCH 1/6] KVM/userspace: Device Assignment: Add ioctl wrappers needed for assigning devices Avi Kivity
2008-10-28 10:13     ` Muli Ben-Yehuda
2008-10-24 15:59 ` [v7] Userspace patches for PCI device assignment Anthony Liguori
2008-10-28 10:13   ` Muli Ben-Yehuda

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=4904686A.9030705@redhat.com \
    --to=avi@redhat.com \
    --cc=allen.m.kay@intel.com \
    --cc=amit.shah@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=benami@il.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=weidong.han@intel.com \
    /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.