From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: qemu-devel@nongnu.org, fam@euphon.net, berrange@redhat.com,
f4bug@amsat.org, aurelien@aurel32.net, pbonzini@redhat.com,
stefanha@redhat.com, crosa@redhat.com,
"Michael S. Tsirkin" <mst@redhat.com>,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
"open list:Block layer core" <qemu-block@nongnu.org>,
"open list:virtiofs" <virtio-fs@redhat.com>
Subject: Re: [Virtio-fs] [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start
Date: Mon, 14 Nov 2022 16:43:47 +0000 [thread overview]
Message-ID: <8735albi3h.fsf@linaro.org> (raw)
In-Reply-To: <2277569a-c218-30d1-4d88-9b77d3604513@linux.ibm.com>
Christian Borntraeger <borntraeger@linux.ibm.com> writes:
> Am 08.11.22 um 10:23 schrieb Alex Bennée:
>> The previous fix to virtio_device_started revealed a problem in its
>> use by both the core and the device code. The core code should be able
>> to handle the device "starting" while the VM isn't running to handle
>> the restoration of migration state. To solve this dual use introduce a
>> new helper for use by the vhost-user backends who all use it to feed a
>> should_start variable.
>> We can also pick up a change vhost_user_blk_set_status while we are
>> at
>> it which follows the same pattern.
>> Fixes: 9f6bcfd99f (hw/virtio: move vm_running check to
>> virtio_device_started)
>> Fixes: 27ba7b027f (hw/virtio: add boilerplate for vhost-user-gpio device)
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Cc: "Michael S. Tsirkin" <mst@redhat.com>
>
> Hmmm, is this
> commit 259d69c00b67c02a67f3bdbeeea71c2c0af76c35
> Author: Alex Bennée <alex.bennee@linaro.org>
> AuthorDate: Mon Nov 7 12:14:07 2022 +0000
> Commit: Michael S. Tsirkin <mst@redhat.com>
> CommitDate: Mon Nov 7 14:08:18 2022 -0500
>
> hw/virtio: introduce virtio_device_should_start
>
> and older version?
Only missing the additional Fixes line MST suggested in the review. I
should have made it clearer in the --- comment.
Which test is failing?
--
Alex Bennée
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: qemu-devel@nongnu.org, fam@euphon.net, berrange@redhat.com,
f4bug@amsat.org, aurelien@aurel32.net, pbonzini@redhat.com,
stefanha@redhat.com, crosa@redhat.com,
"Michael S. Tsirkin" <mst@redhat.com>,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
"open list:Block layer core" <qemu-block@nongnu.org>,
"open list:virtiofs" <virtio-fs@redhat.com>
Subject: Re: [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start
Date: Mon, 14 Nov 2022 16:43:47 +0000 [thread overview]
Message-ID: <8735albi3h.fsf@linaro.org> (raw)
In-Reply-To: <2277569a-c218-30d1-4d88-9b77d3604513@linux.ibm.com>
Christian Borntraeger <borntraeger@linux.ibm.com> writes:
> Am 08.11.22 um 10:23 schrieb Alex Bennée:
>> The previous fix to virtio_device_started revealed a problem in its
>> use by both the core and the device code. The core code should be able
>> to handle the device "starting" while the VM isn't running to handle
>> the restoration of migration state. To solve this dual use introduce a
>> new helper for use by the vhost-user backends who all use it to feed a
>> should_start variable.
>> We can also pick up a change vhost_user_blk_set_status while we are
>> at
>> it which follows the same pattern.
>> Fixes: 9f6bcfd99f (hw/virtio: move vm_running check to
>> virtio_device_started)
>> Fixes: 27ba7b027f (hw/virtio: add boilerplate for vhost-user-gpio device)
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Cc: "Michael S. Tsirkin" <mst@redhat.com>
>
> Hmmm, is this
> commit 259d69c00b67c02a67f3bdbeeea71c2c0af76c35
> Author: Alex Bennée <alex.bennee@linaro.org>
> AuthorDate: Mon Nov 7 12:14:07 2022 +0000
> Commit: Michael S. Tsirkin <mst@redhat.com>
> CommitDate: Mon Nov 7 14:08:18 2022 -0500
>
> hw/virtio: introduce virtio_device_should_start
>
> and older version?
Only missing the additional Fixes line MST suggested in the review. I
should have made it clearer in the --- comment.
Which test is failing?
--
Alex Bennée
next prev parent reply other threads:[~2022-11-14 16:43 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 9:22 [PATCH v1 for 7.2 0/9] test and doc updates Alex Bennée
2022-11-08 9:23 ` [PATCH v1 1/9] Run docker probe only if docker or podman are available Alex Bennée
2022-11-08 9:23 ` [PATCH v1 2/9] tests/avocado: improve behaviour waiting for login prompts Alex Bennée
2022-11-08 11:23 ` Philippe Mathieu-Daudé
2022-11-08 21:19 ` John Snow
2022-11-08 9:23 ` [PATCH v1 3/9] tests/avocado/machine_aspeed.py: Reduce noise on the console for SDK tests Alex Bennée
2022-11-08 9:23 ` [PATCH v1 4/9] tests/docker: allow user to override check target Alex Bennée
2022-11-08 11:12 ` Philippe Mathieu-Daudé
2022-11-08 9:23 ` [Virtio-fs] [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start Alex Bennée
2022-11-08 9:23 ` Alex Bennée
2022-11-08 9:32 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-08 9:32 ` Michael S. Tsirkin
2022-11-08 10:23 ` [Virtio-fs] " Alex Bennée
2022-11-08 10:23 ` Alex Bennée
2022-11-08 10:26 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-08 10:26 ` Michael S. Tsirkin
2022-11-08 11:21 ` [Virtio-fs] " Alex Bennée
2022-11-08 11:21 ` Alex Bennée
2022-11-08 15:24 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-08 15:24 ` Michael S. Tsirkin
2022-11-08 16:41 ` [Virtio-fs] " Alex Bennée
2022-11-08 16:41 ` Alex Bennée
2022-11-08 9:33 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-08 9:33 ` Michael S. Tsirkin
2022-11-14 16:18 ` [Virtio-fs] " Christian Borntraeger
2022-11-14 16:18 ` Christian Borntraeger
2022-11-14 16:37 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-14 16:37 ` Michael S. Tsirkin
2022-11-14 16:55 ` [Virtio-fs] " Christian Borntraeger
2022-11-14 16:55 ` Christian Borntraeger
2022-11-14 17:10 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-14 17:10 ` Michael S. Tsirkin
2022-11-14 17:15 ` [Virtio-fs] " Christian Borntraeger
2022-11-14 17:15 ` Christian Borntraeger
2022-11-14 17:20 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-14 17:20 ` Michael S. Tsirkin
2022-11-15 7:44 ` [Virtio-fs] " Christian Borntraeger
2022-11-15 7:44 ` Christian Borntraeger
2022-11-15 8:18 ` [Virtio-fs] " Christian Borntraeger
2022-11-15 8:18 ` Christian Borntraeger
2022-11-15 9:05 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-15 9:05 ` Michael S. Tsirkin
2022-11-15 11:25 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-15 11:25 ` Michael S. Tsirkin
2022-11-15 13:25 ` [Virtio-fs] " Christian Borntraeger
2022-11-15 13:25 ` Christian Borntraeger
2022-11-15 14:31 ` [Virtio-fs] " Alex Bennée
2022-11-15 14:31 ` Alex Bennée
2022-11-15 15:09 ` [Virtio-fs] " Christian Borntraeger
2022-11-15 15:09 ` Christian Borntraeger
2022-11-15 16:05 ` [Virtio-fs] " Alex Bennée
2022-11-15 16:05 ` Alex Bennée
2022-11-15 16:40 ` [Virtio-fs] " Christian Borntraeger
2022-11-15 16:40 ` Christian Borntraeger
2022-11-15 16:46 ` [Virtio-fs] " Christian Borntraeger
2022-11-15 16:46 ` Christian Borntraeger
2022-11-21 22:37 ` [Virtio-fs] " Michael S. Tsirkin
2022-11-21 22:37 ` Michael S. Tsirkin
2022-11-23 6:27 ` [Virtio-fs] " Christian Borntraeger
2022-11-23 6:27 ` Christian Borntraeger
2022-11-14 16:43 ` Alex Bennée [this message]
2022-11-14 16:43 ` Alex Bennée
2022-11-08 9:23 ` [PATCH v1 6/9] docs/devel: add a maintainers section to development process Alex Bennée
2022-11-08 9:23 ` [PATCH v1 7/9] docs/devel: make language a little less code centric Alex Bennée
2022-11-08 9:23 ` [PATCH v1 8/9] docs/devel: simplify the minimal checklist Alex Bennée
2022-11-08 9:23 ` [PATCH v1 9/9] docs/devel: try and improve the language around patch review Alex Bennée
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=8735albi3h.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=crosa@redhat.com \
--cc=dgilbert@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mathieu.poirier@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=stefanha@redhat.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.