All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tian, Kevin" <kevin.tian@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>,
	Jason Wang <jasowang@redhat.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>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Wang, Zhi A" <zhi.a.wang@intel.com>,
	"farman@linux.ibm.com" <farman@linux.ibm.com>
Subject: RE: [RFC PATCH 0/2] Mdev: support mutiple kinds of devices
Date: Wed, 18 Sep 2019 01:54:43 +0000	[thread overview]
Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D19D57B260__13332.6614320808$1568771704$gmane$org@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190917113125.6b2970e5@x1.home>

> 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? :-)

Thanks
Kevin

  parent reply	other threads:[~2019-09-18  1:54 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12  9:40 [RFC PATCH 0/2] Mdev: support mutiple kinds of devices Jason Wang
2019-09-12  9:40 ` [RFC PATCH 1/2] mdev: device id support Jason Wang
2019-09-12  9:40 ` Jason Wang
2019-09-17  7:55   ` Tian, Kevin
2019-09-17  7:55     ` Tian, Kevin
2019-09-17  7:55     ` Tian, Kevin
2019-09-17 10:14     ` Jason Wang
2019-09-17 10:14     ` Jason Wang
2019-09-17 10:14       ` Jason Wang
2019-09-17 10:14       ` Jason Wang
2019-09-17  7:55   ` Tian, Kevin
2019-09-17 12:07   ` Cornelia Huck
2019-09-17 12:07     ` Cornelia Huck
2019-09-18  5:52     ` Jason Wang
2019-09-18  5:52       ` Jason Wang
2019-09-18  5:52     ` Jason Wang
2019-09-17 12:07   ` Cornelia Huck
2019-09-12  9:40 ` [RFC PATCH 2/2] mdev: introduce device specific ops Jason Wang
2019-09-12  9:40 ` Jason Wang
2019-09-12  9:51   ` Michael S. Tsirkin
2019-09-12  9:51     ` Michael S. Tsirkin
2019-09-12  9:51   ` Michael S. Tsirkin
2019-09-17  8:09   ` Tian, Kevin
2019-09-17  8:09     ` Tian, Kevin
2019-09-17  8:09     ` Tian, Kevin
2019-09-17 10:16     ` Jason Wang
2019-09-17 10:16       ` Jason Wang
2019-09-17 10:16       ` Jason Wang
2019-09-18  2:57       ` Tian, Kevin
2019-09-18  2:57       ` Tian, Kevin
2019-09-18  2:57         ` Tian, Kevin
2019-09-18  2:57         ` Tian, Kevin
2019-09-18  6:15         ` Jason Wang
2019-09-18  6:15           ` Jason Wang
2019-09-18  6:15           ` Jason Wang
2019-09-18  6:15         ` Jason Wang
2019-09-17 10:16     ` Jason Wang
2019-09-17 12:42   ` Cornelia Huck
2019-09-17 12:42   ` Cornelia Huck
2019-09-17 12:42     ` Cornelia Huck
2019-09-18  5:54     ` Jason Wang
2019-09-18  5:54       ` Jason Wang
2019-09-18  5:54     ` Jason Wang
2019-09-12 11:46 ` ✗ Fi.CI.CHECKPATCH: warning for Mdev: support mutiple kinds of devices Patchwork
2019-09-12 12:07 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-12 21:12 ` ✓ Fi.CI.IGT: " Patchwork
2019-09-17 17:31 ` [RFC PATCH 0/2] " Alex Williamson
2019-09-17 17:31   ` Alex Williamson
2019-09-18  1:54   ` Tian, Kevin
2019-09-18  2:23     ` Alex Williamson
2019-09-18  1:54   ` Tian, Kevin [this message]
2019-09-17 17:31 ` Alex Williamson
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='AADFC41AFE54684AB9EE6CBC0274A5D19D57B260__13332.6614320808$1568771704$gmane$org@SHSMSX104.ccr.corp.intel.com' \
    --to=kevin.tian@intel.com \
    --cc=airlied@linux.ie \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=farman@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jasowang@redhat.com \
    --cc=joonas.lahtinen@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.