From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
davidel@xmailserver.org
Subject: Re: [KVM PATCH v6 3/4] KVM: Fix races in irqfd using new eventfd_kref_get interface
Date: Wed, 01 Jul 2009 12:44:39 +0300 [thread overview]
Message-ID: <4A4B3007.7080303@redhat.com> (raw)
In-Reply-To: <4A48F148.5030501@novell.com>
On 06/29/2009 07:52 PM, Gregory Haskins wrote:
>
>> One idea I had to make it even clearer was to have a shutdown list
>> of irqfds per-kvm, together with the items list, and make work_struct for
>> shutdown global, not per-irqfd. We can then unconditionally do
>> list_move + schedule_work to shut down an irqfd, and it's safe to do
>> even if it is already on the shutdown list - it just gets moved to tail.
>>
>>
>
> Hmm..I'm not sure that churn really buys us anything, tho. Technically
> the "active" bit is redundant with list_del_init()+list_empty() that I
> employed in previous versions. However, I made it explicit with the
> active bit to be more self-documenting. IMO, the latest code is pretty
> clear, and the change you are proposing is moving towards a slightly
> trickier variant like I originally had. I'd say "lets leave this as is".
>
Could retain self documentation by introducing a helper irqfd_active()
which does the list_blah() magic.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-01 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 15:43 [KVM PATCH v6 0/4] irqfd fixes and enhancements Gregory Haskins
2009-06-29 15:44 ` [KVM PATCH v6 1/4] kvm: prepare irqfd for having interrupts disabled during eventfd->release Gregory Haskins
2009-06-29 15:44 ` [KVM PATCH v6 2/4] eventfd - revised interface and cleanups (4th rev) Gregory Haskins
2009-06-29 15:44 ` [KVM PATCH v6 3/4] KVM: Fix races in irqfd using new eventfd_kref_get interface Gregory Haskins
2009-06-29 16:11 ` Michael S. Tsirkin
2009-06-29 16:52 ` Gregory Haskins
2009-06-29 17:32 ` Michael S. Tsirkin
2009-07-01 9:44 ` Avi Kivity [this message]
2009-06-29 15:44 ` [KVM PATCH v6 4/4] KVM: add irqfd DEASSIGN feature Gregory Haskins
2009-06-29 16:16 ` Michael S. Tsirkin
2009-06-29 15:46 ` [KVM PATCH v6 0/4] irqfd fixes and enhancements Gregory Haskins
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=4A4B3007.7080303@redhat.com \
--to=avi@redhat.com \
--cc=davidel@xmailserver.org \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox