From: Alex Williamson <alex.williamson@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, pugs@cisco.com,
chrisw@redhat.com, mst@redhat.com
Subject: Re: [RFC PATCH 4/5] APIC/IOAPIC EOI callback
Date: Sun, 11 Jul 2010 12:26:24 -0600 [thread overview]
Message-ID: <1278872784.20397.18.camel@x201> (raw)
In-Reply-To: <4C3A09F3.8010304@redhat.com>
On Sun, 2010-07-11 at 21:14 +0300, Avi Kivity wrote:
> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > For device assignment, we need to know when the VM writes an end
> > of interrupt to the APIC, which allows us to de-assert the interrupt
> > line and clear the DisINTx bit. Add a new wrapper for ioapic
> > generated interrupts with a callback on eoi and create an interface
> > for drivers to be notified on eoi.
> >
>
> You aren't going to get this with kvm's in-kernel irqchip, so we need a
> new interface there.
Registering an eventfd for the eoi seems like a reasonable alternative.
I also need to figure out how to avoid bouncing the vfio interrupt
events through qemu, but it's a functional start. Thanks,
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: chrisw@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
kvm@vger.kernel.org, pugs@cisco.com
Subject: [Qemu-devel] Re: [RFC PATCH 4/5] APIC/IOAPIC EOI callback
Date: Sun, 11 Jul 2010 12:26:24 -0600 [thread overview]
Message-ID: <1278872784.20397.18.camel@x201> (raw)
In-Reply-To: <4C3A09F3.8010304@redhat.com>
On Sun, 2010-07-11 at 21:14 +0300, Avi Kivity wrote:
> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > For device assignment, we need to know when the VM writes an end
> > of interrupt to the APIC, which allows us to de-assert the interrupt
> > line and clear the DisINTx bit. Add a new wrapper for ioapic
> > generated interrupts with a callback on eoi and create an interface
> > for drivers to be notified on eoi.
> >
>
> You aren't going to get this with kvm's in-kernel irqchip, so we need a
> new interface there.
Registering an eventfd for the eoi seems like a reasonable alternative.
I also need to figure out how to avoid bouncing the vfio interrupt
events through qemu, but it's a functional start. Thanks,
Alex
next prev parent reply other threads:[~2010-07-11 18:26 UTC|newest]
Thread overview: 64+ 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 ` [Qemu-devel] " 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 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:09 ` [RFC PATCH 2/5] Minimal RAM API support Alex Williamson
2010-07-11 18:09 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:18 ` Alex Williamson
2010-07-11 18:18 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:20 ` Avi Kivity
2010-07-11 18:20 ` [Qemu-devel] " Avi Kivity
2010-07-11 18:24 ` Alex Williamson
2010-07-11 18:24 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:29 ` Avi Kivity
2010-07-11 18:29 ` [Qemu-devel] " 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 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:09 ` [RFC PATCH 4/5] APIC/IOAPIC EOI callback Alex Williamson
2010-07-11 18:09 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:14 ` Avi Kivity
2010-07-11 18:14 ` [Qemu-devel] " Avi Kivity
2010-07-11 18:26 ` Alex Williamson [this message]
2010-07-11 18:26 ` Alex Williamson
2010-07-11 18:30 ` Avi Kivity
2010-07-11 18:30 ` [Qemu-devel] " Avi Kivity
2010-07-11 18:54 ` Michael S. Tsirkin
2010-07-11 18:54 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-11 19:21 ` Alex Williamson
2010-07-11 19:21 ` [Qemu-devel] " Alex Williamson
2010-07-11 19:23 ` Michael S. Tsirkin
2010-07-11 19:23 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-11 20:03 ` Alex Williamson
2010-07-11 20:03 ` [Qemu-devel] " Alex Williamson
2010-07-11 20:05 ` Michael S. Tsirkin
2010-07-11 20:05 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-11 20:12 ` Michael S. Tsirkin
2010-07-11 20:12 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-11 21:59 ` Alex Williamson
2010-07-11 21:59 ` [Qemu-devel] " Alex Williamson
2010-07-12 6:33 ` Avi Kivity
2010-07-12 6:33 ` [Qemu-devel] " Avi Kivity
2010-07-12 9:05 ` Gleb Natapov
2010-07-12 9:05 ` [Qemu-devel] " Gleb Natapov
2010-07-12 9:13 ` Avi Kivity
2010-07-12 9:13 ` [Qemu-devel] " Avi Kivity
2010-07-11 18:09 ` [RFC PATCH 5/5] VFIO based device assignment Alex Williamson
2010-07-11 18:09 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:27 ` Avi Kivity
2010-07-11 18:27 ` [Qemu-devel] " Avi Kivity
2010-07-11 19:38 ` Alex Williamson
2010-07-11 19:38 ` [Qemu-devel] " Alex Williamson
2010-07-12 6:37 ` Avi Kivity
2010-07-12 6:37 ` [Qemu-devel] " Avi Kivity
2010-07-11 18:17 ` [RFC PATCH 0/5] QEMU VFIO " Avi Kivity
2010-07-11 18:17 ` [Qemu-devel] " Avi Kivity
2010-07-11 18:37 ` Alex Williamson
2010-07-11 18:37 ` [Qemu-devel] " Alex Williamson
2010-07-11 18:43 ` Avi Kivity
2010-07-11 18:43 ` [Qemu-devel] " Avi Kivity
2010-07-11 20:24 ` Alex Williamson
2010-07-11 20:24 ` [Qemu-devel] " Alex Williamson
2010-07-12 6:29 ` Avi Kivity
2010-07-12 6:29 ` [Qemu-devel] " Avi Kivity
2010-07-12 11:03 ` Michael S. Tsirkin
2010-07-12 11:03 ` [Qemu-devel] " Michael S. Tsirkin
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=1278872784.20397.18.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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 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.