qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: marcel@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	qemu list <qemu-devel@nongnu.org>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] ich9: add disable_s3, disable_s4, s4_val properties
Date: Mon, 12 Jan 2015 13:16:46 +0200	[thread overview]
Message-ID: <20150112111646.GA28946@redhat.com> (raw)
In-Reply-To: <20150112111103.GI9688@grmbl.mre>

On Mon, Jan 12, 2015 at 04:41:03PM +0530, Amit Shah wrote:
> On (Mon) 12 Jan 2015 [13:01:28], Michael S. Tsirkin wrote:
> > On Mon, Jan 12, 2015 at 04:25:01PM +0530, Amit Shah wrote:
> > > On (Mon) 12 Jan 2015 [12:26:08], Marcel Apfelbaum wrote:
> > > > On 12/16/2014 01:23 PM, Amit Shah wrote:
> > > > >PIIX4 has disable_s3 and disable_s4 properties to enable or disable PM
> > > > >functions.  Add such properties to the ICH9 chipset as well for the Q35
> > > > >machine type.
> > > > >
> > > > >S3 / S4 are not guaranteed to always work (needs work in the guest as
> > > > >well as QEMU for things to work properly), and disabling advertising of
> > > > >these features ensures guests don't go into zombie state if something
> > > > >isn't working right.
> > > > >
> > > > >The defaults are kept the same as in PIIX4: both S3 and S4 are enabled
> > > > >by default.
> > > > >
> > > > >These can be disabled via the cmdline:
> > > > >
> > > > >   ... -global ICH9-LPC,disable_s3=1 -global ICH9-LPC,disable_s4=1
> > > >                         ^^^                           ^^^
> > > > Should be -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1
> > > 
> > > Indeed, thanks.
> > > 
> > > > Hi Amit, thanks for answering my prev question.
> > > > I have one more:)
> > > > 
> > > > I didn't see how the properties are connected to the ACPI mechanism.
> > > > I tested it with your suggested command line and it didn't work from some reason.
> > > >    - I used ... -M Q35 -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1
> > > >    - On guest: pm-is-supported --hibernate && echo $? => 0 (enabled)
> > > >    - Furthermore, pm-hibernate worked
> > > > 
> > > > Maybe I am missing something or maybe this is not in the scope of this patch.
> > > 
> > > Hibernate is special for Linux guests.  If acpi-based hibernate isn't
> > > available, Linux simulates it by writing a hibernate image and doing a
> > > shutdown of the guest instead of entering the S4 state.
> > >
> > > To test, there are two ways: check if s3 works after passing this
> > > parm, or check the acpi blobs inside the guest for the advertisement
> > > of the params.
> > > 
> > > 		Amit
> > 
> > Interesting. So this isn't for the benefit of linux guests then?
> > Which guests do actually benefit? It might be a good idea to
> > put this info in the commit log.
> 
> No, this does disable the ACPI-based s4 advertisement, so it does
> affect Linux too.
> 
> Linux, though, has a way of doing hibernate even when acpi-s4 isn't
> available.  It's a convenience(?) feature offered by Linux, and isn't
> related to anything else.  No need for mentioning it in the commit
> message, and this behaviour is not dependent on anything that qemu can
> or cannot do.

Yes but the implication is that your patch will not prevent Linux
from "go into zombie state".

> (I think Windows since some version too does this, but don't remember
> the details..)
> 
> 		Amit

While I don't have issues with workarounds for guest bugs,
the following text in the commit log:
" ensures guests don't go into zombie state if something isn't working right"
seems unnecessarily vague.

What does zombie state refer to, with which guests was this observed,
and what was the root cause?

-- 
MST

  reply	other threads:[~2015-01-12 11:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 11:23 [Qemu-devel] [PATCH 1/1] ich9: add disable_s3, disable_s4, s4_val properties Amit Shah
2014-12-17 13:08 ` Marcel Apfelbaum
2015-01-05 12:23   ` Amit Shah
2015-01-07 12:04     ` Paolo Bonzini
2015-01-12 10:26 ` Marcel Apfelbaum
2015-01-12 10:55   ` Amit Shah
2015-01-12 11:01     ` Michael S. Tsirkin
2015-01-12 11:11       ` Amit Shah
2015-01-12 11:16         ` Michael S. Tsirkin [this message]
2015-01-12 11:30           ` Amit Shah
2015-01-12 11:51     ` Marcel Apfelbaum
2015-01-12 12:00       ` Amit Shah

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=20150112111646.GA28946@redhat.com \
    --to=mst@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=marcel@redhat.com \
    --cc=pbonzini@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).