public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "Zhu Lingshan" <lingshan.zhu@amd.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	"David Stevens" <stevensd@chromium.org>
Subject: Re: [PATCH v5] virtio: introduce SUSPEND bit in device status
Date: Wed, 12 Jun 2024 08:20:14 -0400	[thread overview]
Message-ID: <20240612081135-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DM8PR12MB54804F81E1673C09213A4302DCC02@DM8PR12MB5480.namprd12.prod.outlook.com>

On Wed, Jun 12, 2024 at 11:26:39AM +0000, Parav Pandit wrote:
> No locks are needed. Hypervisor is accessing the admin vq on the PF.

I'm not even going to try and get through a jumble of this thread
heavily corrupted by outlook and whatnot, but from the glimpses I got
this discussion looks like just two people talking past each other.
Lingshan, Parav's not the only one bothered by how the device seemingly
has to block a transaction until it completes suspend. Parav, I feel how
to address this is up to the author to resolve really, leave it at that.

Thanks,

-- 
MST


  reply	other threads:[~2024-06-12 12:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  7:42 [PATCH v5] virtio: introduce SUSPEND bit in device status Zhu Lingshan
2024-06-10 16:04 ` Cornelia Huck
2024-06-11  5:17   ` Parav Pandit
2024-06-11  8:26     ` Zhu Lingshan
2024-06-11  8:48       ` Parav Pandit
2024-06-11  9:33         ` Zhu Lingshan
2024-06-11  9:43           ` Parav Pandit
2024-06-11 10:12             ` Zhu Lingshan
2024-06-11 10:37               ` Parav Pandit
2024-06-12  9:19                 ` Zhu Lingshan
2024-06-12 10:07                   ` Parav Pandit
2024-06-12 10:30                     ` Zhu Lingshan
2024-06-12 11:26                       ` Parav Pandit
2024-06-12 12:20                         ` Michael S. Tsirkin [this message]
2024-06-13  5:58                           ` David Stevens
2024-06-13  9:59                             ` Zhu Lingshan
2024-06-15  4:33                               ` Parav Pandit
2024-06-17  2:22                                 ` Jason Wang
2024-06-17  3:00                                   ` Parav Pandit
2024-06-13  9:47                         ` Zhu Lingshan
2024-06-12 12:10     ` Michael S. Tsirkin
2024-06-11  8:20   ` Zhu Lingshan
2024-06-11 16:26     ` Michael S. Tsirkin
2024-06-12  9:53       ` Zhu Lingshan
2024-06-12 12:23         ` Michael S. Tsirkin
2024-06-12  7:43     ` David Stevens

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=20240612081135-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lingshan.zhu@amd.com \
    --cc=parav@nvidia.com \
    --cc=stevensd@chromium.org \
    --cc=virtio-comment@lists.linux.dev \
    /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