From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, maz@kernel.org, tglx@linutronix.de,
peterz@infradead.org, sgarzare@redhat.com,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH V2 1/5] virtio: use virtio_device_ready() in virtio_device_restore()
Date: Thu, 7 Apr 2022 14:19:00 +0800 [thread overview]
Message-ID: <be2dd73d-7394-20d0-fa2b-652fdaa5700f@redhat.com> (raw)
In-Reply-To: <20220406073803-mutt-send-email-mst@kernel.org>
在 2022/4/6 下午7:44, Michael S. Tsirkin 写道:
> patch had wrong mime type. I managed to extra it but pls fix.
>
>>
>> From: Stefano Garzarella <sgarzare@redhat.com>
>>
>> It will allows us
> will allow us
>
>> to do extension on virtio_device_ready() without
>> duplicating codes.
> code
>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> Cc: "Paul E. McKenney" <paulmck@kernel.org>
>> Cc: Marc Zyngier <maz@kernel.org>
>> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> drivers/virtio/virtio.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/virtio/virtio.c b/drivers/virtio/virtio.c
>> index 22f15f444f75..75c8d560bbd3 100644
>> --- a/drivers/virtio/virtio.c
>> +++ b/drivers/virtio/virtio.c
>> @@ -526,8 +526,9 @@ int virtio_device_restore(struct virtio_device *dev)
>> goto err;
>> }
>>
>> - /* Finally, tell the device we're all set */
>> - virtio_add_status(dev, VIRTIO_CONFIG_S_DRIVER_OK);
>> + /* If restore didn't do it, mark device DRIVER_OK ourselves. */
>> + if (!(dev->config->get_status(dev) & VIRTIO_CONFIG_S_DRIVER_OK))
>> + virtio_device_ready(dev);
>>
>> virtio_config_enable(dev);
> it's unfortunate that this adds an extra vmexit since virtio_device_ready
> calls get_status too.
>
> We now have:
>
> static inline
> void virtio_device_ready(struct virtio_device *dev)
> {
> unsigned status = dev->config->get_status(dev);
>
> BUG_ON(status & VIRTIO_CONFIG_S_DRIVER_OK);
> dev->config->set_status(dev, status | VIRTIO_CONFIG_S_DRIVER_OK);
> }
>
>
> I propose adding a helper and putting common code there.
Ok, let me fix it.
Thanks
>
>>
>> --
>> 2.25.1
next prev parent reply other threads:[~2022-04-07 6:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 8:35 [PATCH V2 0/5] rework on the IRQ hardening of virtio Jason Wang
2022-04-06 8:35 ` [PATCH V2 1/5] virtio: use virtio_device_ready() in virtio_device_restore() Jason Wang
2022-04-06 11:44 ` Michael S. Tsirkin
2022-04-07 6:19 ` Jason Wang [this message]
2022-04-06 8:35 ` [PATCH V2 2/5] virtio: use virtio_reset_device() when possible Jason Wang
2022-04-06 11:53 ` Michael S. Tsirkin
2022-04-06 8:35 ` [PATCH V2 3/5] virtio: introduce config op to synchronize vring callbacks Jason Wang
2022-04-06 11:59 ` Michael S. Tsirkin
2022-04-07 6:25 ` Jason Wang
2022-04-06 8:35 ` [PATCH V2 4/5] virtio-pci: implement synchronize_vqs() Jason Wang
2022-04-06 12:00 ` Michael S. Tsirkin
2022-04-06 13:04 ` Cornelia Huck
2022-04-06 15:31 ` Michael S. Tsirkin
2022-04-07 6:38 ` Jason Wang
2022-04-07 7:52 ` Cornelia Huck
2022-04-07 8:04 ` Jason Wang
2022-04-08 13:03 ` Halil Pasic
2022-04-10 7:51 ` Michael S. Tsirkin
2022-04-11 8:22 ` Jason Wang
2022-04-11 8:56 ` Michael S. Tsirkin
2022-04-12 2:21 ` Jason Wang
2022-04-11 14:27 ` Cornelia Huck
2022-04-12 0:01 ` Halil Pasic
2022-04-12 2:24 ` Jason Wang
2022-04-12 7:55 ` Halil Pasic
2022-04-12 16:48 ` Cornelia Huck
2022-04-13 2:53 ` Jason Wang
2022-04-13 6:41 ` Cornelia Huck
2022-04-06 8:35 ` [PATCH V2 5/5] virtio: harden vring IRQ Jason Wang
2022-04-06 12:04 ` Michael S. Tsirkin
2022-04-07 6:39 ` Jason Wang
2022-04-06 11:36 ` [PATCH V2 0/5] rework on the IRQ hardening of virtio Michael S. Tsirkin
2022-04-07 6:12 ` Jason Wang
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=be2dd73d-7394-20d0-fa2b-652fdaa5700f@redhat.com \
--to=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mst@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sgarzare@redhat.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®