[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/4] vhost: Re-enable vrings after setting features
|
From: |
Michael S. Tsirkin |
|
Subject: |
Re: [PATCH 1/4] vhost: Re-enable vrings after setting features |
|
Date: |
Thu, 13 Apr 2023 11:48:24 -0400 |
On Thu, Apr 13, 2023 at 05:24:36PM +0300, Anton Kuchin wrote:
> But is there a valid use-case for logging some dirty memory but not all?
> I can't understand if this is a feature or a just flaw in specification.
IRC the use-case originally conceived was for shadow VQs. If you use
shadow VQs the VQ access by backend does not change memory since shadow
VQ is not in memory. Not a practical concern right now but there you
have it.
--
MST
Re: [PATCH 1/4] vhost: Re-enable vrings after setting features, Stefan Hajnoczi, 2023/04/13
Re: [PATCH 1/4] vhost: Re-enable vrings after setting features, Michael S. Tsirkin, 2023/04/13
[PATCH 2/4] vhost-user: Interface for migration state transfer, Hanna Czenczek, 2023/04/11
- Re: [PATCH 2/4] vhost-user: Interface for migration state transfer, Stefan Hajnoczi, 2023/04/12
- Re: [PATCH 2/4] vhost-user: Interface for migration state transfer, Hanna Czenczek, 2023/04/13
- Re: [PATCH 2/4] vhost-user: Interface for migration state transfer, Stefan Hajnoczi, 2023/04/13
- Re: [PATCH 2/4] vhost-user: Interface for migration state transfer, Hanna Czenczek, 2023/04/13
- Re: [PATCH 2/4] vhost-user: Interface for migration state transfer, Stefan Hajnoczi, 2023/04/13
- Re: [PATCH 2/4] vhost-user: Interface for migration state transfer, Eugenio Perez Martin, 2023/04/14