From: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: izumi.taku@jp.fujitsu.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC v3 08/10] vfio-pci: add VFIO_FEATURE_ENABLE_AER_CAP feature
Date: Thu, 26 Feb 2015 14:46:41 +0800 [thread overview]
Message-ID: <54EEC151.4070202@cn.fujitsu.com> (raw)
In-Reply-To: <1423586352.22865.810.camel@redhat.com>
On 02/11/2015 12:39 AM, Alex Williamson wrote:
> On Tue, 2015-02-10 at 15:03 +0800, Chen Fan wrote:
>> add a new "aercap" feature in vfio device, for controlling
>> whether expose aer capability.
>>
>> Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
>> ---
>> hw/vfio/pci.c | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
>> index bf314a1..c21b40b 100644
>> --- a/hw/vfio/pci.c
>> +++ b/hw/vfio/pci.c
>> @@ -138,6 +138,8 @@ typedef struct VFIOMSIXInfo {
>> enum {
>> #define VFIO_FEATURE_ENABLE_VGA_BIT 0
>> VFIO_FEATURE_ENABLE_VGA = (1 << VFIO_FEATURE_ENABLE_VGA_BIT),
>> +#define VFIO_FEATURE_ENABLE_AER_CAP_BIT 1
>> + VFIO_FEATURE_ENABLE_AER_CAP = (1 << VFIO_FEATURE_ENABLE_AER_CAP_BIT),
>> };
>>
>> typedef struct VFIOPCIDevice {
>> @@ -2721,8 +2723,10 @@ static int vfio_add_ext_cap(VFIOPCIDevice *vdev, uint16_t pos)
>>
>> switch (cap_id) {
>> case PCI_EXT_CAP_ID_ERR:
>> - pcie_add_capability(pdev, cap_id, cap_ver, pos, size);
>> - vfio_setup_pcie_aer(vdev, pos);
>> + if (vdev->features & VFIO_FEATURE_ENABLE_AER_CAP) {
>> + pcie_add_capability(pdev, cap_id, cap_ver, pos, size);
>> + vfio_setup_pcie_aer(vdev, pos);
>> + }
Hi Alex,
sorry for replaying so late. I am just back from holiday. :)
> Maybe the question should be why we're adding extended capabilities at
> all if the chipset doesn't expose them. If we boot on 440fx, all
> extended capability parsing could be disabled. We could then add an
> x-aer=off option to vfio-pci to allow the user to disable aer
> specifically if they want.
your meaning is adding two option:
1) one controls exposing extended caps to device. in particular on
440fx chipset we must disable it.
2) the other one controls exposing aer capability to user specifically.
right?
Thanks,
Chen
>> break;
>> default:
>> pcie_add_capability(pdev, cap_id, cap_ver, pos, size);
>> @@ -3487,6 +3491,8 @@ static Property vfio_pci_dev_properties[] = {
>> DEFINE_PROP_BIT("x-vga", VFIOPCIDevice, features,
>> VFIO_FEATURE_ENABLE_VGA_BIT, false),
>> DEFINE_PROP_INT32("bootindex", VFIOPCIDevice, bootindex, -1),
>> + DEFINE_PROP_BIT("aercap", VFIOPCIDevice, features,
>> + VFIO_FEATURE_ENABLE_AER_CAP_BIT, true),
>> /*
>> * TODO - support passed fds... is this necessary?
>> * DEFINE_PROP_STRING("vfiofd", VFIOPCIDevice, vfiofd_name),
>
>
> .
>
next prev parent reply other threads:[~2015-02-26 6:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 7:03 [Qemu-devel] [RFC v3 00/10] pass aer error to guest for vfio device Chen Fan
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 01/10] pcie_aer: fix typos in pcie_aer_inject_error comment Chen Fan
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 02/10] aer: fix a wrong init PCI_ERR_COR_STATUS w1cmask type register Chen Fan
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 03/10] aer: introduce pcie_aer_setup to setup aer related bits Chen Fan
2015-02-10 16:39 ` Alex Williamson
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 04/10] vfio: add pcie extanded capability support Chen Fan
2015-02-10 16:39 ` Alex Williamson
2015-02-26 9:37 ` Chen Fan
2015-02-26 22:28 ` Alex Williamson
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 05/10] pcie_aer: expose pcie_aer_msg() interface Chen Fan
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 06/10] piix: disable all vfio device aercap property Chen Fan
2015-02-10 16:39 ` Alex Williamson
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 07/10] vfio_pci: change vfio device features bit macro to enum definition Chen Fan
2015-02-10 16:39 ` Alex Williamson
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 08/10] vfio-pci: add VFIO_FEATURE_ENABLE_AER_CAP feature Chen Fan
2015-02-10 16:39 ` Alex Williamson
2015-02-26 6:46 ` Chen Fan [this message]
2015-02-26 22:18 ` Alex Williamson
2015-03-02 7:23 ` Chen Fan
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 09/10] vfio-pci: pass the aer error to guest Chen Fan
2015-02-10 7:03 ` [Qemu-devel] [RFC v3 10/10] pcie_aer: fix a trivial typo in PCIEAERMsg comments Chen Fan
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=54EEC151.4070202@cn.fujitsu.com \
--to=chen.fan.fnst@cn.fujitsu.com \
--cc=alex.williamson@redhat.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 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).