qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Moore, Robert" <robert.moore@intel.com>,
	Josh Triplett <josh@joshtriplett.org>
Cc: Michael Tsirkin <mtsirkin@redhat.com>,
	edk2-devel-01 <edk2-devel@ml01.01.org>,
	Shannon Zhao <zhaoshenglong@huawei.com>,
	qemu devel list <qemu-devel@nongnu.org>, Jake Edge <jake@lwn.net>,
	"Smith, Jonathan D" <jonathan.d.smith@intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] "Using Python to investigate EFI and ACPI"
Date: Thu, 3 Sep 2015 18:16:39 +0200	[thread overview]
Message-ID: <55E87267.8090501@redhat.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D342E42@ORSMSX112.amr.corp.intel.com>

On 09/03/15 17:57, Moore, Robert wrote:
> 
> 
>> -----Original Message-----
>> From: Laszlo Ersek [mailto:lersek@redhat.com]
>> Sent: Thursday, September 03, 2015 8:54 AM
>> To: Josh Triplett
>> Cc: edk2-devel-01; qemu devel list; Michael Tsirkin; Igor Mammedov; Marcel
>> Apfelbaum; Paolo Bonzini; Shannon Zhao; Moore, Robert; Smith, Jonathan D;
>> Jake Edge
>> Subject: Re: "Using Python to investigate EFI and ACPI"
>>
>> Another question: when you execute an AML method that does, say, IO port
>> access, does the AML interpreter of ACPICA actually *perform* that IO port
>> access? Because, the one that is embedded in Linux obviously does, and the
>> one that is embedded in the userspace ACPICA command line utility
>> "acpiexec" obviously doesn't.
> 
> We have recently integrated the ACPICA AML debugger with the Linux kernel,
> and we have a userspace utility that allows communication with the debugger.
> This allows the user to enter debugger commands such as "execute control method",
> and the commands are carried out by the kernel code -- thus talking to the
> actual hardware.

... Was it merged in commit c91c5b276b? The series at
<https://lkml.org/lkml/2015/8/24/921>? Or is that "only" a followup
series to the main work?

Can you please provide a pointer to the userspace tool as well?

This thread is getting better and better. :)

Thank you!
Laszlo

  reply	other threads:[~2015-09-03 16:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03  9:16 [Qemu-devel] "Using Python to investigate EFI and ACPI" Laszlo Ersek
2015-09-03  9:41 ` Laszlo Ersek
2015-09-03 14:48   ` Jake Edge
2015-09-03 14:50 ` Josh Triplett
2015-09-03 15:22   ` josh
2015-09-03 15:53   ` Laszlo Ersek
2015-09-03 15:57     ` Moore, Robert
2015-09-03 16:16       ` Laszlo Ersek [this message]
2015-09-03 16:19         ` Moore, Robert
2015-09-03 16:41     ` josh
2015-09-03 17:19       ` Laszlo Ersek
2015-09-03 21:25         ` josh
2015-09-03 23:21           ` Laszlo Ersek
2015-09-04 17:11             ` josh

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=55E87267.8090501@redhat.com \
    --to=lersek@redhat.com \
    --cc=edk2-devel@ml01.01.org \
    --cc=imammedo@redhat.com \
    --cc=jake@lwn.net \
    --cc=jonathan.d.smith@intel.com \
    --cc=josh@joshtriplett.org \
    --cc=marcel@redhat.com \
    --cc=mtsirkin@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.moore@intel.com \
    --cc=zhaoshenglong@huawei.com \
    /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).