linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: avi@redhat.com, gleb@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, jan.kiszka@siemens.com
Subject: Re: [PATCH v4 0/3] kvm: level irqfd and new eoifd
Date: Sun, 15 Jul 2012 19:45:17 +0300	[thread overview]
Message-ID: <20120715164517.GC17995@redhat.com> (raw)
In-Reply-To: <20120713192625.5474.60777.stgit@bling.home>

On Fri, Jul 13, 2012 at 01:40:48PM -0600, Alex Williamson wrote:
> v4:
>  - KVM_IRQFD_FLAG_LEVEL flag now documented and coded to only be
>    necessary on assign.
>  - Lock added to struct _irq_source to maintain the source ID assertion
>    state to avoid repeat assertions or spurious EOIs.  I couldn't figure
>    out a way to make this work w/o races using atomics and don't see any
>    way to make use of kvm_irq_line_state.

Well not kvm_irq_line_state specifically but what's the problem
with looking at irq_state in the correct pic? That is already
done atomically. We'll need new APIs for this of course.
See specific patch for suggestion.

>  - GSI support in KVM_EOIFD is dropped since it's not immediately used
>    and I don't seem to be able to explain why it's useful.  It makes it
>    optional though, which may be a good thing if other archs try to use
>    this interface.
>  - eoifd switch to mutex from spinlock (all tested as lockdep safe)
>  - _irqfd_fdget_lock/_irqfd_put_unlock replaces _irqfd_fdget/_irqfd_put
>    so we hold the lock for the irqfds ensuring the one we're binding to
>    doesn't go away while we get a reference to the _irq_source.
>  - We also pull the GSI off the irqfd rather than specifying it for eoifd.
>  - eoifd_deactivate renamed to eoifd_destroy to make it blindingly
>    obvious what it does.

Overall looks ok to me.
Looks like as written userspace can create any # of eoifds
with same irqfd leading to unlimited kernel memory use.
See specific patch for suggestion on how to fix.

> Patch 3/3 is not for commit and not meant to be ready for commit, it's
> just an FYI on what adding back support for a GSI based, non-de-asserting
> eoifd will look like.  Thanks,
> 
> Alex
> 
> ---
> 
> Alex Williamson (3):
>       kvm: Add a GSI specification for KVM_EOIFD
>       kvm: KVM_EOIFD, an eventfd for EOIs
>       kvm: Extend irqfd to support level interrupts
> 
> 
>  Documentation/virtual/kvm/api.txt |   27 +++
>  arch/x86/kvm/x86.c                |    3 
>  include/linux/kvm.h               |   24 +++
>  include/linux/kvm_host.h          |   13 +
>  virt/kvm/eventfd.c                |  349 +++++++++++++++++++++++++++++++++++++
>  virt/kvm/kvm_main.c               |   11 +
>  6 files changed, 423 insertions(+), 4 deletions(-)

      parent reply	other threads:[~2012-07-15 16:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 19:40 [PATCH v4 0/3] kvm: level irqfd and new eoifd Alex Williamson
2012-07-13 19:40 ` [PATCH v4 1/3] kvm: Extend irqfd to support level interrupts Alex Williamson
2012-07-13 19:41 ` [PATCH v4 2/3] kvm: KVM_EOIFD, an eventfd for EOIs Alex Williamson
2012-07-15 16:23   ` Michael S. Tsirkin
2012-07-15 16:32   ` Michael S. Tsirkin
2012-07-16 15:01     ` Alex Williamson
2012-07-13 19:41 ` [PATCH v4 3/3] kvm: Add a GSI specification for KVM_EOIFD Alex Williamson
2012-07-15 16:45 ` 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=20120715164517.GC17995@redhat.com \
    --to=mst@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).