From: Parav Pandit via Virtualization <virtualization@lists.linux-foundation.org>
To: <mst@redhat.com>, <virtualization@lists.linux-foundation.org>
Subject: [PATCH v1 0/4] virtio short improvements
Date: Mon, 19 Jul 2021 10:52:14 +0300 [thread overview]
Message-ID: <20210719075218.1485812-1-parav@nvidia.com> (raw)
Hi,
This series contains small improvements for virtio pci driver.
The main idea support surprise removal of virtio pci device.
Patches 1 to 3 prepare the code to handle surprise removal by marking
the device as broken in patch-4.
Patch summary:
patch-1: ensures that compiler optimization doesn't occur on vq->broken
flag
patch-2: maintains the mirror sequence on VQ delete and VQ create
patch-3: protects vqs list for simultaneous access from reader and a writer
patch-4: handles surprise removal of virtio pci device which avoids
call trace and system lockup
---
changelog:
v0->v1:
- fixed below comments from Michael
- fixed typo in patch4 in comment
- using WRITE_ONCE instead of smp_store_release()
- using spinlock instead of rwlock
- improved comment in patch
- removed fixes tag in patch-1
Parav Pandit (4):
virtio: Improve vq->broken access to avoid any compiler optimization
virtio: Keep vring_del_virtqueue() mirror of VQ create
virtio: Protect vqs list access
virtio_pci: Support surprise removal of virtio pci device
drivers/virtio/virtio.c | 1 +
drivers/virtio/virtio_pci_common.c | 7 +++++++
drivers/virtio/virtio_ring.c | 17 ++++++++++++++---
include/linux/virtio.h | 1 +
4 files changed, 23 insertions(+), 3 deletions(-)
--
2.27.0
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next reply other threads:[~2021-07-19 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 7:52 Parav Pandit via Virtualization [this message]
2021-07-19 7:52 ` [PATCH v1 1/4] virtio: Improve vq->broken access to avoid any compiler optimization Parav Pandit via Virtualization
2021-07-19 7:52 ` [PATCH v1 2/4] virtio: Keep vring_del_virtqueue() mirror of VQ create Parav Pandit via Virtualization
2021-07-19 7:52 ` [PATCH v1 3/4] virtio: Protect vqs list access Parav Pandit via Virtualization
2021-07-19 7:52 ` [PATCH v1 4/4] virtio_pci: Support surprise removal of virtio pci device Parav Pandit via Virtualization
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=20210719075218.1485812-1-parav@nvidia.com \
--to=virtualization@lists.linux-foundation.org \
--cc=mst@redhat.com \
--cc=parav@nvidia.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).