qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 v3 0/2] pcie: Fix ARI next function numbers
Date: Mon, 3 Jul 2023 00:52:17 -0400	[thread overview]
Message-ID: <20230703005201-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0a6bd04c-8364-2735-0ee6-060550bea77b@daynix.com>

On Mon, Jul 03, 2023 at 12:17:16PM +0900, Akihiko Odaki wrote:
> On 2023/07/02 21:43, Michael S. Tsirkin wrote:
> > On Sun, Jul 02, 2023 at 09:02:25PM +0900, Akihiko Odaki wrote:
> > > The ARI next function number field is undefined for VF. The PF should
> > > end the linked list formed with the field by specifying 0.
> > > 
> > > Supersedes: <20230701070133.24877-1-akihiko.odaki@daynix.com>
> > > ("[PATCH 0/4] pci: Compare function number and ARI next function number")
> > 
> > Thanks! How was this patch tested?
> 
> I brought VFs up with igb and performed link up for a fresh VM and a VM
> migrated from 8.0.2.

Which guest?

> > 
> > 
> > > V2 -> V3:
> > >    Moved the logic to PCI common infrastucture (Michael S. Tsirkin)
> > > 
> > > V1 -> V2:
> > >    Fixed migration. (Michael S. Tsirkin)
> > >    Added a caveat comment. (Michael S. Tsirkin)
> > > 
> > > Akihiko Odaki (2):
> > >    pcie: Use common ARI next function number
> > >    pcie: Specify 0 for ARI next function numbers
> > > 
> > >   docs/pcie_sriov.txt   | 4 ++--
> > >   include/hw/pci/pci.h  | 2 ++
> > >   include/hw/pci/pcie.h | 2 +-
> > >   hw/core/machine.c     | 1 +
> > >   hw/net/igb.c          | 2 +-
> > >   hw/net/igbvf.c        | 2 +-
> > >   hw/nvme/ctrl.c        | 2 +-
> > >   hw/pci/pci.c          | 2 ++
> > >   hw/pci/pcie.c         | 4 +++-
> > >   9 files changed, 14 insertions(+), 7 deletions(-)
> > > 
> > > -- 
> > > 2.41.0
> > 



  reply	other threads:[~2023-07-03  4:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 12:02 [PATCH v3 0/2] pcie: Fix ARI next function numbers Akihiko Odaki
2023-07-02 12:02 ` [PATCH v3 1/2] pcie: Use common ARI next function number Akihiko Odaki
2023-07-02 12:02 ` [PATCH v3 2/2] pcie: Specify 0 for ARI next function numbers Akihiko Odaki
2023-07-04 12:03   ` Igor Mammedov
2023-07-02 12:43 ` [PATCH v3 0/2] pcie: Fix " Michael S. Tsirkin
2023-07-03  3:17   ` Akihiko Odaki
2023-07-03  4:52     ` Michael S. Tsirkin [this message]
2023-07-03  4:54       ` Akihiko Odaki

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=20230703005201-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 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).