From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] spice: add qxl device
Date: Wed, 17 Nov 2010 20:00:08 +0200 [thread overview]
Message-ID: <20101117180008.GE29556@redhat.com> (raw)
In-Reply-To: <4CE40AAF.7090202@redhat.com>
On Wed, Nov 17, 2010 at 06:02:39PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> >>>>Better don't try ...
> >>>
> >>>Better prevent it then?
> >>
> >>How can I do that?
>
> Question still stands: Is there some way to disable hotplug for
> certain pci devices?
Not sure. It's really a work-around bug, maybe it's better to fix
it properly.
> >> How does this work btw? Only
> >>one vga adapter can drive the legacy vga ports, right? Is there
> >>some way to enable/disable this per vga device?
> >
> >Yes, just disable IO memory.
>
> This is supposed to disable legacy vga ports (0x03c0+) too?
Sure.
> >> If so: does qemu
> >>emulate this correctly?
> >
> >It mostly does.
>
> I doubt it actually enables/disables the legacy vga ports.
I'll check when I have the time. We can fix it if it doesn't,
> >But the counter wrapping will at least in theory crash qemu,
> >this is an even bigger problem than a guest crash.
>
> I can put it a limit at one million hotplugs or so ...
How about a simple allocator? With at most 256 devices
on a pci bus * 8 functions, it need not be hard: just
a long long bitmask with ffsll used to find a free bit.
Also - what is the ID used for? What happens if it's not
unique?
> >> I also don't see the point in plugging a display like
> >>mad.
> >
> >Just to see if you can exploit some memory corruption maybe?
>
> Can the guest do that without the hosts help?
> Especially plugging *in* something?
>
> cheers,
> Gerd
No, but a monitor user connected to qemu over a qmp socket can do this.
--
MST
next prev parent reply other threads:[~2010-11-17 18:00 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 [this message]
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
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=20101117180008.GE29556@redhat.com \
--to=mst@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).