All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: gleb@redhat.com, mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCHv0 RFC] kvm: irqfd support for level interrupts
Date: Wed, 19 Aug 2009 15:20:21 +0300	[thread overview]
Message-ID: <4A8BEE05.1000105@redhat.com> (raw)
In-Reply-To: <20090726162225.GA21972@redhat.com>

On 07/26/2009 07:22 PM, Michael S. Tsirkin wrote:
> Here's an untested patch with partial support for level triggered
> interrupts in irqfd. What this patch has: support for clearing interrupt
> on ack. What this patch does not have: support signalling eventfd on ack
> so that userspace can take action and e.g. reenable interrupt.
>
> Gleb, Marcelo, I'd like your input on the approach taken wrt locking.
> Does it look sane?
>
> Avi, how's the interface? I intend to also add an eventfd probably in
> the padding in the irqfd struct.
>    

What about the state-capable eventfd?  Seems much more natural for this.

>
>   static struct workqueue_struct *irqfd_cleanup_wq;
> @@ -63,10 +65,15 @@ irqfd_inject(struct work_struct *work)
>
>   	mutex_lock(&kvm->irq_lock);
>   	kvm_set_irq(kvm, KVM_USERSPACE_IRQ_SOURCE_ID, irqfd->gsi, 1);
> -	kvm_set_irq(kvm, KVM_USERSPACE_IRQ_SOURCE_ID, irqfd->gsi, 0);
> +	if (!irqfd->is_level)
> +		kvm_set_irq(kvm, KVM_USERSPACE_IRQ_SOURCE_ID, irqfd->gsi, 0);
>    

e.g. inject the eventfd->state as the irq level.

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


  parent reply	other threads:[~2009-08-19 12:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26 16:22 [PATCHv0 RFC] kvm: irqfd support for level interrupts Michael S. Tsirkin
2009-07-27  5:33 ` Gleb Natapov
2009-07-27  6:28   ` Michael S. Tsirkin
2009-07-27  7:31     ` Gleb Natapov
2009-07-27  8:02       ` Michael S. Tsirkin
2009-07-27  8:13         ` Gleb Natapov
2009-07-27  8:21           ` Michael S. Tsirkin
2009-07-27  8:30             ` Gleb Natapov
2009-08-19 12:17   ` Avi Kivity
2009-07-29 16:01 ` Gregory Haskins
2009-07-29 16:03   ` Gregory Haskins
2009-08-19 12:20 ` Avi Kivity [this message]
2009-08-19 13:09   ` 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=4A8BEE05.1000105@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.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.