From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Amos Kong <akong@redhat.com>,
"Kevin O'Connor" <kevin@koconnor.net>,
seabios@seabios.org, Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org, jasowang@redhat.com,
alex williamson <alex.williamson@redhat.com>
Subject: Re: [PATCHv2 0/3] acpi: fix up EJ0 in DSDT
Date: Fri, 23 Sep 2011 11:47:12 -0300 [thread overview]
Message-ID: <20110923144712.GA1618@amt.cnet> (raw)
In-Reply-To: <cover.1316690724.git.mst@redhat.com>
On Thu, Sep 22, 2011 at 02:37:16PM +0300, Michael S. Tsirkin wrote:
> This is a second iteration of the patch. The patch has been
> significantly reworked to address (offline) comments by Gleb.
>
> I think the infrastructure created is generic enough
> to be generally useful beyond the specific bug
> that I would like to fix. Specifically it
> will be able to find S3 Name to patch that,
> or process compiled CPU SSDT to avoid the need for
> hardcoded offsets.
>
> Please comment.
>
> Main changes:
> - tools rewritten in python
> - Original ASL retains _EJ0 methods, BIOS patches that to EJ0_
> - generic ACP_EXTRACT infrastructure that can match Method
> and Name Operators
> - instead of matching specific method name, insert tags
> in original DSL source and match that to AML
>
> -----
Neat, looks good to me.
next prev parent reply other threads:[~2011-09-23 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 11:37 [PATCHv2 0/3] acpi: fix up EJ0 in DSDT Michael S. Tsirkin
2011-09-22 11:37 ` [PATCHv2 1/3] acpi: generate and parse mixed asl/aml listing Michael S. Tsirkin
2011-09-22 11:37 ` [PATCHv2 2/3] acpi: EJ0 method name patching Michael S. Tsirkin
2011-09-22 11:37 ` [PATCHv2 3/3] acpi: remove _RMV Michael S. Tsirkin
2011-09-23 14:47 ` Marcelo Tosatti [this message]
2011-09-28 11:41 ` [PATCHv2 0/3] acpi: fix up EJ0 in DSDT Amos Kong
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=20110923144712.GA1618@amt.cnet \
--to=mtosatti@redhat.com \
--cc=akong@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=gleb@redhat.com \
--cc=jasowang@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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