qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "Chen, Jiqian" <Jiqian.Chen@amd.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Huang, Ray" <Ray.Huang@amd.com>
Subject: Re: [RFC QEMU PATCH v8 2/2] virtio-pci: implement No_Soft_Reset bit
Date: Fri, 29 Mar 2024 06:44:49 -0400	[thread overview]
Message-ID: <20240329064431-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEt=V4V4JgT08o5_f7tj-eNZDi2GB4=H_Qp7xALrRxBWhQ@mail.gmail.com>

On Fri, Mar 29, 2024 at 03:20:59PM +0800, Jason Wang wrote:
> On Fri, Mar 29, 2024 at 3:07 PM Chen, Jiqian <Jiqian.Chen@amd.com> wrote:
> >
> > On 2024/3/28 20:36, Michael S. Tsirkin wrote:
> > >>>> +}
> > >>>> +
> > >>>>  static void virtio_pci_bus_reset_hold(Object *obj)
> > >>>>  {
> > >>>>      PCIDevice *dev = PCI_DEVICE(obj);
> > >>>>      DeviceState *qdev = DEVICE(obj);
> > >>>>
> > >>>> +    if (virtio_pci_no_soft_reset(dev)) {
> > >>>> +        return;
> > >>>> +    }
> > >>>> +
> > >>>>      virtio_pci_reset(qdev);
> > >>>>
> > >>>>      if (pci_is_express(dev)) {
> > >>>> @@ -2484,6 +2511,8 @@ static Property virtio_pci_properties[] = {
> > >>>>                      VIRTIO_PCI_FLAG_INIT_LNKCTL_BIT, true),
> > >>>>      DEFINE_PROP_BIT("x-pcie-pm-init", VirtIOPCIProxy, flags,
> > >>>>                      VIRTIO_PCI_FLAG_INIT_PM_BIT, true),
> > >>>> +    DEFINE_PROP_BIT("x-pcie-pm-no-soft-reset", VirtIOPCIProxy, flags,
> > >>>> +                    VIRTIO_PCI_FLAG_PM_NO_SOFT_RESET_BIT, false),
> 
> Why does it come with an x prefix?
> 
> > >>>>      DEFINE_PROP_BIT("x-pcie-flr-init", VirtIOPCIProxy, flags,
> > >>>>                      VIRTIO_PCI_FLAG_INIT_FLR_BIT, true),
> > >>>>      DEFINE_PROP_BIT("aer", VirtIOPCIProxy, flags,
> > >>>
> > >>> I am a bit confused about this part.
> > >>> Do you want to make this software controllable?
> > >> Yes, because even the real hardware, this bit is not always set.
> 
> We are talking about emulated devices here.
> 
> > >
> > > So which virtio devices should and which should not set this bit?
> > This depends on the scenario the virtio-device is used, if we want to trigger an internal soft reset for the virtio-device during S3, this bit shouldn't be set.
> 
> If the device doesn't need reset, why bother the driver for this?
> 
> Btw, no_soft_reset is insufficient for some cases, there's a proposal
> for the virtio-spec. I think we need to wait until it is done.

That seems orthogonal or did I miss something?

> > In my use case on my environment, I don't want to reset virtio-gpu during S3,
> > because once the display resources are destroyed, there are not enough information to re-create them, so this bit should be set.
> > Making this bit software controllable is convenient for users to take their own choices.
> 
> Thanks
> 
> >
> > >
> > >>> Or should this be set to true by default and then
> > >>> changed to false for old machine types?
> > >> How can I do so?
> > >> Do you mean set this to true by default, and if old machine types don't need this bit, they can pass false config to qemu when running qemu?
> > >
> > > No, you would use compat machinery. See how is x-pcie-flr-init handled.
> > >
> > >
> >
> > --
> > Best regards,
> > Jiqian Chen.



  parent reply	other threads:[~2024-03-29 10:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 10:39 [RFC QEMU PATCH v8 0/1] S3 support Jiqian Chen
2024-03-28 10:39 ` [RFC QEMU PATCH v8 1/2] virtio-pci: only reset pm state during resetting Jiqian Chen
2024-03-28 10:39 ` [RFC QEMU PATCH v8 2/2] virtio-pci: implement No_Soft_Reset bit Jiqian Chen
2024-03-28 10:57   ` Michael S. Tsirkin
2024-03-28 11:08     ` Chen, Jiqian
2024-03-28 12:36       ` Michael S. Tsirkin
2024-03-29  7:00         ` Chen, Jiqian
2024-03-29  7:20           ` Jason Wang
2024-03-29  8:00             ` Chen, Jiqian
2024-03-29 10:38               ` Jason Wang
2024-04-02  2:56                 ` Chen, Jiqian
2024-03-29 10:44             ` Michael S. Tsirkin [this message]
2024-04-02  3:03               ` Chen, Jiqian
2024-04-07  3:20                 ` Jason Wang
2024-04-07 11:49                   ` Michael S. Tsirkin
2024-04-08  4:56                     ` Jason Wang
2024-04-12  6:10                       ` Chen, Jiqian
2024-04-12  6:04                     ` Chen, Jiqian
2024-04-12  6:41                       ` Jason Wang
2024-04-12  6:49                         ` Chen, Jiqian
2024-04-12  5:59                   ` Chen, Jiqian
2024-04-12  6:42                     ` 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=20240329064431-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=Jiqian.Chen@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).