qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org, Marcel Apfelbaum <marcel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] allocate pci id for mdpy
Date: Thu, 26 Apr 2018 11:00:28 -0600	[thread overview]
Message-ID: <20180426110028.738cb2f1@w520.home> (raw)
In-Reply-To: <20180426184017-mutt-send-email-mst@kernel.org>

On Thu, 26 Apr 2018 18:40:40 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Thu, Apr 26, 2018 at 05:31:48PM +0200, Gerd Hoffmann wrote:
> > On Thu, Apr 26, 2018 at 06:10:48PM +0300, Michael S. Tsirkin wrote:  
> > > On Tue, Apr 24, 2018 at 08:38:57AM +0200, Gerd Hoffmann wrote:  
> > > > mdpy is a sample pci device for vfio-mdev.  Not (yet) merged upstream,
> > > > patch available here:
> > > > 
> > > > https://www.kraxel.org/cgit/linux/commit/?h=vfio-sample-display&id=6fd86cff3d7df38ab89625b16fdd6434b1c18749
> > > > 
> > > > Cc: Alex Williamson <alex.williamson@redhat.com>
> > > > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>  
> > > 
> > > Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> > > 
> > > I presume this should be merged together with the
> > > device implementation in qemu, or do you want this
> > > in tree sooner?  
> > 
> > There isn't a device implementation in qemu.  It's a mdev device
> > provided by the kernel.  Can be used with qemu using vfio. 
> 
> Why do we need a define in pci.h then?

Because we want to allocate the device ID rather than squat on an
unused one and risk that it later conflicts with an another device.  Do
we track device ID allocations from the RH vendor ID other than here in
QEMU?  Thanks,

Alex

  reply	other threads:[~2018-04-26 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24  6:38 [Qemu-devel] [PATCH] allocate pci id for mdpy Gerd Hoffmann
2018-04-26 15:10 ` Michael S. Tsirkin
2018-04-26 15:31   ` Gerd Hoffmann
2018-04-26 15:40     ` Michael S. Tsirkin
2018-04-26 17:00       ` Alex Williamson [this message]
2018-04-26 18:36         ` Michael S. Tsirkin
2018-04-27  6:18       ` Gerd Hoffmann

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=20180426110028.738cb2f1@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).