From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org, pugs@cisco.com,
chrisw@redhat.com
Subject: Re: [RFC PATCH 0/5] QEMU VFIO device assignment
Date: Mon, 12 Jul 2010 14:03:12 +0300 [thread overview]
Message-ID: <20100712110312.GA25835@redhat.com> (raw)
In-Reply-To: <4C3AB652.4000106@redhat.com>
On Mon, Jul 12, 2010 at 09:29:38AM +0300, Avi Kivity wrote:
> On 07/11/2010 11:24 PM, Alex Williamson wrote:
> >
> >One other thing to be aware of is that vfio requires devices to be
> >PCI-2.3 compliant in order to support DisINTx. This allows vfio to
> >support devices making use of shared INTx interrupts, but excludes older
> >devices that users maybe managed to get assigned to an exclusive
> >interrupt for kvm style assignment.
> >
> >I suppose we might be able to make vfio work with either pci 2.3 devices
> >or older devices with exclusive interrupts if that ends up affecting
> >many users.
>
> PCI 2.3 is already old enough (6-7 years?)
I believe it was made a standard in 2002.
> that I believe we can require it.
>
> --
> I have a truly marvellous patch that fixes the bug which this
> signature is too narrow to contain.
prev parent reply other threads:[~2010-07-12 11:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 18:09 [RFC PATCH 0/5] QEMU VFIO device assignment Alex Williamson
2010-07-11 18:09 ` [RFC PATCH 1/5] qemu_ram_map/unmap: Allow pre-allocated space to be mapped Alex Williamson
2010-07-11 18:09 ` [RFC PATCH 2/5] Minimal RAM API support Alex Williamson
2010-07-11 18:18 ` Alex Williamson
2010-07-11 18:20 ` Avi Kivity
2010-07-11 18:24 ` Alex Williamson
2010-07-11 18:29 ` Avi Kivity
2010-07-11 18:09 ` [RFC PATCH 3/5] RAM API: Make use of it for x86 PC Alex Williamson
2010-07-11 18:09 ` [RFC PATCH 4/5] APIC/IOAPIC EOI callback Alex Williamson
2010-07-11 18:14 ` Avi Kivity
2010-07-11 18:26 ` Alex Williamson
2010-07-11 18:30 ` Avi Kivity
2010-07-11 18:54 ` Michael S. Tsirkin
2010-07-11 19:21 ` Alex Williamson
2010-07-11 19:23 ` Michael S. Tsirkin
2010-07-11 20:03 ` Alex Williamson
2010-07-11 20:05 ` Michael S. Tsirkin
2010-07-11 20:12 ` Michael S. Tsirkin
2010-07-11 21:59 ` Alex Williamson
2010-07-12 6:33 ` Avi Kivity
2010-07-12 9:05 ` Gleb Natapov
2010-07-12 9:13 ` Avi Kivity
2010-07-11 18:09 ` [RFC PATCH 5/5] VFIO based device assignment Alex Williamson
2010-07-11 18:27 ` Avi Kivity
2010-07-11 19:38 ` Alex Williamson
2010-07-12 6:37 ` Avi Kivity
2010-07-11 18:17 ` [RFC PATCH 0/5] QEMU VFIO " Avi Kivity
2010-07-11 18:37 ` Alex Williamson
2010-07-11 18:43 ` Avi Kivity
2010-07-11 20:24 ` Alex Williamson
2010-07-12 6:29 ` Avi Kivity
2010-07-12 11:03 ` Michael S. Tsirkin [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=20100712110312.GA25835@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pugs@cisco.com \
--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