From: Alex Williamson <alex.williamson@redhat.com>
To: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Cc: marcel@redhat.com, izumi.taku@jp.fujitsu.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC v2 2/8] vfio-pci: add aer capability support
Date: Mon, 02 Feb 2015 13:15:47 -0700 [thread overview]
Message-ID: <1422908147.22865.416.camel@redhat.com> (raw)
In-Reply-To: <515cec0e8873b456341be9a0272f5fbea805c65f.1422433767.git.chen.fan.fnst@cn.fujitsu.com>
On Wed, 2015-01-28 at 16:37 +0800, Chen Fan wrote:
> if we detect the aer capability in vfio device, then
> we should initialize the vfio device aer rigister bits.
> so guest OS can set this bits as needed.
s/rigister/register/
> Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
> ---
> hw/vfio/pci.c | 72 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 72 insertions(+)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 014a92c..2072261 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -2670,6 +2670,73 @@ static int vfio_add_capabilities(VFIOPCIDevice *vdev)
> return vfio_add_std_cap(vdev, pdev->config[PCI_CAPABILITY_LIST]);
> }
>
> +static void vfio_pci_aer_init(VFIOPCIDevice *vdev)
> +{
> + PCIDevice *pdev = &vdev->pdev;
> + PCIExpressDevice *exp = &pdev->exp;
> + uint16_t offset = exp->aer_cap;
> +
> + if (!offset) {
> + return;
> + }
> +
All of these need to be documented with comments.
> + memset(pdev->wmask + offset, 0, PCI_ERR_SIZEOF);
> + memset(pdev->w1cmask + offset, 0, PCI_ERR_SIZEOF);
> + memset(pdev->cmask + offset, 0xFF, PCI_ERR_SIZEOF);
> +
> + pci_long_test_and_set_mask(pdev->wmask + exp->exp_cap + PCI_EXP_DEVCTL,
> + PCI_EXP_DEVCTL_CERE | PCI_EXP_DEVCTL_NFERE |
> + PCI_EXP_DEVCTL_FERE | PCI_EXP_DEVCTL_URRE);
> + pci_long_test_and_set_mask(pdev->w1cmask + exp->exp_cap + PCI_EXP_DEVSTA,
> + PCI_EXP_DEVSTA_CED | PCI_EXP_DEVSTA_NFED |
> + PCI_EXP_DEVSTA_FED | PCI_EXP_DEVSTA_URD);
> +
> + pci_set_long(pdev->w1cmask + offset + PCI_ERR_UNCOR_STATUS,
> + PCI_ERR_UNC_SUPPORTED);
> + pci_set_long(pdev->wmask + offset + PCI_ERR_UNCOR_SEVER,
> + PCI_ERR_UNC_SUPPORTED);
> + pci_long_test_and_set_mask(pdev->w1cmask + offset + PCI_ERR_COR_STATUS,
> + PCI_ERR_COR_STATUS);
> + pci_set_long(pdev->wmask + offset + PCI_ERR_COR_MASK,
> + PCI_ERR_COR_SUPPORTED);
> +
> + pci_set_long(pdev->wmask + offset + PCI_ERR_CAP,
> + PCI_ERR_CAP_ECRC_GENE | PCI_ERR_CAP_ECRC_CHKE |
> + PCI_ERR_CAP_MHRE);
> +}
> +
> +static int vfio_add_ext_capabilities(VFIOPCIDevice *vdev)
> +{
> + PCIDevice *pdev = &vdev->pdev;
> + PCIExpressDevice *exp;
> + uint32_t header;
> + uint16_t next = PCI_CONFIG_SPACE_SIZE;
> +
> + if (pci_config_size(pdev) <= PCI_CONFIG_SPACE_SIZE) {
> + return 0;
> + }
> +
> + header = pci_get_long(pdev->config + next);
> + while (header) {
> + switch (PCI_EXT_CAP_ID(header)) {
> + case PCI_EXT_CAP_ID_ERR:
> + exp = &pdev->exp;
> + exp->aer_cap = next;
Shouldn't we call pcie_aer_init() here?
> +
> + vfio_pci_aer_init(vdev);
> + break;
> + };
> +
> + next = PCI_EXT_CAP_NEXT(header);
> + if (!next) {
> + return 0;
> + }
> + header = pci_get_long(pdev->config + next);
I'd like to see this look more like vfio_add_std_cap(), registering
every capability with the QEMU PCIe-core and setting up emulation to
allow QEMU to skip capabilities that it doesn't want to expose.
> + }
> +
> + return 0;
> +}
> +
> static void vfio_pci_pre_reset(VFIOPCIDevice *vdev)
> {
> PCIDevice *pdev = &vdev->pdev;
> @@ -3296,6 +3363,11 @@ static int vfio_initfn(PCIDevice *pdev)
> goto out_teardown;
> }
>
> + ret = vfio_add_ext_capabilities(vdev);
> + if (ret) {
> + goto out_teardown;
> + }
> +
Why not extend vfio_add_capabilities()? It specifically calls
vfio_add_std_cap() in order that there could be a vfio_add_ext_cap().
> /* QEMU emulates all of MSI & MSIX */
> if (pdev->cap_present & QEMU_PCI_CAP_MSIX) {
> memset(vdev->emulated_config_bits + pdev->msix_cap, 0xff,
next prev parent reply other threads:[~2015-02-02 20:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 8:37 [Qemu-devel] [RFC v2 0/8] pass aer error to guest for vfio device Chen Fan
2015-01-28 8:37 ` [Qemu-devel] [RFC v2 1/8] pcie_aer: fix typos in pcie_aer_inject_error comment Chen Fan
2015-01-28 8:37 ` [Qemu-devel] [RFC v2 2/8] vfio-pci: add aer capability support Chen Fan
2015-02-02 20:15 ` Alex Williamson [this message]
2015-02-06 7:03 ` Chen Fan
2015-02-06 13:43 ` Alex Williamson
2015-01-28 8:37 ` [Qemu-devel] [RFC v2 3/8] pcie_aer: expose pcie_aer_msg() interface Chen Fan
2015-01-28 8:37 ` [Qemu-devel] [RFC v2 4/8] vfio-pci: pass the aer error to guest Chen Fan
2015-02-02 20:16 ` Alex Williamson
2015-02-06 7:06 ` Chen Fan
2015-01-28 8:37 ` [Qemu-devel] [RFC v2 5/8] pcie_aer: fix a trivial typo in PCIEAERMsg comments Chen Fan
2015-01-28 8:37 ` [Qemu-devel] [RFC v2 6/8] vfio_pci: fix a wrong check in vfio_pci_reset Chen Fan
2015-02-02 20:16 ` Alex Williamson
2015-02-04 9:54 ` Chen Fan
2015-02-04 13:53 ` Alex Williamson
2015-01-28 8:37 ` [Qemu-devel] [RFC v2 7/8] vfio_pci: change vfio device features bit macro to enum definition Chen Fan
2015-02-02 20:15 ` Alex Williamson
2015-01-28 8:37 ` [Qemu-devel] [RFC v2 8/8] vfio-pci: add VFIO_FEATURE_ENABLE_AER_CAP feature Chen Fan
2015-02-02 20:16 ` Alex Williamson
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=1422908147.22865.416.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=marcel@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).