[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe02f34a-c3d9-056a-3081-58605e8e1247@huawei.com>
Date: Fri, 21 Apr 2023 11:07:53 +0800
From: liulongfang <liulongfang@...wei.com>
To: Jason Gunthorpe <jgg@...dia.com>
CC: <alex.williamson@...hat.com>,
<shameerali.kolothum.thodi@...wei.com>,
<jonathan.cameron@...wei.com>, <cohuck@...hat.com>,
<linux-kernel@...r.kernel.org>, <linuxarm@...neuler.org>
Subject: Re: [PATCH v10 5/5] vfio: update live migration device status
On 2023/4/14 20:25, Jason Gunthorpe write:
> On Sat, Apr 08, 2023 at 03:42:24PM +0800, Longfang Liu wrote:
>> migration debugfs needs to perform debug operations based on the
>> status of the current device. If the device is not loaded or has
>> stopped, debugfs does not allow operations.
>>
>> so, after the live migration function is executed and the device is
>> turned off, the device no longer needs to be accessed. At this time,
>> the status of the device needs to be set to stop.
>
> STOP means the devices isn't functioning
> > An idle device that has just been reset is RUNNING by definiton.
>
After the vfio device is opened, it will be set to RUNNING, and after it
is closed, it should be set to STOP according to the function of the device.
Or redefine an IDLE state?
Thanks,
Longfang.
> Jason
> .
>
Powered by blists - more mailing lists