All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: bobooscar <bobooscar@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 回复: Re: 回复: Re:  Which part of qemu responds to ACPI control method?
Date: Thu, 04 Jul 2013 12:06:19 +0200	[thread overview]
Message-ID: <51D5491B.4050402@redhat.com> (raw)
In-Reply-To: <iugcpb1l5i7ase58vhbis2pf.1372917943967@email.android.com>

On 07/04/13 08:05, bobooscar wrote:
> Thank you laszlo. however, after I got DSDT.dsl, I found that there is
> no “_PTS” method, even if “_TTS” “_GTS”.  
> Then I go through all the acpi tables, still found no PTS/TTS methods:
>     acpidump > acpidump.out
>     acpixtract -a acpidump.out
>     for file in `ls |grep dat`; do iasl -a $file; done
> 
> The guest os is redhat 6.1 hvm.
> 
> What does that mean? Does that mean this OS does not support
> sleep/wakeup(suspend/resume) with acpi? What caused this problem? Does
> that have anything to do with qemu? (I tried to add logs in
> hwsleep.c:acpi_enter_sleep_mode in the guest kernel code, and found that
> the os does not get here)

Some tables can have several instances, like SSDT; see the --skip option.

But, it seems reasonable that you have found no _PTS method, as SeaBIOS
doesn't seem to define such. Since you started your email with _PTS, I
treated the method as something given in your case. Now I'm supposing
you use SeaBIOS and _PTS not being there is consistent with that.

So, back to square 1, what is your *actual* problem?

In any of the dumped / decompiled SSDT tables, do you see _S3, _S4, _S5
objects?

Maybe try passing the following options to qemu:

  -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0

Laszlo

      reply	other threads:[~2013-07-04 10:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  6:05 [Qemu-devel] 回复: Re: 回复: Re: Which part of qemu responds to ACPI control method? bobooscar
2013-07-04 10:06 ` Laszlo Ersek [this message]

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=51D5491B.4050402@redhat.com \
    --to=lersek@redhat.com \
    --cc=bobooscar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.