From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cornelia Huck Subject: Re: [libvirt] [PATCH v2 4/4] Documentation/vfio-mediated-device.txt: update for aggregation attribute Date: Fri, 27 Jul 2018 13:49:15 +0200 Message-ID: <20180727134915.0b904c88.cohuck@redhat.com> References: <20180620074039.10539-1-zhenyuw@linux.intel.com> <20180720021928.15343-1-zhenyuw@linux.intel.com> <20180720021928.15343-5-zhenyuw@linux.intel.com> <20180726174640.581f62bc.cohuck@redhat.com> <20180727021658.GN1267@zhen-hp.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kevin.tian@intel.com, kvm@vger.kernel.org, libvirt-list@redhat.com, kwankhede@nvidia.com, intel-gvt-dev@lists.freedesktop.org To: Zhenyu Wang Return-path: In-Reply-To: <20180727021658.GN1267@zhen-hp.sh.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com List-Id: kvm.vger.kernel.org On Fri, 27 Jul 2018 10:16:58 +0800 Zhenyu Wang wrote: > On 2018.07.26 17:46:40 +0200, Cornelia Huck wrote: > > On Fri, 20 Jul 2018 10:19:28 +0800 > > Zhenyu Wang wrote: > > > > > Update mdev doc on new aggregration attribute and instances attribute > > > for mdev. > > > > > > Cc: Kirti Wankhede > > > Cc: Alex Williamson > > > Cc: Kevin Tian > > > Signed-off-by: Zhenyu Wang > > > --- > > > Documentation/vfio-mediated-device.txt | 39 ++++++++++++++++++++++---- > > > 1 file changed, 33 insertions(+), 6 deletions(-) > > > > > > diff --git a/Documentation/vfio-mediated-device.txt b/Documentation/vfio-mediated-device.txt > > > index c3f69bcaf96e..9ec9495dcbe7 100644 > > > --- a/Documentation/vfio-mediated-device.txt > > > +++ b/Documentation/vfio-mediated-device.txt > > > @@ -211,12 +211,20 @@ Directories and files under the sysfs for Each Physical Device > > > | | |--- description > > > | | |--- [devices] > > > | |--- [] > > > - | |--- create > > > - | |--- name > > > - | |--- available_instances > > > - | |--- device_api > > > - | |--- description > > > - | |--- [devices] > > > + | | |--- create > > > + | | |--- name > > > + | | |--- available_instances > > > + | | |--- device_api > > > + | | |--- description > > > + | | |--- [devices] > > > + | |--- [] > > > + | | |--- create > > > + | | |--- name > > > + | | |--- available_instances > > > + | | |--- device_api > > > + | | |--- description > > > + | | |--- > > > + | | |--- [devices] > > > > > > * [mdev_supported_types] > > > > > > @@ -260,6 +268,19 @@ Directories and files under the sysfs for Each Physical Device > > > This attribute should show brief features/description of the type. This is > > > optional attribute. > > > > > > +* > > > + > > > + The description is to show feature for one instance of the type. > > > > You are talking about "one instance" here. Can this be different for > > the same type with different physical devices? > > > > I would expect for normal mdev types, driver might expose like x2, x4, x8 types > which split hw resource equally. But for type with aggregation feature, it can > set user wanted number of instances. Sorry maybe my use of word was not clear, how > about "one example of type"? Maybe my question was confusing as well... is an attribute that is exposed for a particular type under a particular physical device. - If is always the same for that particular type, regardless of which physical device we're dealing with, let's just drop the "one instance" sentence. - If it instead depends on what physical device we're handling, I'd write something like "The contents of this attribute depend both on the type and on the particular instance."