qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] Add PIIX4 properties to control PM system states.
Date: Wed, 23 May 2012 16:34:14 +0200	[thread overview]
Message-ID: <4FBCF566.3060902@suse.de> (raw)
In-Reply-To: <4FBCE5A5.7050308@codemonkey.ws>

Am 23.05.2012 15:27, schrieb Anthony Liguori:
> On 05/20/2012 04:02 AM, Gleb Natapov wrote:
>> This patch adds two things. First it allows QEMU to distinguish between
>> regular powerdown and S4 powerdown. Later separate QMP notification will
>> be added for S4 powerdown. Second it allows S3/S4 states to be disabled
>> from QEMU command line. Some guests known to be broken with regards to
>> power management, but allow to use it anyway. Using new properties
>> management will be able to disable S3/S4 for such guests.
>>
>> Supported system state are passed to a firmware using new fw_cfg file.
>> The file contains  6 byte array. Each byte represents one system
>> state. If byte at offset X has its MSB set it means that system state
>> X is supported and to enter it guest should use the value from lowest 3
>> bits.
>>
>> Signed-off-by: Gleb Natapov<gleb@redhat.com>
> 
> I see nothing wrong in principle here except that you should use a PTR
> property to pass the fw_cfg object to the ACPI PM device.

Paolo was on a quest to eliminate the PTR properties so I don't think we
should advocate adding any more. Without having reviewed the code, I
would suggest to rather QOM'ify the fw_cfg object and to use a link<>
property if needed.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2012-05-23 14:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20  9:02 [Qemu-devel] [PATCH 1/2] Make pointer to fw_cfg device global Gleb Natapov
2012-05-20  9:02 ` [Qemu-devel] [PATCH 2/2] Add PIIX4 properties to control PM system states Gleb Natapov
2012-05-23 13:27   ` Anthony Liguori
2012-05-23 13:34     ` Gleb Natapov
2012-05-23 13:48       ` Anthony Liguori
2012-05-23 14:34     ` Andreas Färber [this message]
2012-05-23 14:42       ` Paolo Bonzini
2012-05-23 15:11         ` Anthony Liguori
2012-05-23 15:16           ` Gleb Natapov
2012-05-23 12:37 ` [Qemu-devel] [PATCH 1/2] Make pointer to fw_cfg device global Gleb Natapov
2012-05-23 13:25   ` Anthony Liguori
2012-05-23 13:32     ` Gleb Natapov
2012-05-23 13:46       ` Anthony Liguori
2012-05-23 12:44 ` Peter Maydell
2012-05-23 12:47   ` Gleb Natapov
2012-05-23 14:41   ` Andreas Färber
2012-05-23 14:54     ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2012-05-14 12:34 Gleb Natapov
2012-05-14 12:34 ` [Qemu-devel] [PATCH 2/2] Add PIIX4 properties to control PM system states Gleb Natapov

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=4FBCF566.3060902@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=gleb@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).