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.
