All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [post 1.1 PATCH] hw/qxl: disallow non sync io for revision >= 3
Date: Wed, 09 May 2012 14:51:01 +0200	[thread overview]
Message-ID: <4FAA6835.1010508@redhat.com> (raw)
In-Reply-To: <1336562766-25682-1-git-send-email-alevy@redhat.com>

On 05/09/12 13:26, Alon Levy wrote:
> The guest drivers should already know how to use async for revision 3.
> But since it's still possible to have an older driver with revision 3
> that doesn't check for the revision, require a new parameter
> "force_async", which we can later turn to 1 by default.

Hmm.  PCI revisions are supposed to be backward compatible, I don't
think this is a good idea.  We might want to log a warning or inform via
'info spice' in case we find a guest using the old, sync commands, so
management can figure and warn, but I wouldn't do more.

We can think about defining a qxl2 pci device, with a different pci id,
where we can throw away old stuff.  For such a new & incompatible device
I'd like to change a few more things while being at it ...

(1) go for a single 32bit mmio register set similar to real hardware.
That should replace the rom bar (device info), the fields in the ram
area (where interrupt mask etc live) and the io command bar.

(2) consider virtio for the rings.  Not sure this is worth it as that
wouldn't make qxl bus-agnostic, for vga compatibility and device memory
we'll still have a dependency on pci ...

(3) renumber the remaining bars so we can make the vram bar 64bit,
without a 32bit compatibility alias needed.

(4) Drop QXL_IO_SET_MODE support and the mode list.

Possibly more ...

cheers,
  Gerd

  reply	other threads:[~2012-05-09 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 11:26 [Qemu-devel] [post 1.1 PATCH] hw/qxl: disallow non sync io for revision >= 3 Alon Levy
2012-05-09 12:51 ` Gerd Hoffmann [this message]
2012-05-09 13:16   ` Alon Levy

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=4FAA6835.1010508@redhat.com \
    --to=kraxel@redhat.com \
    --cc=alevy@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 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.