From: Laszlo Ersek <lersek@redhat.com>
To: bobooscar <bobooscar@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 回复： Re: Which part of qemu responds to ACPI control method?
Date: Wed, 03 Jul 2013 10:01:34 +0200 [thread overview]
Message-ID: <51D3DA5E.80809@redhat.com> (raw)
In-Reply-To: <5q852j4g1hsu4mh5x8dqhupl.1372817671447@email.android.com>
On 07/03/13 04:14, bobooscar wrote:
> Take the method “_PTS” for example, how could I know how it access a
> certain hardware, and what hardware it accesses? I am a newbie in this
> field, thanks in advance;)
In "POSIX-like" guests, you can dump the ACPI tables with the "acpidump"
utility (pmtools package), eg.
acpidump --table DSDT --output DSDT.aml --binary
then decompile it with "iasl":
iasl -d DSDT.aml
This creates "DSDT.dsl", a decompiled ACPI Source Language file. You can
interpret it by consulting the ACPI specification
<http://www.acpi.info/spec50.htm>.
Laszlo
prev parent reply other threads:[~2013-07-03 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 2:14 [Qemu-devel] 回复： Re: Which part of qemu responds to ACPI control method? bobooscar
2013-07-03 8:01 ` 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=51D3DA5E.80809@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 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).