From: Parav Pandit via Virtualization <virtualization@lists.linux-foundation.org>
To: Parav Pandit <parav@nvidia.com>, "mst@redhat.com" <mst@redhat.com>
Cc: "virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: RE: [PATCH v3 0/4] virtio short improvements
Date: Mon, 9 Aug 2021 07:33:56 +0000 [thread overview]
Message-ID: <PH0PR12MB54814E4657560159AB5910BEDCF69@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PH0PR12MB54813F761DEA56B792B29E0EDCF09@PH0PR12MB5481.namprd12.prod.outlook.com>
Hi Michael,
> From: Virtualization <virtualization-bounces@lists.linux-foundation.org> On
> Behalf Of Parav Pandit via Virtualization
> Hi Michael,
>
> > From: Parav Pandit
> > Sent: Thursday, July 29, 2021 10:09 AM
> >
> > Hi Michael,
> >
> > > From: Parav Pandit <parav@nvidia.com>
> > > Sent: Wednesday, July 21, 2021 7:57 PM
> > > To: mst@redhat.com; virtualization@lists.linux-foundation.org
> > > Cc: Parav Pandit <parav@nvidia.com>
> > > Subject: [PATCH v3 0/4] virtio short improvements
> > >
> > > Hi,
> > >
> > > This series contains small improvements for virtio pci driver.
> > > The main idea is to support surprise removal of virtio pci device
> > > when the driver is already loaded. Future patches will further
> > > improve other areas of hotplug.
> > >
> > > 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
> > >
> > Any comments to address or will you please take this short series?
> >
>
> Can we please proceed with these series?
We want users to stop facing the call trace and lockup.
Can you please respond to this short series?
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2021-08-09 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 14:26 [PATCH v3 0/4] virtio short improvements Parav Pandit via Virtualization
2021-07-21 14:26 ` [PATCH v3 1/4] virtio: Improve vq->broken access to avoid any compiler optimization Parav Pandit via Virtualization
2021-07-21 14:26 ` [PATCH v3 2/4] virtio: Keep vring_del_virtqueue() mirror of VQ create Parav Pandit via Virtualization
2021-07-21 14:26 ` [PATCH v3 3/4] virtio: Protect vqs list access Parav Pandit via Virtualization
2021-07-21 14:26 ` [PATCH v3 4/4] virtio_pci: Support surprise removal of virtio pci device Parav Pandit via Virtualization
2021-07-29 4:39 ` [PATCH v3 0/4] virtio short improvements Parav Pandit via Virtualization
2021-08-03 2:30 ` Parav Pandit via Virtualization
2021-08-09 7:33 ` Parav Pandit via Virtualization [this message]
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=PH0PR12MB54814E4657560159AB5910BEDCF69@PH0PR12MB5481.namprd12.prod.outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.