From: Gleb Natapov <gleb@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Marcel Apfelbaum <marcel.a@redhat.com>,
seabios@seabios.org, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [SeaBIOS] [PATCH] don't expose pvpanic device in the UI
Date: Tue, 6 Aug 2013 12:20:27 +0300 [thread overview]
Message-ID: <20130806092027.GK8218@redhat.com> (raw)
In-Reply-To: <5200B78D.2060708@suse.de>
On Tue, Aug 06, 2013 at 10:45:01AM +0200, Andreas Färber wrote:
> Am 06.08.2013 10:36, schrieb Gleb Natapov:
> > On Tue, Aug 06, 2013 at 11:33:10AM +0300, Michael S. Tsirkin wrote:
> >> On Tue, Aug 06, 2013 at 10:21:52AM +0300, Gleb Natapov wrote:
> >>>> If you see a mouse in a room, how likely is it that there's
> >>>> a single mouse there?
> >>>>
> >>>> This is a PV technology which to me looks like it was
> >>>> rushed through and not only set on by default, but
> >>>> without a way to disable it - apparently on the assumption
> >>>> there's 0 chance it can cause any damage. Now that
> >>>> we do know the chance it's not there, why not go back
> >>>> to the standard interface, and why not give
> >>>> users a chance to enable/disable it?
> >>> You should be able to disable it with: -device pvpanic,ioport=0
> >>
> >> Doesn't work for me.
> > Bug that should be fixed. With this command line _STA should return
> > zero.
> >
> >> Besides, both -device pvpanic and use of ioport=0 to disable it
> >> are completely undocumented.
> >>
> > Not the only undocumented thing in QEMU command line :)
> [snip]
>
> I disagree: -device adds a device, not removes one. It will still be
> present.
>
I assume you are answering to the quote about ioport=0, not
documentation here. ioport=0 does not removes the device, it disables
it. The claim was it cannot be disabled, it can (assuming no bugs), but
it should not be.
> I am neutral as to whether qemu-system-x86_64 should have it enabled by
> default or not. But if we want to suppress it, then -nodefaults should
> disable it. Since libvirt uses that though, it would mean libvirt would
> need to add it back, whether via user's XML domain config or by libvirt
> itself based on some version/etc. heuristics.
>
There is no clear definition of what -nodefaults should or should not
do. Should it disable PV ACPI hotplug device? Should it create a machine
with no mmio/io regions registered at all?
--
Gleb.
next prev parent reply other threads:[~2013-08-06 9:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1375688843-19573-1-git-send-email-hutao@cn.fujitsu.com>
[not found] ` <20130805081055.GA356@redhat.com>
[not found] ` <20130805081617.GB2258@redhat.com>
[not found] ` <20130805091826.GA877@redhat.com>
[not found] ` <20130805092044.GH2258@redhat.com>
[not found] ` <20130805150333.GC877@redhat.com>
[not found] ` <20130805160421.GB15901@redhat.com>
2013-08-05 18:32 ` [Qemu-devel] [SeaBIOS] [PATCH] don't expose pvpanic device in the UI Michael S. Tsirkin
2013-08-06 7:34 ` Gleb Natapov
2013-08-06 8:03 ` Vadim Rozenfeld
2013-08-06 8:05 ` Gleb Natapov
2013-08-06 8:14 ` Vadim Rozenfeld
2013-08-06 8:38 ` Gleb Natapov
[not found] ` <51FF6A79.9060603@redhat.com>
[not found] ` <703333176.9515483.1375697447963.JavaMail.root@redhat.com>
[not found] ` <20130805151723.GF877@redhat.com>
[not found] ` <1970367422.9695773.1375718517492.JavaMail.root@redhat.com>
[not found] ` <20130805161833.GA4244@redhat.com>
[not found] ` <51FFD6CE.5090302@redhat.com>
[not found] ` <20130805182628.GC4244@redhat.com>
[not found] ` <20130806072152.GK10891@redhat.com>
2013-08-06 8:33 ` Michael S. Tsirkin
2013-08-06 8:36 ` Gleb Natapov
2013-08-06 8:45 ` Andreas Färber
2013-08-06 9:15 ` Michael S. Tsirkin
2013-08-06 9:20 ` Gleb Natapov [this message]
2013-08-06 10:04 ` Michael S. Tsirkin
2013-08-06 17:53 ` Andreas Färber
2013-08-06 9:56 ` Markus Armbruster
2013-08-06 10:11 ` Michael S. Tsirkin
2013-08-06 9:21 ` Michael S. Tsirkin
2013-08-06 9:32 ` Gleb Natapov
2013-08-06 10:19 ` Michael S. Tsirkin
2013-08-06 10:44 ` Gleb Natapov
2013-08-06 11:03 ` Andreas Färber
2013-08-06 11:16 ` Gleb Natapov
2013-08-06 11:48 ` Markus Armbruster
2013-08-06 12:03 ` Gleb Natapov
2013-08-06 12:09 ` Michael S. Tsirkin
2013-08-06 12:45 ` Andreas Färber
2013-08-07 8:17 ` Stefan Hajnoczi
2013-08-06 11:54 ` Gerd Hoffmann
2013-08-06 12:08 ` Gleb Natapov
2013-08-06 10:35 ` Andreas Färber
2013-08-06 11:00 ` Gleb Natapov
2013-08-06 11:23 ` Andreas Färber
2013-08-06 12:00 ` Gleb Natapov
2013-08-06 12:02 ` Gerd Hoffmann
2013-08-06 12:05 ` Michael S. Tsirkin
2013-08-06 12:17 ` Gleb Natapov
2013-08-06 17:22 ` Andreas Färber
2013-08-06 12:08 ` Michael S. Tsirkin
2013-08-06 12:19 ` Gleb Natapov
2013-08-06 9:26 ` Hu Tao
2013-08-06 9:29 ` Gleb Natapov
2013-08-06 10:13 ` Michael S. Tsirkin
2013-08-06 10:14 ` Gleb Natapov
2013-08-06 10:23 ` Michael S. Tsirkin
2013-08-06 10:28 ` Gleb Natapov
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=20130806092027.GK8218@redhat.com \
--to=gleb@redhat.com \
--cc=afaerber@suse.de \
--cc=kraxel@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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.