Re: [PATCH RFC 05/15] vhost-user: add memory_isolation to VhostUserState

--GRVu7jzoCipJ+wdN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 23, 2026 at 03:30:04PM -0700, Connor Kite wrote:
> @@ -73,12 +74,14 @@ typedef struct VhostUserState {
>      int memory_slots;
>      bool supports_config;
>      bool supports_inflight_migration;
> +    bool memory_isolation;
>  } VhostUserState;
> =20
>  /**
>   * vhost_user_init() - initialise shared vhost_user state
>   * @user: allocated area for storing shared state
>   * @chr: the chardev for the vhost socket
> + * @memory_isolation: disables device access to guest memory

"Device" is confusing because it has several meanings. "vhost-user
back-end" would be clearer.

"Disables" is also a little confusing because the vhost-user back-end
still needs to access guest memory somehow. Memory access cannot be
completely disabled. Something like "restricts vhost-user back-end
access to guest memory via bounce buffers" could be clearer, but it's up
to you. We probably don't want to repeat the full explanation in every
comment about memory isolation, so it's fine to omit the details as long
as there is user-facing documentation somewhere that explains what the
feature does.

--GRVu7jzoCipJ+wdN
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEhpWov9P5fNqsNXdanKSrs4Grc8gFAmpnrBwACgkQnKSrs4Gr
c8g/dggAh1YcQjd3Z68P3Ps7X5qBR06hLTnzCcvxJcgUdkL/zhk2JRB8QNKknhvW
S3BgaUom6aHcIvbo510pR/Y/IH0TqPU/IqKKwCRMS801ifd0K+Ma34s99i3vislo
vq5zrfcfMuyWUKb3KFaiiwGpoRSIEMon+jyZvB2UxU+bfRvRvVDN1wP/1Wn+TsDK
QRVDqg8Gzy4fWGB9YvM+OV6efVcOtLCTdzOLb/TVAFaxG0nJ3529x49lQHG5Myv+
i91ha0m/yl1XM/YMcTwIi8/ptgMgtPdqJPh8fSuU9d03ej4OM7bRsRkowrHE0+eq
F+92L+IMyU7aR8Y1A1vdhcakQZ2IBw==
=3u2s
-----END PGP SIGNATURE-----

--GRVu7jzoCipJ+wdN--