qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anthoine Bourgeois <anthoine.bourgeois@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/2] virtio-vga: fix virtio-vga bar ordering
Date: Thu, 23 Apr 2020 16:03:50 +0200	[thread overview]
Message-ID: <20200423140350.tlsfvoktrbb7zamx@sirius.home.kraxel.org> (raw)
In-Reply-To: <20200423085202-mutt-send-email-mst@kernel.org>

On Thu, Apr 23, 2020 at 08:52:58AM -0400, Michael S. Tsirkin wrote:
> On Wed, Apr 22, 2020 at 11:54:54PM +0200, Anthoine Bourgeois wrote:
> > With virtio-vga, pci bar are reordered. Bar #2 is used for compatibility
> > with stdvga. By default, bar #2 is used by virtio modern io bar.
> > This bar is the last one introduce in the virtio pci bar layout and it's
> > crushed by the virtio-vga reordering. So virtio-vga and
> > modern-pio-notify are incompatible because virtio-vga failed to
> > initialize with this option.
> > 
> > This fix sets the modern io bar to the bar #5 to avoid conflict.
> > 
> > Signed-off-by: Anthoine Bourgeois <anthoine.bourgeois@gmail.com>
> 
> Gerd, would you say it's required for 5.0?

Given that modern-pio-notify is off by default I wouldn't classify this
as release blocker, i.e. I wouldn't delay the release for that.

We are at -rc4 (last rc) already, so I'd tend to say no.  Maybe if we
need -rc5 for other reasons.

cheers,
  Gerd



      reply	other threads:[~2020-04-23 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 21:54 [PATCH v2 1/2] virtio-vga: fix virtio-vga bar ordering Anthoine Bourgeois
2020-04-22 21:54 ` [PATCH v2 2/2] virtio-pci: update virtio pci bar layout documentation Anthoine Bourgeois
2020-04-23 11:32   ` Gerd Hoffmann
2020-04-23 11:31 ` [PATCH v2 1/2] virtio-vga: fix virtio-vga bar ordering Gerd Hoffmann
2020-04-23 12:52 ` Michael S. Tsirkin
2020-04-23 14:03   ` Gerd Hoffmann [this message]

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=20200423140350.tlsfvoktrbb7zamx@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=anthoine.bourgeois@gmail.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).