From: Alex Williamson <alex.williamson@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com, izumi.taku@jp.fujitsu.com,
Dou Liyang <douly.fnst@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH RFC v11 4/4] vfio: add 'aer' property to expose aercap
Date: Fri, 20 Jan 2017 11:01:01 -0700 [thread overview]
Message-ID: <20170120110101.538bed72@t450s.home> (raw)
In-Reply-To: <5881A858.2020203@cn.fujitsu.com>
On Fri, 20 Jan 2017 14:04:08 +0800
Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
> On 01/19/2017 06:36 AM, Alex Williamson wrote:
> > On Sat, 31 Dec 2016 17:13:08 +0800
> > Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
> >
> >> From: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
> >>
> >> Add 'aer' property, let user choose whether expose the aer capability
> >> or not.
> >
> > But that's not what it does, it only controls the behavior in response
> > to non-fatal errors, the capability is exposed regardless.
> >
>
> This commit log is legacy, and defaults to off is a result of the
> configuration restriction & your previous discussion, right?
>
> In current version, if 'aer' property is off, we just allocate the
> config space via pcie_add_capability(), we don't init the AER
> capability, the value is all 0s there, so does that still mean
> "capability is exposed regardless"?
The design has changed, we no longer require a matching host and guest
topology, we can more easily transparently enable non-fatal error
correction. We need to reevaluate whether previous decisions are still
valid, we cannot blindly assume that a requirement for a previous
design still applies. Thanks,
Alex
> >> Should disable aer feature by default, because only non-fatal
> >> error is supported now.
> >
> > Why does that mean it should be disabled by default? What bad thing
> > happens if we enable this opportunistically?
> >
> >> Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
> >> Signed-off-by: Dou Liyang <douly.fnst@cn.fujitsu.com>
> >> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> >> ---
> >> hw/vfio/pci.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> >> index 9861f72..fc9db66 100644
> >> --- a/hw/vfio/pci.c
> >> +++ b/hw/vfio/pci.c
> >> @@ -3057,6 +3057,8 @@ static Property vfio_pci_dev_properties[] = {
> >> DEFINE_PROP_UINT32("x-pci-sub-device-id", VFIOPCIDevice,
> >> sub_device_id, PCI_ANY_ID),
> >> DEFINE_PROP_UINT32("x-igd-gms", VFIOPCIDevice, igd_gms, 0),
> >> + DEFINE_PROP_BIT("aer", VFIOPCIDevice, features,
> >> + VFIO_FEATURE_ENABLE_AER_BIT, false),
> >> /*
> >> * TODO - support passed fds... is this necessary?
> >> * DEFINE_PROP_STRING("vfiofd", VFIOPCIDevice, vfiofd_name),
> >
> >
> >
> > .
> >
>
next prev parent reply other threads:[~2017-01-20 18:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 9:13 [Qemu-devel] [PATCH RFC v11 0/4] vfio-pci: pass non-fatal error to guest Cao jin
2016-12-31 9:13 ` [Qemu-devel] [PATCH v11 1/4] pcie_aer: support configurable AER capa version Cao jin
2016-12-31 9:13 ` [Qemu-devel] [PATCH RFC v11 2/4] vfio: new function to init aer cap for vfio device Cao jin
2017-01-18 22:09 ` Alex Williamson
2017-01-20 6:03 ` Cao jin
2017-01-20 18:12 ` Alex Williamson
2016-12-31 9:13 ` [Qemu-devel] [PATCH RFC v11 3/4] vfio-pci: pass the aer error to guest Cao jin
2017-01-09 22:55 ` Michael S. Tsirkin
2017-01-18 22:31 ` Alex Williamson
2017-01-20 6:50 ` Cao jin
2017-01-20 6:57 ` Tian, Kevin
2017-01-20 18:21 ` Alex Williamson
2017-01-22 4:43 ` Tian, Kevin
2016-12-31 9:13 ` [Qemu-devel] [PATCH RFC v11 4/4] vfio: add 'aer' property to expose aercap Cao jin
2017-01-18 22:36 ` Alex Williamson
2017-01-20 6:04 ` Cao jin
2017-01-20 18:01 ` Alex Williamson [this message]
2016-12-31 9:17 ` [Qemu-devel] [PATCH RFC v11 0/4] vfio-pci: pass non-fatal error to guest no-reply
2017-01-18 21:43 ` Alex Williamson
2017-01-19 6:15 ` Cao jin
2017-01-19 6:25 ` Cao jin
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=20170120110101.538bed72@t450s.home \
--to=alex.williamson@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=mst@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).