All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirti Wankhede <kwankhede@nvidia.com>
To: <alex.williamson@redhat.com>, <dgilbert@redhat.com>
Cc: mgurtovoy@nvidia.com, yishaih@nvidia.com, cjia@nvidia.com,
	cohuck@redhat.com, qemu-devel@nongnu.org, dnigam@nvidia.com,
	Jason Gunthorpe <jgg@nvidia.com>,
	targupta@nvidia.com
Subject: Re: [PATCH v1 1/1] vfio/migration: Correct device state from vmstate change for savevm case.
Date: Fri, 18 Jun 2021 16:14:33 +0530	[thread overview]
Message-ID: <00b57c95-98aa-3543-8d4a-369ae5efea00@nvidia.com> (raw)
In-Reply-To: <1623177441-27496-1-git-send-email-kwankhede@nvidia.com>

CCing more Nvidia folks who are testing this patch.

Gentle Ping for review.

Thanks,
Kirti


On 6/9/2021 12:07 AM, Kirti Wankhede wrote:
> Set _SAVING flag for device state from vmstate change handler when it gets
> called from savevm.
> 
> Currently State transition savevm/suspend is seen as:
>      _RUNNING -> _STOP -> Stop-and-copy -> _STOP
> 
> State transition savevm/suspend should be:
>      _RUNNING -> Stop-and-copy -> _STOP
> 
> State transition from _RUNNING to _STOP occurs from vfio_vmstate_change()
> where when vmstate changes from running to !running, _RUNNING flag is reset
> but at the same time when vfio_vmstate_change() is called for
> RUN_STATE_SAVE_VM, _SAVING bit should be set.
> 
> Reported by: Yishai Hadas <yishaih@nvidia.com>
> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
> ---
>   hw/vfio/migration.c | 11 ++++++++++-
>   1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/hw/vfio/migration.c b/hw/vfio/migration.c
> index 384576cfc051..33242b2313b9 100644
> --- a/hw/vfio/migration.c
> +++ b/hw/vfio/migration.c
> @@ -725,7 +725,16 @@ static void vfio_vmstate_change(void *opaque, bool running, RunState state)
>            * _RUNNING bit
>            */
>           mask = ~VFIO_DEVICE_STATE_RUNNING;
> -        value = 0;
> +
> +        /*
> +         * When VM state transition to stop for savevm command, device should
> +         * start saving data.
> +         */
> +        if (state == RUN_STATE_SAVE_VM) {
> +            value = VFIO_DEVICE_STATE_SAVING;
> +        } else {
> +            value = 0;
> +        }
>       }
>   
>       ret = vfio_migration_set_state(vbasedev, mask, value);
> 


      reply	other threads:[~2021-06-18 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 18:37 [PATCH v1 1/1] vfio/migration: Correct device state from vmstate change for savevm case Kirti Wankhede
2021-06-18 10:44 ` Kirti Wankhede [this message]

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=00b57c95-98aa-3543-8d4a-369ae5efea00@nvidia.com \
    --to=kwankhede@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=dnigam@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=mgurtovoy@nvidia.com \
    --cc=qemu-devel@nongnu.org \
    --cc=targupta@nvidia.com \
    --cc=yishaih@nvidia.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.