From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-6686-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 4F596985F97 for ; Wed, 22 Jan 2020 11:10:41 +0000 (UTC) Date: Wed, 22 Jan 2020 06:10:27 -0500 From: "Michael S. Tsirkin" Message-ID: <20200122060844-mutt-send-email-mst@kernel.org> References: <20200122032103-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: Subject: Re: [virtio-dev][RFC PATCH v1 1/2] content: define what an exported object is Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: inline To: David Stevens Cc: Gerd Hoffmann , Dylan Reid , Tomasz Figa , Zach Reizner , Keiichi Watanabe , Alexandre Courbot , Alex Lau , =?iso-8859-1?Q?St=E9phane?= Marchesin , Pawel Osciak , Gurchetan Singh , Stefan Hajnoczi , qemu-devel , Linux Media Mailing List , virtio-dev@lists.oasis-open.org List-ID: On Wed, Jan 22, 2020 at 07:13:41PM +0900, David Stevens wrote: > > > +When an object created by one virtio device needs to be > > > +shared with a seperate virtio device, the first device can > > > +export the object by generating a \field{uuid} > > > > This is a field where? >=20 > It's a property of the exported object, but I guess it doesn't really > correspond to any concrete field. I'll remove \field. >=20 > > > which the > > > +guest can pass to the second device to identify the object. > > > > s/guest/Driver/ ? >=20 > The uuid can be passed to a second device controlled by a different > driver, so I think 'driver' by itself is ambiguous. I'm using guest as > a shorthand for 'system which includes the drivers and software which > sits on top of the drivers', and that meaning does seem to be > compatible with language in the rest of the spec. If that shorthand > isn't acceptable, I can rewrite the sentence passively as '... a uuid > which can then be passed to a second device ...'. >=20 > > Also - what are guest and host here? >=20 > There are a number of places in the virtio spec where 'guest' is used > to refer to the system where drivers run and where 'host' is used to > refer to the system where devices run. I guess those terms aren't > concretely defined within the spec, but they do seem to have a well > understood meaning. Or is the guest/host language discouraged in new > additions to the spec? >=20 > -David Yes - generally most devices are/should be implementable in hardware. In that setup guest/host doesn't make sense. We haven't reworked all of spec with that in mind yet, and in some cases such as the balloon it's actually specific to virtualization. --=20 MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org