From: Yan Zhao <yan.y.zhao@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] VFIO mdev aggregated resources handling
Date: Wed, 8 Jul 2020 11:38:46 +0800 [thread overview]
Message-ID: <20200708033845.GB20022@joy-OptiPlex-7040> (raw)
In-Reply-To: <20200708015419.GM27035@zhen-hp.sh.intel.com>
On Wed, Jul 08, 2020 at 09:54:19AM +0800, Zhenyu Wang wrote:
> On 2020.07.07 19:06:34 -0600, Alex Williamson wrote:
> > On Tue, 7 Jul 2020 23:28:39 +0000
> > "Tian, Kevin" <kevin.tian@intel.com> wrote:
> >
> > > Hi, Alex,
> > >
> > > Gentle ping... Please let us know whether this version looks good.
> >
> > I figured this is entangled with the versioning scheme. There are
> > unanswered questions about how something that assumes a device of a
> > given type is software compatible to another device of the same type
> > handles aggregation and how the type class would indicate compatibility
> > with an aggregated instance. Thanks,
> >
>
> +Yan
>
> Alex, If no concern on aggregated resources info for instance that would
> be vendor's behavior to determine what type of resources would be aggregated,
> then I'll check with Yan to see how to fulfill this during migration.
>
> Thanks
>
hi zhenyu and Alex
currently in this series, it looks that aggregated instances are created
in this way:
echo "<uuid>,aggregate=10" > create
Is that possible that we change it like that:
1. provide a separate attribute named "aggregator" under mdev type.
|- [parent physical device]
|--- Vendor-specific-attributes [optional]
|--- [mdev_supported_types]
| |--- [<type-id>]
| | |--- create
+ | | |--- aggregator
| | |--- name
| | |--- available_instances
| | |--- device_api
| | |--- description
| | |--- [devices]
normally, the aggregator is read as 0.
2. when we want to create an aggregated instance, we first echo the count
into the aggregator attribute. e.g.
echo 10 > aggregator
It will switch the mdev type to 10 x original_type. And then,
available_instances and description would be updated accordingly.
3. do the real mdev creation.
echo <uuid> > create
In this way, before any instance is created, we can use the
migration_version attribute to test if two aggregation mdevs are
migration compatible.
Thanks
Yan
next prev parent reply other threads:[~2020-07-08 3:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 5:41 [PATCH v2 0/2] VFIO mdev aggregated resources handling Zhenyu Wang
2020-03-26 5:41 ` [PATCH v2 1/2] Documentation/driver-api/vfio-mediated-device.rst: update for aggregation support Zhenyu Wang
2020-03-26 8:17 ` Tian, Kevin
2020-03-26 8:21 ` Zhenyu Wang
2020-03-27 6:16 ` Tian, Kevin
2020-03-27 6:21 ` Zhenyu Wang
2020-03-26 5:41 ` [PATCH v2 2/2] drm/i915/gvt: mdev aggregation type Zhenyu Wang
2020-03-27 7:48 ` Tian, Kevin
2020-03-27 8:12 ` Zhenyu Wang
2020-03-27 8:44 ` Tian, Kevin
2020-03-27 8:58 ` Zhenyu Wang
2020-03-27 9:31 ` Tian, Kevin
2020-04-08 5:58 ` [PATCH v3 0/2] VFIO mdev aggregated resources handling Zhenyu Wang
2020-07-07 23:28 ` Tian, Kevin
2020-07-08 1:06 ` Alex Williamson
2020-07-08 1:54 ` Zhenyu Wang
2020-07-08 3:38 ` Yan Zhao [this message]
2020-07-08 3:40 ` Yan Zhao
2020-07-08 4:17 ` Alex Williamson
2020-07-08 6:31 ` Tian, Kevin
2020-07-08 9:54 ` Zhenyu Wang
2020-07-08 18:48 ` Alex Williamson
2020-07-09 2:53 ` Tian, Kevin
2020-07-09 7:23 ` Yan Zhao
2020-07-09 20:22 ` Alex Williamson
2020-07-10 1:58 ` Yan Zhao
2020-07-10 15:00 ` Alex Williamson
2020-07-09 17:28 ` Alex Williamson
2020-07-10 2:09 ` Tian, Kevin
2020-07-10 6:29 ` Yan Zhao
2020-07-10 15:12 ` Alex Williamson
2020-07-13 0:59 ` Yan Zhao
2020-04-08 5:58 ` [PATCH v3 1/2] Documentation/driver-api/vfio-mediated-device.rst: update for aggregation support Zhenyu Wang
2020-04-08 5:58 ` [PATCH v3 2/2] drm/i915/gvt: mdev aggregation type Zhenyu Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200708033845.GB20022@joy-OptiPlex-7040 \
--to=yan.y.zhao@intel.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=zhenyuw@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).