From: Lukasz Maniak <lukasz.maniak@linux.intel.com>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com, lukasz.maniak@linux.intel.com,
stefanha@redhat.com, qemu-block@nongnu.org, mst@redhat.com,
k.jensen@samsung.com, armbru@redhat.com, f4bug@amsat.org,
kbusch@kernel.org, its@irrelevant.dk, hreitz@redhat.com,
xypron.glpk@gmx.de, lukasz.gieryk@linux.intel.com,
ani@anisinha.ca, imammedo@redhat.com
Subject: [PATCH v6 00/12] hw/nvme: SR-IOV with Virtualization Enhancements
Date: Fri, 18 Mar 2022 19:53:27 +0100 [thread overview]
Message-ID: <20220318185327.1666536-1-lukasz.maniak@linux.intel.com> (raw)
Changes since v5:
- Fixed PCI hotplug issue related to deleting VF twice
- Corrected error messages for SR-IOV parameters
- Rebased on master, patches for PCI got pulled into the tree
- Added Reviewed-by labels
Lukasz Maniak (4):
hw/nvme: Add support for SR-IOV
hw/nvme: Add support for Primary Controller Capabilities
hw/nvme: Add support for Secondary Controller List
docs: Add documentation for SR-IOV and Virtualization Enhancements
Łukasz Gieryk (8):
hw/nvme: Implement the Function Level Reset
hw/nvme: Make max_ioqpairs and msix_qsize configurable in runtime
hw/nvme: Remove reg_size variable and update BAR0 size calculation
hw/nvme: Calculate BAR attributes in a function
hw/nvme: Initialize capability structures for primary/secondary
controllers
hw/nvme: Add support for the Virtualization Management command
hw/nvme: Update the initalization place for the AER queue
hw/acpi: Make the PCI hot-plug aware of SR-IOV
docs/system/devices/nvme.rst | 82 +++++
hw/acpi/pcihp.c | 6 +-
hw/nvme/ctrl.c | 673 ++++++++++++++++++++++++++++++++---
hw/nvme/ns.c | 2 +-
hw/nvme/nvme.h | 55 ++-
hw/nvme/subsys.c | 75 +++-
hw/nvme/trace-events | 6 +
include/block/nvme.h | 65 ++++
include/hw/pci/pci_ids.h | 1 +
9 files changed, 909 insertions(+), 56 deletions(-)
--
2.25.1
reply other threads:[~2022-03-18 18:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220318185327.1666536-1-lukasz.maniak@linux.intel.com \
--to=lukasz.maniak@linux.intel.com \
--cc=ani@anisinha.ca \
--cc=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=imammedo@redhat.com \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=lukasz.gieryk@linux.intel.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xypron.glpk@gmx.de \
/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).