qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: famz@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2] nvme: correct locking around completion
Date: Wed, 10 Oct 2018 13:19:56 +0200	[thread overview]
Message-ID: <da1cc131-0352-5fd8-8180-829d2f5d07ec@redhat.com> (raw)
In-Reply-To: <46af1836-e70a-185e-7312-e26fa57d1e2a@redhat.com>

On 09/10/2018 21:37, John Snow wrote:
> 
> 
> On 08/14/2018 02:27 AM, Paolo Bonzini wrote:
>> nvme_poll_queues is already protected by q->lock, and
>> AIO callbacks are invoked outside the AioContext lock.
>> So remove the acquire/release pair in nvme_handle_event.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>>  block/nvme.c | 2 --
>>  1 file changed, 2 deletions(-)
>>
>> diff --git a/block/nvme.c b/block/nvme.c
>> index 6f71122bf5..42116907ed 100644
>> --- a/block/nvme.c
>> +++ b/block/nvme.c
>> @@ -489,10 +489,8 @@ static void nvme_handle_event(EventNotifier *n)
>>      BDRVNVMeState *s = container_of(n, BDRVNVMeState, irq_notifier);
>>  
>>      trace_nvme_handle_event(s);
>> -    aio_context_acquire(s->aio_context);
>>      event_notifier_test_and_clear(n);
>>      nvme_poll_queues(s);
>> -    aio_context_release(s->aio_context);
>>  }
>>  
>>  static bool nvme_add_io_queue(BlockDriverState *bs, Error **errp)
>>
> 
> This is over a month old (and seemingly didn't land); do we still want it?
> 

Yes, we do.

Paolo

  reply	other threads:[~2018-10-10 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14  6:27 [Qemu-devel] [PATCH v2] nvme: correct locking around completion Paolo Bonzini
2018-08-14  6:45 ` Fam Zheng
2018-08-14  8:06   ` Paolo Bonzini
2018-10-09 19:37 ` [Qemu-devel] [Qemu-block] " John Snow
2018-10-10 11:19   ` Paolo Bonzini [this message]
2018-10-11  2:56     ` Fam Zheng
2018-10-11  2:58     ` Fam Zheng

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=da1cc131-0352-5fd8-8180-829d2f5d07ec@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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).