linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, Dave Airlie <airlied@gmail.com>,
	Dave Airlie <airlied@redhat.com>, David Airlie <airlied@linux.ie>,
	Rusty Russell <rusty@rustcorp.com.au>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
	"open list:VIRTIO CORE,
	NET..."  <virtualization@lists.linux-foundation.org>,
	"open list:ABI/API" <linux-api@vger.kernel.org>
Subject: Re: [PATCH] Add virtio gpu driver.
Date: Wed, 25 Mar 2015 15:52:01 +0100	[thread overview]
Message-ID: <1427295121.23304.5.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <20150324171255-mutt-send-email-mst@redhat.com>

  Hi,

> > diff --git a/drivers/virtio/virtio_pci_common.c b/drivers/virtio/virtio_pci_common.c
> > index e894eb2..a3167fa 100644
> > --- a/drivers/virtio/virtio_pci_common.c
> > +++ b/drivers/virtio/virtio_pci_common.c
> > @@ -510,7 +510,7 @@ static int virtio_pci_probe(struct pci_dev *pci_dev,
> >  		goto err_enable_device;
> >  
> >  	rc = pci_request_regions(pci_dev, "virtio-pci");
> > -	if (rc)
> > +	if (rc && ((pci_dev->class >> 8) != PCI_CLASS_DISPLAY_VGA))
> >  		goto err_request_regions;
> >  
> >  	if (force_legacy) {
> 
> This is probably what you described as "the only concern?

Ahem, no, forgot that one, but it is related.  With vesafb using and
registering the vga compat framebuffer bar pci_request_regions will not
succeed.

vesafb will be unregistered later on (this is what I was refering to) by
the virtio-gpu driver.

> If we only need to request specific
> regions, I think we should do exactly that, requesting only parts of
> regions that are covered by the virtio capabilities.

That should work too.

cheers,
  Gerd



  reply	other threads:[~2015-03-25 14:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 16:07 [PATCH] Add virtio gpu driver Gerd Hoffmann
2015-03-24 16:15 ` Michael S. Tsirkin
2015-03-25 14:52   ` Gerd Hoffmann [this message]
2015-03-25 15:24     ` Michael S. Tsirkin
2015-03-25 15:37       ` Gerd Hoffmann
2015-03-25 17:09         ` Michael S. Tsirkin
2015-03-26  7:12           ` Gerd Hoffmann
2015-03-26  8:18             ` Michael S. Tsirkin
2015-03-26  8:42               ` [virtio-dev] " Gerd Hoffmann
2015-03-26  9:04                 ` Michael S. Tsirkin
2015-03-26 11:38                   ` Gerd Hoffmann
2015-03-26 11:53                     ` Michael S. Tsirkin
2015-03-26 15:07                       ` Gerd Hoffmann
2015-03-26 16:47                         ` Michael S. Tsirkin
2015-03-27  8:08                           ` Gerd Hoffmann
2015-03-24 16:50 ` Daniel Vetter
2015-03-25 14:53   ` Gerd Hoffmann
2015-03-26  8:53     ` Daniel Vetter
2015-03-30 12:23   ` Gerd Hoffmann
2015-03-30 14:49     ` Daniel Vetter
2016-05-25 16:40       ` Daniel Vetter
2016-05-25 16:44         ` Emil Velikov
2016-05-27  7:48         ` Gerd Hoffmann
2016-05-27  9:03           ` Daniel Vetter
2016-05-30 13:50             ` Gerd Hoffmann
2016-05-30 14:47               ` Daniel Vetter
2016-05-31  6:29                 ` Gerd Hoffmann
2016-05-31  6:55                   ` Daniel Vetter
2016-05-31  7:00                   ` Pekka Paalanen
2015-03-24 17:04 ` Michael S. Tsirkin
2015-03-24 20:47 ` Paul Bolle
2015-03-24 22:50 ` Daniel Stone
2015-03-25  0:00   ` Dave Airlie
2015-03-25 15:19   ` 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=1427295121.23304.5.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.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).