From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH v2 00/10] virtio_pci: split out legacy device support
Date: Mon, 8 Dec 2014 17:16:33 +0200 [thread overview]
Message-ID: <1418051779-27748-1-git-send-email-mst@redhat.com> (raw)
Sorry about sending two versions in such quick order -
it turns out v1 was broken on modular kernels,
so I'm sending v2 to make these configs testable as well.
virtio 1.0 support for virtio-pci isn't ready yet.
Therefore, this patchset doesn't make any functional changes.
Instead, this simply refactors virtio-pci, splitting legacy
device support code out to a separate file: virtio_pci_legacy.c
For virtio 1.0, all that's left is to add virtio_pci_modern.c
supporting
get_features
finalize_features
get (config)
set (config)
get_status
set_status
reset
setup_vq
del_vq
probe
remove
Most notably, tricky MSI-X vector probing logic stays
in common file: virtio_pci.c. version-specific only has
to code setup/del functions for individual vqs.
Note: to keep patch size down, I avoid big file changes
and renames in the same patch, so I resort to
#include "virtio_pci_legacy.c"
which is ugly, but is there only as an intermediate step.
Changes from v2:
rename virtio_pci ->virtio_pci_common, to keep
kbuild happy for modular builds.
Michael S. Tsirkin (10):
virtio_pci: add isr field
virtio_pci: fix coding style for structs
virtio_pci: free up vq->priv
virtio_pci: use priv for vq notification
virtio_pci: delete vqs indirectly
virtio_pci: setup vqs indirectly
virtio_pci: setup config vector indirectly
virtio_pci: split out legacy device support
virtio_pci: update file descriptions and copyright
virtio_pci: rename virtio_pci -> virtio_pci_common
drivers/virtio/virtio_pci_common.h | 136 +++++++
drivers/virtio/virtio_pci.c | 806 -------------------------------------
drivers/virtio/virtio_pci_common.c | 464 +++++++++++++++++++++
drivers/virtio/virtio_pci_legacy.c | 326 +++++++++++++++
drivers/virtio/Makefile | 1 +
5 files changed, 927 insertions(+), 806 deletions(-)
create mode 100644 drivers/virtio/virtio_pci_common.h
delete mode 100644 drivers/virtio/virtio_pci.c
create mode 100644 drivers/virtio/virtio_pci_common.c
create mode 100644 drivers/virtio/virtio_pci_legacy.c
--
MST
next reply other threads:[~2014-12-08 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 15:16 Michael S. Tsirkin [this message]
2014-12-08 15:16 ` [PATCH v2 01/10] virtio_pci: add isr field Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 02/10] virtio_pci: fix coding style for structs Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 03/10] virtio_pci: free up vq->priv Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 04/10] virtio_pci: use priv for vq notification Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 05/10] virtio_pci: delete vqs indirectly Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 06/10] virtio_pci: setup " Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 07/10] virtio_pci: setup config vector indirectly Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 08/10] virtio_pci: split out legacy device support Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 09/10] virtio_pci: update file descriptions and copyright Michael S. Tsirkin
2014-12-08 15:16 ` [PATCH v2 10/10] virtio_pci: rename virtio_pci -> virtio_pci_common 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=1418051779-27748-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®