From: Wei Huang <wei@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>,
"'Peter Maydell'" <peter.maydell@linaro.org>,
"'Igor Mammedov'" <imammedo@redhat.com>
Cc: 'G Gregory' <graeme.gregory@linaro.org>,
"'Michael S. Tsirkin'" <mst@redhat.com>,
"'Huangpeng \(Peter\)'" <peter.huangpeng@huawei.com>,
'QEMU Developers' <qemu-devel@nongnu.org>,
'qemu-arm' <qemu-arm@nongnu.org>,
'Shannon Zhao' <shannon.zhao@linaro.org>,
'Shannon Zhao' <zhaoshenglong@huawei.com>
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH v3 1/8] hw/arm/virt: Add a GPIO controller
Date: Tue, 1 Dec 2015 09:29:19 -0600 [thread overview]
Message-ID: <565DBCCF.7050404@redhat.com> (raw)
In-Reply-To: <01d201d12c47$5a77dd00$0f679700$@samsung.com>
On 12/01/2015 08:48 AM, Pavel Fedin wrote:
> Hello!
>
>>>> ACPI 5.0 supports GPIO-signaled ACPI Events. This can be used for
>>>> powerdown, hotplug evnets. Add a GPIO controller in machine virt,
>>> s/evnets/events/
>>>
>>>> to support powerdown, maybe can be used for cpu hotplug. And
>>>> here we use pl061.
>
> Sorry for late jumping in, but this was the first message Cc'ed to me.
> With these devices virt machine IMHO goes farther and farther away from its initial goal: be a minimalistic virtual box, which ensures maximum possible compatibility and portability.
> virt machine already supports poweroff using PSCI interface. Why we need to add more hardware? Can't ACPI deal with PSCI?
PSCI handles the actions initiated from the inside of OS. Examples
include system shutdown and hotplug (still inside OS). From this
perspective PSCI works well. However this communication is
one-direction: there isn't a way to communicate from the outside (e.g.
libvirt) to the guest OS. For instance, "system_powerdown" qmp command
won't work because guest OS can't receive the notification.
> To tell the truth, i dislike ACPI + EFI thing at all. It looks like cramming PC-oriented firmware into architecture for which it was never meant to be written. Too much overcomplications, we drop already established things and reinvent a (triangular) wheel, but what's the purpose? Is it being done only because vendors want obscure proprietary firmware instead of old good u-boot?
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
WARNING: multiple messages have this Message-ID (diff)
From: Wei Huang <wei@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>,
'Peter Maydell' <peter.maydell@linaro.org>,
'Igor Mammedov' <imammedo@redhat.com>
Cc: 'G Gregory' <graeme.gregory@linaro.org>,
"'Michael S. Tsirkin'" <mst@redhat.com>,
"'Huangpeng (Peter)'" <peter.huangpeng@huawei.com>,
'QEMU Developers' <qemu-devel@nongnu.org>,
'qemu-arm' <qemu-arm@nongnu.org>,
'Shannon Zhao' <shannon.zhao@linaro.org>,
'Shannon Zhao' <zhaoshenglong@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/8] hw/arm/virt: Add a GPIO controller
Date: Tue, 1 Dec 2015 09:29:19 -0600 [thread overview]
Message-ID: <565DBCCF.7050404@redhat.com> (raw)
In-Reply-To: <01d201d12c47$5a77dd00$0f679700$@samsung.com>
On 12/01/2015 08:48 AM, Pavel Fedin wrote:
> Hello!
>
>>>> ACPI 5.0 supports GPIO-signaled ACPI Events. This can be used for
>>>> powerdown, hotplug evnets. Add a GPIO controller in machine virt,
>>> s/evnets/events/
>>>
>>>> to support powerdown, maybe can be used for cpu hotplug. And
>>>> here we use pl061.
>
> Sorry for late jumping in, but this was the first message Cc'ed to me.
> With these devices virt machine IMHO goes farther and farther away from its initial goal: be a minimalistic virtual box, which ensures maximum possible compatibility and portability.
> virt machine already supports poweroff using PSCI interface. Why we need to add more hardware? Can't ACPI deal with PSCI?
PSCI handles the actions initiated from the inside of OS. Examples
include system shutdown and hotplug (still inside OS). From this
perspective PSCI works well. However this communication is
one-direction: there isn't a way to communicate from the outside (e.g.
libvirt) to the guest OS. For instance, "system_powerdown" qmp command
won't work because guest OS can't receive the notification.
> To tell the truth, i dislike ACPI + EFI thing at all. It looks like cramming PC-oriented firmware into architecture for which it was never meant to be written. Too much overcomplications, we drop already established things and reinvent a (triangular) wheel, but what's the purpose? Is it being done only because vendors want obscure proprietary firmware instead of old good u-boot?
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
next prev parent reply other threads:[~2015-12-01 15:29 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 13:23 [Qemu-devel] [PATCH v3 0/8] Add system_powerdown support on ARM for ACPI and DT shannon.zhao
2015-11-16 13:23 ` [Qemu-devel] [PATCH v3 1/8] hw/arm/virt: Add a GPIO controller shannon.zhao
2015-12-01 13:21 ` Igor Mammedov
2015-12-01 13:49 ` [Qemu-arm] " Peter Maydell
2015-12-01 13:49 ` Peter Maydell
2015-12-01 14:48 ` Pavel Fedin
2015-12-01 14:48 ` Pavel Fedin
2015-12-01 15:25 ` [Qemu-arm] " Shannon Zhao
2015-12-01 15:25 ` Shannon Zhao
2015-12-01 15:29 ` Wei Huang [this message]
2015-12-01 15:29 ` Wei Huang
2015-12-02 9:39 ` [Qemu-arm] " Pavel Fedin
2015-12-02 9:39 ` [Qemu-devel] [Qemu-arm] " Pavel Fedin
2015-11-16 13:23 ` [Qemu-devel] [PATCH v3 2/8] hw/arm/virt-acpi-build: Add GPIO controller in ACPI DSDT table shannon.zhao
2015-11-16 13:23 ` [Qemu-devel] [PATCH v3 3/8] hw/arm/virt-acpi-build: Add power button device " shannon.zhao
2015-12-01 11:41 ` Igor Mammedov
2015-12-01 12:43 ` [Qemu-arm] " Shannon Zhao
2015-12-01 12:43 ` Shannon Zhao
2015-12-01 13:05 ` Igor Mammedov
2015-12-01 13:12 ` [Qemu-arm] " Shannon Zhao
2015-12-01 13:12 ` Shannon Zhao
2015-11-16 13:23 ` [Qemu-devel] [PATCH v3 4/8] hw/acpi/aml-build: Add GPIO Connection Descriptor shannon.zhao
2015-12-03 15:15 ` [Qemu-arm] " Igor Mammedov
2015-12-03 15:15 ` [Qemu-devel] " Igor Mammedov
2015-11-16 13:23 ` [Qemu-devel] [PATCH v3 5/8] hw/acpi/aml-build: Add a wrapper for GPIO Interrupt Connection shannon.zhao
2015-12-03 15:34 ` [Qemu-arm] " Igor Mammedov
2015-12-03 15:34 ` [Qemu-devel] " Igor Mammedov
2015-12-03 15:37 ` [Qemu-arm] " Igor Mammedov
2015-12-03 15:37 ` [Qemu-devel] " Igor Mammedov
2015-11-16 13:23 ` [Qemu-devel] [PATCH v3 6/8] hw/arm/virt-acpi-build: Add _E03 for Power Button shannon.zhao
2015-12-04 14:10 ` [Qemu-arm] " Igor Mammedov
2015-12-04 14:10 ` Igor Mammedov
2015-12-07 7:10 ` [Qemu-arm] " Shannon Zhao
2015-12-07 7:10 ` Shannon Zhao
2015-11-16 13:23 ` [Qemu-devel] [PATCH v3 7/8] hw/arm/virt: Add QEMU powerdown notifier and hook it to GPIO Pin 3 shannon.zhao
2015-11-16 13:23 ` [Qemu-devel] [PATCH v3 8/8] hw/arm/virt: Add gpio-keys node for Poweroff using DT shannon.zhao
2015-11-27 17:16 ` [Qemu-arm] " Peter Maydell
2015-11-27 17:16 ` [Qemu-devel] " Peter Maydell
2015-11-28 3:06 ` [Qemu-arm] " Shannon Zhao
2015-11-28 3:06 ` [Qemu-devel] " Shannon Zhao
2015-11-17 1:37 ` [Qemu-arm] [PATCH v3 0/8] Add system_powerdown support on ARM for ACPI and DT Shannon Zhao
2015-11-17 1:37 ` [Qemu-devel] " Shannon Zhao
2015-12-01 13:43 ` Igor Mammedov
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=565DBCCF.7050404@redhat.com \
--to=wei@redhat.com \
--cc=graeme.gregory@linaro.org \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=p.fedin@samsung.com \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.