From: "Michael S. Tsirkin" <mst@redhat.com>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: "Anthony Liguori" <aliguori@us.ibm.com>,
"Stefan Berger" <stefanb@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, "Bruce Rogers" <brogers@suse.com>,
"Joel Schopp" <jschopp@linux.vnet.ibm.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Isaku Yamahata" <yamahata@valinux.co.jp>
Subject: Re: [Qemu-devel] [PATCH 0/4] add ACPI Embedded Controller
Date: Fri, 24 May 2013 14:45:29 +0300 [thread overview]
Message-ID: <20130524114528.GC7046@redhat.com> (raw)
In-Reply-To: <1369194397-608-1-git-send-email-lig.fnst@cn.fujitsu.com>
On Wed, May 22, 2013 at 11:46:33AM +0800, liguang wrote:
> These patches try to add ACPI Embedded Controller (EC),
> refer-to:
> ACPI SPEC v5 chapter 5
> "ACPI Embedded Controller Interface Specification"
>
> EC is a standard ACPI device, it plays flexible roles,
> e.g.
> power controller, it can control power sequence for
> platform to enter or leave system state(0,1,3,4,5),
> it can controller CPU fan by the temperature of sensor.
> event carrier, it can pass events between platform
> and OS, so OS can execute _Qxx method which defined
> by yourself.
>
> So, I want to deliver CPU online/offline event between
> OS and QEMU for CPU hotplug feature, then we will don't
> need to "echo 1 > /sys/devices/system/cpu/cpu1/online"
> again after 'cpu-add'.
>
> patches for online/offline event handler of QEUM and
> linux kernel are writing, and will send once finished.
>
> since EC is a common device, so I send pathes separately.
Do any non-linux guests support this device?
--
MST
next prev parent reply other threads:[~2013-05-24 11:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 3:46 [Qemu-devel] [PATCH 0/4] add ACPI Embedded Controller liguang
2013-05-22 3:46 ` [Qemu-devel] [PATCH 1/4] acpi: add ACPI Embedded Controller support liguang
2013-05-22 3:46 ` [Qemu-devel] [PATCH 2/4] acpi/gpe: expand bits of gpe register liguang
2013-05-22 5:28 ` Isaku Yamahata
2013-05-22 5:37 ` li guang
2013-05-24 1:24 ` Isaku Yamahata
2013-05-24 2:02 ` li guang
2013-05-27 9:00 ` Gerd Hoffmann
2013-05-28 0:32 ` li guang
2013-05-27 9:06 ` Gerd Hoffmann
2013-05-22 3:46 ` [Qemu-devel] [PATCH 3/4] ich9: add notifer for ec to generate sci liguang
2013-05-27 20:21 ` Michael S. Tsirkin
2013-05-28 0:23 ` li guang
2013-05-28 6:40 ` Michael S. Tsirkin
2013-05-28 6:44 ` li guang
2013-05-22 3:46 ` [Qemu-devel] [PATCH 4/4][seabios] ec: add ASL for ACPI Embedded Controller liguang
2013-05-23 3:03 ` li guang
2013-05-24 0:34 ` [Qemu-devel] [PATCH 0/4] add " li guang
2013-05-24 11:45 ` Michael S. Tsirkin [this message]
2013-05-27 0:20 ` li guang
2013-05-27 0:51 ` Anthony Liguori
2013-05-27 1:22 ` li guang
2013-05-27 11:45 ` Igor Mammedov
2013-05-28 0:28 ` li guang
2013-05-28 8:16 ` Igor Mammedov
2013-05-28 8:34 ` li guang
2013-05-28 9:38 ` Igor Mammedov
2013-05-29 0:23 ` li guang
2013-05-27 20:23 ` Michael S. Tsirkin
2013-05-28 0:21 ` li guang
2013-05-28 6:31 ` Michael S. Tsirkin
2013-05-28 6:40 ` li guang
2013-05-28 6:48 ` Michael S. Tsirkin
2013-05-28 8:26 ` Igor Mammedov
2013-05-28 8:40 ` li guang
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=20130524114528.GC7046@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=brogers@suse.com \
--cc=jschopp@linux.vnet.ibm.com \
--cc=kraxel@redhat.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=yamahata@valinux.co.jp \
/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).