From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v2] hw/virtio: Document *_should_notify() are called within rcu_read_lock()
Date: Tue, 6 Jul 2021 12:04:12 +0200 [thread overview]
Message-ID: <5711b02d-5cc0-414c-eb5c-4e8a7f191088@redhat.com> (raw)
In-Reply-To: <d3198f6b-3bce-1686-2123-e1c44479bdf9@redhat.com>
Hi Michael, since I asked a modification on v1, I suppose
this patch is somehow worth in documentation, so I'm
pinging again. It could go via qemu-trival if you ack it.
On 6/21/21 12:06 PM, Philippe Mathieu-Daudé wrote:
> ping?
>
> On 5/23/21 11:40 AM, Philippe Mathieu-Daudé wrote:
>> Such comments make reviewing this file somehow easier.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> v2: only one space before end of comment (mst)
>> ---
>> hw/virtio/virtio.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
>> index e02544b2df7..130e3568409 100644
>> --- a/hw/virtio/virtio.c
>> +++ b/hw/virtio/virtio.c
>> @@ -2449,6 +2449,7 @@ static void virtio_set_isr(VirtIODevice *vdev, int value)
>> }
>> }
>>
>> +/* Called within rcu_read_lock(). */
>> static bool virtio_split_should_notify(VirtIODevice *vdev, VirtQueue *vq)
>> {
>> uint16_t old, new;
>> @@ -2485,6 +2486,7 @@ static bool vring_packed_need_event(VirtQueue *vq, bool wrap,
>> return vring_need_event(off, new, old);
>> }
>>
>> +/* Called within rcu_read_lock(). */
>> static bool virtio_packed_should_notify(VirtIODevice *vdev, VirtQueue *vq)
>> {
>> VRingPackedDescEvent e;
>>
>
next prev parent reply other threads:[~2021-07-06 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 9:40 [PATCH v2] hw/virtio: Document *_should_notify() are called within rcu_read_lock() Philippe Mathieu-Daudé
2021-06-05 19:06 ` Laurent Vivier
2021-06-14 10:42 ` Philippe Mathieu-Daudé
2021-06-21 10:06 ` Philippe Mathieu-Daudé
2021-07-06 10:04 ` Philippe Mathieu-Daudé [this message]
2021-07-09 9:10 ` Laurent Vivier
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=5711b02d-5cc0-414c-eb5c-4e8a7f191088@redhat.com \
--to=philmd@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).