On Wed, 2012-08-15 at 17:05 +0300, Michael S. Tsirkin wrote:
> On Fri, Aug 10, 2012 at 04:37:48PM -0600, Alex Williamson wrote:
> > Enable a mechanism for IRQ ACKs to be exposed through an eventfd. The
> > user can specify the GSI and optionally an IRQ source ID and have the
> > provided eventfd
On Fri, Aug 10, 2012 at 04:37:48PM -0600, Alex Williamson wrote:
> Enable a mechanism for IRQ ACKs to be exposed through an eventfd. The
> user can specify the GSI and optionally an IRQ source ID and have the
> provided eventfd trigger whenever the irqchip resamples it's inputs,
> for instance on
On Fri, Aug 10, 2012 at 04:37:48PM -0600, Alex Williamson wrote:
Enable a mechanism for IRQ ACKs to be exposed through an eventfd. The
user can specify the GSI and optionally an IRQ source ID and have the
provided eventfd trigger whenever the irqchip resamples it's inputs,
for instance on
On Wed, 2012-08-15 at 17:05 +0300, Michael S. Tsirkin wrote:
On Fri, Aug 10, 2012 at 04:37:48PM -0600, Alex Williamson wrote:
Enable a mechanism for IRQ ACKs to be exposed through an eventfd. The
user can specify the GSI and optionally an IRQ source ID and have the
provided eventfd trigger
Enable a mechanism for IRQ ACKs to be exposed through an eventfd. The
user can specify the GSI and optionally an IRQ source ID and have the
provided eventfd trigger whenever the irqchip resamples it's inputs,
for instance on EOI.
Signed-off-by: Alex Williamson
---
Enable a mechanism for IRQ ACKs to be exposed through an eventfd. The
user can specify the GSI and optionally an IRQ source ID and have the
provided eventfd trigger whenever the irqchip resamples it's inputs,
for instance on EOI.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
6 matches
Mail list logo