From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH 1/4] acpi: generate mixed asl/aml listing Date: Wed, 21 Sep 2011 15:47:40 +0300 Message-ID: <20110921124739.GA19203@redhat.com> References: <3d1b7511b6d36aa0af898eb2eeca8992b9c45f8f.1316608551.git.mst@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Kevin O'Connor" , seabios@seabios.org, Gleb Natapov , kvm@vger.kernel.org, jasowang@redhat.com, alex williamson , Marcelo Tosatti To: Amos Kong Return-path: Received: from mx1.redhat.com ([209.132.183.28]:40549 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753571Ab1IUMqr (ORCPT ); Wed, 21 Sep 2011 08:46:47 -0400 Content-Disposition: inline In-Reply-To: <3d1b7511b6d36aa0af898eb2eeca8992b9c45f8f.1316608551.git.mst@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Sep 21, 2011 at 03:44:21PM +0300, Michael S. Tsirkin wrote: > Use iasl -l flag to produce a mixed listing, where a > source line is followed by matching AML. > Since we use a preprocessed input, this generates long lines with > multiple commands per line. To make it possible to match > AML to source exactly, split the input that we supply iasl, > with each command on a separate line. > > Signed-off-by: Michael S. Tsirkin I thought I'd add an example listing here: 467.... Device (S1) { 0000080B....5B 82 25 53 31 5F 5F ... "[.%S1__" 468.... Name (_ADR, 0x00010000) 00000812....08 5F 41 44 52 0C 00 00 "._ADR..." 0000081A....01 00 .................. ".." 469.... Method (EJ0_,1) { 0000081C....14 0F 45 4A 30 5F 01 ... "..EJ0_." 470.... Store(ShiftLeft(1, 0x0001), B0EJ) -- MST