From: "Michael S. Tsirkin" <mst@redhat.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Ani Sinha <anisinha@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Sriram Yagnaraman <sriram.yagnaraman@est.tech>,
Jason Wang <jasowang@redhat.com>, Keith Busch <kbusch@kernel.org>,
Klaus Jensen <its@irrelevant.dk>
Subject: Re: [PATCH 3/3] igb: Fix ARI next function numbers
Date: Sun, 2 Jul 2023 06:39:16 -0400 [thread overview]
Message-ID: <20230702063501-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <d0769c54-62f7-6aa8-01b1-0e40cc46e02a@daynix.com>
On Sun, Jul 02, 2023 at 06:49:50PM +0900, Akihiko Odaki wrote:
> On 2023/07/02 18:00, Michael S. Tsirkin wrote:
> > On Sun, Jul 02, 2023 at 05:33:56PM +0900, Akihiko Odaki wrote:
> > > The ARI next function number field is undefined for VF so the PF should
> > > end the linked list formed with the field by specifying 0.
> > >
> > > Fixes: 3a977deebe ("Intrdocue igb device emulation")
> > > Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> >
> >
> > I would also change it for the VF just so people don't wonder
> > what's the magic value. Do document in commit log though.
> >
> > Maybe just drop this parameter from pcie_ari_init completely
> > for now?
>
> I sent v2, but it doesn't change the field for VFs either to save code for
> migration. The parameter for pcie_ari_init() also remains to migrate from
> older versions.
For migration, stick the boolean in PCIDevice::cap_present. Use QEMU_PCIE_ERR_UNC_MASK_BITNR as
a template.
> >
> >
> > > ---
> > > hw/net/igb.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/hw/net/igb.c b/hw/net/igb.c
> > > index 1c989d7677..897386fc09 100644
> > > --- a/hw/net/igb.c
> > > +++ b/hw/net/igb.c
> > > @@ -431,7 +431,7 @@ static void igb_pci_realize(PCIDevice *pci_dev, Error **errp)
> > > hw_error("Failed to initialize AER capability");
> > > }
> > > - pcie_ari_init(pci_dev, 0x150, 1);
> > > + pcie_ari_init(pci_dev, 0x150, 0);
> > > pcie_sriov_pf_init(pci_dev, IGB_CAP_SRIOV_OFFSET, TYPE_IGBVF,
> > > IGB_82576_VF_DEV_ID, IGB_MAX_VF_FUNCTIONS, IGB_MAX_VF_FUNCTIONS,
> > > --
> > > 2.41.0
> >
next prev parent reply other threads:[~2023-07-02 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 8:33 [PATCH 0/3] pci: Fix ARI next function numbers Akihiko Odaki
2023-07-02 8:33 ` [PATCH 1/3] docs: Fix next function numbers in SR/IOV documentation Akihiko Odaki
2023-07-02 8:33 ` [PATCH 2/3] hw/nvme: Fix ARI next function numbers Akihiko Odaki
2023-07-02 8:33 ` [PATCH 3/3] igb: " Akihiko Odaki
2023-07-02 9:00 ` Michael S. Tsirkin
2023-07-02 9:49 ` Akihiko Odaki
2023-07-02 10:39 ` Michael S. Tsirkin [this message]
2023-07-02 8:44 ` [PATCH 0/3] pci: " Michael S. Tsirkin
2023-07-03 5:15 ` Ani Sinha
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=20230702063501-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=anisinha@redhat.com \
--cc=its@irrelevant.dk \
--cc=jasowang@redhat.com \
--cc=kbusch@kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sriram.yagnaraman@est.tech \
/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.