qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] add hotplug opt-out option for devices.
Date: Thu, 18 Nov 2010 13:42:25 +0200	[thread overview]
Message-ID: <20101118114225.GH7948@redhat.com> (raw)
In-Reply-To: <4CE50E03.1020907@redhat.com>

On Thu, Nov 18, 2010 at 12:29:07PM +0100, Gerd Hoffmann wrote:
> On 11/18/10 12:20, Gleb Natapov wrote:
> >On Thu, Nov 18, 2010 at 12:13:21PM +0100, Gerd Hoffmann wrote:
> >>On 11/18/10 12:01, Gleb Natapov wrote:
> >>>On Thu, Nov 18, 2010 at 11:45:15AM +0100, Gerd Hoffmann wrote:
> >>>>   Hi,
> >>>>
> >>>>This patch series adds a qdev flag which allows devices being tagged as
> >>>>not hotpluggable.  It also sets this flag for a number of devices.
> >>>>
> >>>Do we want to be able to mark device as not hot-unpluggable from command
> >>>like too? Something like this -device blabla,notunplug=no.
> >>
> >>Hmm, dunno.  Do you have a example where this would be needed or useful?
> >>
> >Dunno me too. Windows allows to eject any hot-unpluggable device to any
> >user and in the past we got requirement to disable this and had to build
> >two BIOSes one with cpu hot-plug support another without. So
> >hot-pluggability of device looks like management decision (along with
> >technical one if device can't be actually unplugged).
> 
> For *that* use case well have to do a bit more like dynamically
> building the acpi table which indicates which slots are
> hot-pluggable and which are not.  Which indeed would be useful and
> would fix the windows xp offering me to unplug the piix chipset in
> the "savely remove hardware" menu ;)
> 
Yes, but management has to specify to us somehow that certain device
is not hotpluggable and notunplug=no looks like good way to do it.

> But I suspect it also isn't exactly trivial and way behind the scope
> of this little patch set ...
> 
If it is not trivial I will not insist.

--
			Gleb.

  reply	other threads:[~2010-11-18 11:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 10:45 [Qemu-devel] [PATCH 0/3] add hotplug opt-out option for devices Gerd Hoffmann
2010-11-18 10:45 ` [Qemu-devel] [PATCH 1/3] qdev: allow devices being tagged as not hotpluggable Gerd Hoffmann
2010-11-18 10:45 ` [Qemu-devel] [PATCH 2/3] piix: tag " Gerd Hoffmann
2010-11-18 10:45 ` [Qemu-devel] [PATCH 3/3] vga: tag as not hotplugable Gerd Hoffmann
2010-11-18 11:01 ` [Qemu-devel] [PATCH 0/3] add hotplug opt-out option for devices Gleb Natapov
2010-11-18 11:13   ` Gerd Hoffmann
2010-11-18 11:20     ` Gleb Natapov
2010-11-18 11:29       ` Gerd Hoffmann
2010-11-18 11:42         ` Gleb Natapov [this message]
2010-11-18 12:07           ` Michael Tokarev
2010-11-18 12:16             ` Gleb Natapov
2010-11-20  2:30 ` Anthony Liguori
2010-11-20 17:24   ` Gleb Natapov
2010-11-22 10:17   ` Gerd Hoffmann
2010-11-22 13:31     ` Gleb Natapov
2010-12-10 12:34     ` Markus Armbruster
2010-12-10 14:04       ` 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=20101118114225.GH7948@redhat.com \
    --to=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).