qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] Get system state configuration from QEMU and patch DSDT with it.
Date: Sun, 20 May 2012 19:49:05 +0300	[thread overview]
Message-ID: <20120520164905.GD26391@redhat.com> (raw)
In-Reply-To: <20120520163913.GA18509@morn.localdomain>

On Sun, May 20, 2012 at 12:39:13PM -0400, Kevin O'Connor wrote:
> On Sun, May 20, 2012 at 07:25:40PM +0300, Avi Kivity wrote:
> > On 05/20/2012 07:16 PM, Kevin O'Connor wrote:
> > > > Here we in agreement, and I was against patching till it was unavoidable,
> > > > but than pci hotplug started using it, and afterwards processor
> > > > definitions, so no point in avoiding it now by using inferior methods.
> > >
> > > I agree as well.
> > >
> > > What's the background to needing to have dynamic S3/S4 definitions?
> > > (Why will some qemu instances be able to sleep and not others?)
> > >
> > 
> > Backwards compatibility.  qemu has a -M machine-type option that expose
> > an old qemu's guest-visible attributes.  If an old qemu didn't support
> > S3, then -M old shouldn't either.
> 
> The DSDT has claimed S3, S4, and S5 support since SeaBIOS has
> supported ACPI.  What's the background to the requirement to stop
> claiming support for it?
> 
Not all guests have working S3/S4 implementation. We want management to
be able to disable S3/S4 for such guests. S4 value changes since we want
to distinguish between S4 and S5 in qemu.

--
			Gleb.

  reply	other threads:[~2012-05-20 16:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20  9:03 [Qemu-devel] [PATCH 1/3] Fix aml_name_string() to recognize block name modifiers Gleb Natapov
2012-05-20  9:03 ` [Qemu-devel] [PATCH 2/3] Add ACPI_EXTRACT_PKG_START macro parsing Gleb Natapov
2012-05-20  9:03 ` [Qemu-devel] [PATCH 3/3] Get system state configuration from QEMU and patch DSDT with it Gleb Natapov
2012-05-20 11:44   ` Avi Kivity
2012-05-20 12:15     ` Gleb Natapov
2012-05-20 12:30       ` Avi Kivity
2012-05-20 12:36         ` Gleb Natapov
2012-05-20 12:47           ` Avi Kivity
2012-05-20 12:59             ` Gleb Natapov
2012-05-20 13:39               ` Avi Kivity
2012-05-20 13:57                 ` Gleb Natapov
2012-05-20 14:34                   ` Avi Kivity
2012-05-20 14:43                     ` Gleb Natapov
2012-05-20 14:46                       ` Avi Kivity
2012-05-20 15:15                         ` Gleb Natapov
2012-05-20 16:16                           ` Kevin O'Connor
2012-05-20 16:25                             ` Avi Kivity
2012-05-20 16:39                               ` Kevin O'Connor
2012-05-20 16:49                                 ` Gleb Natapov [this message]
2012-05-20 16:11                 ` Kevin O'Connor
2012-05-20 10:32 ` [Qemu-devel] [SeaBIOS] [PATCH 1/3] Fix aml_name_string() to recognize block name modifiers Alon Levy
2012-05-20 11:13   ` Gleb Natapov
2012-05-23  1:23 ` [Qemu-devel] " Kevin O'Connor
2012-06-20 13:08   ` Gleb Natapov
2012-06-22  1:06     ` Kevin O'Connor

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=20120520164905.GD26391@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).