From: Alex Williamson <alex.williamson@redhat.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mst@redhat.com" <mst@redhat.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"joonas.lahtinen@linux.intel.com"
<joonas.lahtinen@linux.intel.com>,
"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"kwankhede@nvidia.com" <kwankhede@nvidia.com>,
"rob.miller@broadcom.com" <rob.miller@broadcom.com>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"sebott@linux.ibm.com" <sebott@linux.ibm.com>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
"borntraeger@de.ibm.com" <borntraeger@de.ibm.com>,
"Wang, Zhi A" <zhi.a.wang@intel.com>,
"farman@linux.ibm.com" <farman@linux.ibm.com>,
"idos@mellanox.com" <idos@mellanox.com>,
"gor@linux.ibm.com" <gor@linux.ibm.com>, intel-
Subject: Re: [RFC PATCH 0/2] Mdev: support mutiple kinds of devices
Date: Tue, 17 Sep 2019 20:23:55 -0600 [thread overview]
Message-ID: <20190917202355.50830aa2@x1.home> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D19D57B260@SHSMSX104.ccr.corp.intel.com>
On Wed, 18 Sep 2019 01:54:43 +0000
"Tian, Kevin" <kevin.tian@intel.com> wrote:
> > From: Alex Williamson
> > Sent: Wednesday, September 18, 2019 1:31 AM
> >
> > [cc +Parav]
> >
> > On Thu, 12 Sep 2019 17:40:10 +0800
> > Jason Wang <jasowang@redhat.com> wrote:
> >
> > > Hi all:
> > >
> > > During the development of virtio-mdev[1]. I find that mdev needs to be
> > > extended to support devices other than vfio mdev device. So this
> > > series tries to extend the mdev to be able to differ from different
> > > devices by:
> > >
> > > - device id and matching for mdev bus
> > > - device speicfic callbacks and move vfio callbacks there
> > >
> > > Sent for early reivew, compile test only!
> > >
> > > Thanks
> > >
> > > [1] https://lkml.org/lkml/2019/9/10/135
> >
> > I expect Parav must have something similar in the works for their
> > in-kernel networking mdev support. Link to discussion so far:
> >
> > https://lore.kernel.org/kvm/20190912094012.29653-1-
> > jasowang@redhat.com/T/#t
> >
>
> It links to the current thread. Is it intended or do you want
> people to look at another thread driven by Parav? :-)
Sorry, the link was provided for Parav since they weren't cc'd. Thanks,
Alex
next prev parent reply other threads:[~2019-09-18 2:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190912094012.29653-1-jasowang@redhat.com>
2019-09-12 9:40 ` [RFC PATCH 1/2] mdev: device id support Jason Wang
2019-09-12 9:40 ` [RFC PATCH 2/2] mdev: introduce device specific ops Jason Wang
[not found] ` <20190912094012.29653-2-jasowang@redhat.com>
2019-09-17 7:55 ` [RFC PATCH 1/2] mdev: device id support Tian, Kevin
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D19D579F2F@SHSMSX104.ccr.corp.intel.com>
2019-09-17 10:14 ` Jason Wang
2019-09-17 12:07 ` Cornelia Huck
[not found] ` <20190917140720.3686e0cc.cohuck@redhat.com>
2019-09-18 5:52 ` Jason Wang
[not found] ` <20190912094012.29653-3-jasowang@redhat.com>
2019-09-12 9:51 ` [RFC PATCH 2/2] mdev: introduce device specific ops Michael S. Tsirkin
2019-09-17 8:09 ` Tian, Kevin
2019-09-17 10:16 ` Jason Wang
[not found] ` <6bb2c43c-25bb-16f9-1fa0-08cb08e42b94@redhat.com>
2019-09-18 2:57 ` Tian, Kevin
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D19D57B49A@SHSMSX104.ccr.corp.intel.com>
2019-09-18 6:15 ` Jason Wang
2019-09-17 12:42 ` Cornelia Huck
[not found] ` <20190917144240.6a59b65f.cohuck@redhat.com>
2019-09-18 5:54 ` Jason Wang
2019-09-17 17:31 ` [RFC PATCH 0/2] Mdev: support mutiple kinds of devices Alex Williamson
[not found] ` <20190917113125.6b2970e5@x1.home>
2019-09-18 1:54 ` Tian, Kevin
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D19D57B260@SHSMSX104.ccr.corp.intel.com>
2019-09-18 2:23 ` Alex Williamson [this message]
2019-09-12 9:40 Jason 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=20190917202355.50830aa2@x1.home \
--to=alex.williamson@redhat.com \
--cc=airlied@linux.ie \
--cc=borntraeger@de.ibm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=farman@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=idos@mellanox.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=rob.miller@broadcom.com \
--cc=sebott@linux.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=zhi.a.wang@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