From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Chen Fan <chen.fan.fnst@cn.fujitsu.com>,
izumi.taku@jp.fujitsu.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 7/7] pc: add PC_I440FX_COMPAT to disable aercap for vifo device
Date: Wed, 18 Mar 2015 15:36:03 +0100 [thread overview]
Message-ID: <20150318153207-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1426688101.3643.367.camel@redhat.com>
On Wed, Mar 18, 2015 at 08:15:01AM -0600, Alex Williamson wrote:
> On Wed, 2015-03-18 at 15:05 +0100, Michael S. Tsirkin wrote:
> > On Wed, Mar 18, 2015 at 08:02:26AM -0600, Alex Williamson wrote:
> > > On Wed, 2015-03-18 at 14:23 +0100, Michael S. Tsirkin wrote:
> > > > typo in subject: vfio, not vifo.
> > > >
> > > > On Thu, Mar 12, 2015 at 06:23:59PM +0800, Chen Fan wrote:
> > > > > for piix4 chipset, we don't need to expose aer, so introduce
> > > > > PC_I440FX_COMPAT for all piix4 machines to disable aercap,
> > > > > and add HW_COMPAT_2_2 to disable aercap for all lower
> > > > > than 2.3.
> > > > >
> > > > > Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
> > > >
> > > > Well vfio is never migrated ATM.
> > > > So why is compat code needed at all?
> > >
> > > It's not for migration, it's to maintain current behavior on existing
> > > platforms. If someone gets an uncorrected AER error on q35 machine type
> > > today, the VM stops. With this change, AER would be exposed to the
> > > guest and the guest could handle it. The compat change therefore
> > > maintains the stop VM behavior on existing q35 machine types.
> >
> > If stop VM behaviour is useful, expose it to users.
> > If not, then don't.
> > I don't see why does it have to be tied to machine types.
>
> Because q35-2.2 machine type will currently do a stop VM on uncorrected
> AER error. If we don't tie that to a machine option then q35-2.2 would
> suddenly start exposing the error to the guest. That's a fairly
> significant change in behavior for a static machine type.
I don't think you can classify it as a behaviour change. VM stop is not
guest visible behaviour.
Are you worrying about guests misbehaving when they see these errors?
Then you want this as user-controlled, supported option.
In other words: we only tie things to machine types when we
have to. This code gets almost no testing, and is a lot of
work to test. This one sounds like "just in case" is not a good
motivation.
--
MST
next prev parent reply other threads:[~2015-03-18 14:36 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 10:23 [Qemu-devel] [PATCH v5 0/7] pass aer error to guest for vfio device Chen Fan
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 1/7] vfio: add pcie extanded capability support Chen Fan
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 2/7] aer: impove pcie_aer_init to support vfio device Chen Fan
2015-03-13 22:25 ` Alex Williamson
2015-03-16 2:30 ` Chen Fan
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 3/7] vfio: add aer support for " Chen Fan
2015-03-13 22:28 ` Alex Williamson
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 4/7] pcie_aer: expose pcie_aer_msg() interface Chen Fan
2015-03-13 22:30 ` Alex Williamson
2015-03-18 13:29 ` Michael S. Tsirkin
2015-03-19 1:33 ` Chen Fan
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 5/7] vfio-pci: pass the aer error to guest Chen Fan
2015-03-13 22:34 ` Alex Williamson
2015-03-16 3:05 ` Chen Fan
2015-03-16 3:52 ` Alex Williamson
2015-03-16 7:35 ` Chen Fan
2015-03-16 14:09 ` Alex Williamson
2015-03-25 1:33 ` Chen Fan
2015-03-25 2:31 ` Alex Williamson
2015-03-25 1:53 ` Chen Fan
2015-03-25 2:41 ` Alex Williamson
2015-03-25 3:07 ` Chen Fan
2015-04-01 4:12 ` Chen Fan
2015-04-01 15:46 ` Alex Williamson
2015-04-08 8:59 ` Chen Fan
2015-04-08 15:36 ` Alex Williamson
2015-04-15 10:30 ` Chen Fan
2015-04-15 14:18 ` Alex Williamson
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 6/7] vfio: add 'x-aer' property to expose aercap Chen Fan
2015-03-18 13:23 ` Michael S. Tsirkin
2015-03-18 14:09 ` Alex Williamson
2015-03-12 10:23 ` [Qemu-devel] [PATCH v5 7/7] pc: add PC_I440FX_COMPAT to disable aercap for vifo device Chen Fan
2015-03-13 22:38 ` Alex Williamson
2015-03-16 2:48 ` Chen Fan
2015-03-16 2:49 ` Chen Fan
2015-03-18 13:23 ` Michael S. Tsirkin
2015-03-18 14:02 ` Alex Williamson
2015-03-18 14:05 ` Michael S. Tsirkin
2015-03-18 14:15 ` Alex Williamson
2015-03-18 14:36 ` Michael S. Tsirkin [this message]
2015-03-18 14:50 ` Alex Williamson
2015-03-18 15:02 ` Michael S. Tsirkin
2015-03-18 15:45 ` Alex Williamson
2015-03-18 16:44 ` Michael S. Tsirkin
2015-03-18 17:11 ` Alex Williamson
2015-03-18 17:45 ` Michael S. Tsirkin
2015-03-18 18:08 ` Alex Williamson
2015-03-18 18:56 ` Michael S. Tsirkin
2015-03-18 19:05 ` Alex Williamson
2015-03-19 21:26 ` Paolo Bonzini
2015-03-16 2:52 ` [Qemu-devel] [PATCH v5 0/7] pass aer error to guest for vfio device Chen Fan
2015-03-16 4:57 ` Michael S. Tsirkin
2015-03-19 21:44 ` Paolo Bonzini
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=20150318153207-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.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 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.