From: "Michael S. Tsirkin" <mst@redhat.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: "Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Jason Wang" <jasowang@redhat.com>,
"Sriram Yagnaraman" <sriram.yagnaraman@ericsson.com>,
"Keith Busch" <kbusch@kernel.org>,
"Klaus Jensen" <its@irrelevant.dk>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Yui Washizu" <yui.washidu@gmail.com>
Subject: Re: [PATCH v5 0/8] virtio-net: add support for SR-IOV emulation
Date: Tue, 30 Jul 2024 13:56:56 -0400 [thread overview]
Message-ID: <20240730135602-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <125b333d-36a3-49d2-84e5-76a5f9d23a48@daynix.com>
On Tue, Jul 30, 2024 at 09:26:20PM +0900, Akihiko Odaki wrote:
> On 2024/07/30 20:37, Michael S. Tsirkin wrote:
> > On Mon, Jul 15, 2024 at 02:19:06PM +0900, Akihiko Odaki wrote:
> > > Based-on: <20240714-rombar-v2-0-af1504ef55de@daynix.com>
> > > ("[PATCH v2 0/4] hw/pci: Convert rom_bar into OnOffAuto")
> >
> > OK I will revert this for now. We'll try again after the release,
> > there will be time to address s390.
> >
>
> I'd like to know if anybody wants to use igb on a s390x machine configured
> with libvirt. Such a configuration is already kind of broken, and it is
> likely to require significant effort on both side of libvirt and QEMU to fix
> it.
I assume Cédric wouldn't report it if was unused.
> As an alternative, I'm also introducing SR-IOV support to virtio-net-pci. It
> does not suffer the same problem with igb thanks to its flexible
> configuration mechanism.
>
> Regards,
> Akihiko Odaki
Sounds like this needs more review time, anyway.
next prev parent reply other threads:[~2024-07-30 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 5:19 [PATCH v5 0/8] virtio-net: add support for SR-IOV emulation Akihiko Odaki
2024-07-15 5:19 ` [PATCH v5 1/8] hw/pci: Do not add ROM BAR for SR-IOV VF Akihiko Odaki
2024-07-15 5:19 ` [PATCH v5 2/8] hw/pci: Fix SR-IOV VF number calculation Akihiko Odaki
2024-07-15 5:19 ` [PATCH v5 3/8] pcie_sriov: Ensure PF and VF are mutually exclusive Akihiko Odaki
2024-07-15 5:19 ` [PATCH v5 4/8] pcie_sriov: Check PCI Express for SR-IOV PF Akihiko Odaki
2024-07-15 5:19 ` [PATCH v5 5/8] pcie_sriov: Allow user to create SR-IOV device Akihiko Odaki
2024-07-15 5:19 ` [PATCH v5 6/8] virtio-pci: Implement SR-IOV PF Akihiko Odaki
2024-07-15 5:19 ` [PATCH v5 7/8] virtio-net: Implement SR-IOV VF Akihiko Odaki
2024-07-15 5:19 ` [PATCH v5 8/8] docs: Document composable SR-IOV device Akihiko Odaki
2024-07-30 11:37 ` [PATCH v5 0/8] virtio-net: add support for SR-IOV emulation Michael S. Tsirkin
2024-07-30 12:26 ` Akihiko Odaki
2024-07-30 17:56 ` Michael S. Tsirkin [this message]
2024-07-31 8:58 ` Cédric Le Goater
2024-08-01 7:13 ` Akihiko Odaki
2024-08-01 7:51 ` Michael S. Tsirkin
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=20240730135602-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=eduardo@habkost.net \
--cc=its@irrelevant.dk \
--cc=jasowang@redhat.com \
--cc=kbusch@kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sriram.yagnaraman@ericsson.com \
--cc=yui.washidu@gmail.com \
/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).