mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: feliu@nvidia.com
Cc: parav@nvidia.com, jiri@nvidia.com, mst@redhat.com,
	yishaih@nvidia.com, alex.williamson@redhat.com,
	jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
	virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
	Francis Ginther <francis.ginther@canonical.com>,
	John Cabaj <john.cabaj@canonical.com>,
	Catherine Redfield <catherine.redfield@canonical.com>,
	Ankush Pathak <ankush.pathak@canonical.com>,
	Chlo Smith <chloe.smith@canonical.com>
Subject: [REGRESSION][v6.8-rc1] virtio-pci: Introduce admin virtqueue
Date: Fri, 3 May 2024 14:03:15 -0400	[thread overview]
Message-ID: <13a313c7-c214-4d49-9029-c79b503c17dd@canonical.com> (raw)

Hi Feng,

During testing, a kernel bug was identified with the suspend/resume 
functionality on instances running in a public cloud [0].  This bug is a 
regression introduced in v6.8-rc1.  After a kernel bisect, the following 
commit was identified as the cause of the regression:

        fd27ef6b44be  ("virtio-pci: Introduce admin virtqueue")

I was hoping to get your feedback, since you are the patch author. Do 
you think gathering any additional data will help diagnose this issue?  
This commit is depended upon by other virtio commits, so a revert test 
is not really straight forward without reverting all the dependencies.   
Any ideas you have would be greatly appreciated.


Thanks,

Joe

http://pad.lv/2063315


             reply	other threads:[~2024-05-03 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 18:03 Joseph Salisbury [this message]
2024-05-08  3:33 ` Jason Wang
2024-05-08 11:18   ` Catherine Redfield
2024-05-09  3:02     ` Feng Liu
     [not found]       ` <CAFRRCvNqAQd4Hf5v8EU7PkVu=7YmB+q340zG6ccm4O8jJHwi+g@mail.gmail.com>
2024-05-16  9:52         ` Jason Wang

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=13a313c7-c214-4d49-9029-c79b503c17dd@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=alex.williamson@redhat.com \
    --cc=ankush.pathak@canonical.com \
    --cc=catherine.redfield@canonical.com \
    --cc=chloe.smith@canonical.com \
    --cc=feliu@nvidia.com \
    --cc=francis.ginther@canonical.com \
    --cc=jasowang@redhat.com \
    --cc=jiri@nvidia.com \
    --cc=john.cabaj@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=yishaih@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
all inboxes | Powered by JetHome®