From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] spice: add qxl device
Date: Thu, 18 Nov 2010 18:14:48 +0200 [thread overview]
Message-ID: <20101118161448.GB9490@redhat.com> (raw)
In-Reply-To: <20101118161012.GA7948@redhat.com>
On Thu, Nov 18, 2010 at 06:10:12PM +0200, Gleb Natapov wrote:
> > WHQL includes surprise removal tests. So any card that passed
> > that will work with surprise removal.
> >
> Yeah. But it is not real "surprise removal". It will not crash qemu.
That was the problem I saw. That the way qxl is written, surprise
removal could crash qemu.
> > > > I expect surprise removal to be of most use for
> > > > assigned devices. But even for emulated devices, we have a small
> > > > number of slots available, so it would still be useful to free up the PCI slot,
> > > > even if guest needs to be rebooted then.
> > > >
> > > We are talking about should we require primary VGA to be
> > > hot-unplaggable. The last thing you want to remove to free PCI slots is
> > > primary VGA card especially if no guest OS can handle it ;)
> >
> > What I am saying is we need surprise removal generally.
> For all HW that we allow to remove from monitor sure.
>
> > If won't be too bad if we make these commands fail for VGA.
> >
> The patch is on the list already.
That's good. If my review is needed, Cc me so it won't get lost
in the noise.
--
MST
prev parent reply other threads:[~2010-11-18 16:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 13:34 [Qemu-devel] [PATCH] spice: add qxl device Gerd Hoffmann
2010-11-16 14:24 ` Anthony Liguori
2010-11-17 13:14 ` Gerd Hoffmann
2010-11-16 17:43 ` [Qemu-devel] " Michael S. Tsirkin
2010-11-17 13:28 ` Gerd Hoffmann
2010-11-17 13:58 ` Michael S. Tsirkin
2010-11-17 15:20 ` Gerd Hoffmann
2010-11-17 16:42 ` Michael S. Tsirkin
2010-11-17 17:02 ` Gerd Hoffmann
2010-11-17 18:00 ` Michael S. Tsirkin
2010-11-18 8:09 ` Gleb Natapov
2010-11-18 8:22 ` Gerd Hoffmann
2010-11-18 9:08 ` Michael S. Tsirkin
2010-11-18 10:46 ` Gerd Hoffmann
2010-11-18 9:03 ` Michael S. Tsirkin
2010-11-18 9:11 ` Gleb Natapov
2010-11-18 9:30 ` Michael S. Tsirkin
2010-11-18 9:57 ` Gleb Natapov
2010-11-18 11:33 ` Michael S. Tsirkin
2010-11-18 11:55 ` Gleb Natapov
2010-11-18 12:03 ` Michael S. Tsirkin
2010-11-18 12:27 ` Gleb Natapov
2010-11-18 14:04 ` Michael S. Tsirkin
2010-11-18 14:57 ` Gleb Natapov
2010-11-18 15:25 ` Michael S. Tsirkin
2010-11-18 15:42 ` Gleb Natapov
2010-11-18 16:04 ` Michael S. Tsirkin
2010-11-18 16:10 ` Gleb Natapov
2010-11-18 16:14 ` Michael S. Tsirkin [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=20101118161448.GB9490@redhat.com \
--to=mst@redhat.com \
--cc=gleb@redhat.com \
--cc=kraxel@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).