From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: ACPI
Date: Fri, 22 Nov 2013 21:31:08 +0100 [thread overview]
Message-ID: <201311222131.08787.arnd@arndb.de> (raw)
In-Reply-To: <528ED801.8040705@jonmasters.org>
On Friday 22 November 2013, Jon Masters wrote:
> By 64-bit ARM server, I mean a system conformant with a series of
> specifications that define what such a server system consists of. It
> might be a physical system featuring an ARM-based SoC containing a core
> conformant to the v8 Architecture, along with standardized peripherals,
> or it might be a virtual platform. The boot architecture would include
> UEFI (specifically a sequential progression from an initial EL3 reset
> secure ROM on through to a verified Tiano build), and ACPI being used to
> convey the platform devices, as well as for runtime event delivery.
Ok, that narrows it down a little, although not in the way I expected.
It seems there is a secret spec along the lines of the older PREP, CHRP,
PAPR. Since the group behind this spec has not yet revealed itself, I will
refer to them as SPECTRE (maybe that should be SPCTR?) for the sake of
discussion.
>From your description, it sounds like SPECTRE is actually trying to make
the job easier for the operating system to some degree by defining a
standard hardware platform. If this actually works out and they hardware
people don't screw up too much, supporting that platform should be
a no-brainer, and I see no fundamental problem with adding ACPI support
for that.
What I also take away from this is that we should not any ACPI support
for platforms that are not SPECTRE compliant, because that would
add a long-term maintainance cost without the benefits, especially
if it ends up implementing an incompatible ACPI dialect. I certainly
don't want to have to maintain two or more versions of ACPI (e.g.
one doing power management using AML and one using SoC specific
device drivers).
Unfortunately it is impossible to know at this point what work is
actually relevant for SPECTRE and what is not, so we can't really
merge anything specific to ARM64+ACPI until we have access to an
actual spec, or we get a video message by someone with a monocle
and a lap cat to shed some more light on the actual requirements.
There is also the danger that either the SPECTRE spec or the
actual implementations are so screwed up that we still wouldn't
merge anything, but you can probably judge better how likely that
worst-case scenario is.
Those people that have inside knowledge of SPECTRE can in the meantime
work on the patches and get them reviewed (I think this is happening
anyway), and we can certainly keep working with Intel to enable
whatever features they need for embedded x86 with ACPI.
> I expect to see a series of useful announcements soon that will serve to
> articulate what I am referring to by an ARM v8 server. I will followup
> then with more thoughts about how this fits together.
Sounds good.
Arnd
next prev parent reply other threads:[~2013-11-22 20:31 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 18:42 ACPI Jon Masters
[not found] ` < CACRpkdbNxxNK0GM28H_nDLu6EpbQ-EYAdEeTp5fnXW5mkEPkgw@mail.gmail.com>
[not found] ` < CACxGe6uHuWPh7d9NaVuPRBWq0Fh1BmDV190KEN4C4uaq4KjS8g@mail.gmail.com>
[not found] ` < CACRpkdaCXJzWXoesjD3Jqpm4XMHLQp3SsHcsDG3veUS+xarqHQ@mail.gmail.com>
[not found] ` < CACxGe6vUKzow7QpeX2mU7CiZQzY8aZ+p0jd8Vk0+dqz0B=D0Ew@mail.gmail.com>
[not found] ` < CACRpkdY+6dzs8MpKKtW-3kzsLkZjsit9SeN20k_33TAtVf3NEA@mail.gmail.com>
[not found] ` < CACxGe6t_9hUXL_1PHRU=2DYOYfCqZykd7gYRCshZn0XsVoCdRw@mail.gmail.com>
[not found] ` < 20131126183344.GA16074@srcf.ucam.org>
2013-11-19 18:15 ` ACPI Arnd Bergmann
2013-11-21 20:03 ` ACPI Mark Brown
2013-11-22 0:29 ` ACPI Arnd Bergmann
2013-11-22 4:05 ` ACPI Jon Masters
2013-11-22 20:31 ` Arnd Bergmann [this message]
2013-11-22 20:59 ` ACPI Jon Masters
2013-11-22 21:37 ` ACPI Jon Masters
2013-11-23 9:11 ` ACPI Arnd Bergmann
2013-11-23 18:39 ` ACPI Jason Gunthorpe
2013-11-23 23:03 ` ACPI Matthew Garrett
2013-11-24 3:52 ` ACPI Jon Masters
2013-11-24 3:56 ` ACPI Matthew Garrett
2013-11-24 23:21 ` ACPI Jon Masters
2013-11-24 23:40 ` ACPI Matthew Garrett
2013-11-22 13:19 ` ACPI Mark Brown
2013-11-19 18:28 ` ACPI Måns Rullgård
2013-11-21 16:56 ` ACPI Matthew Garrett
2013-11-24 17:14 ` ACPI Linus Walleij
2013-11-25 0:42 ` ACPI Grant Likely
2013-11-25 1:28 ` ACPI Matthew Garrett
2013-11-25 11:07 ` ACPI Linus Walleij
2013-11-25 11:33 ` ACPI Grant Likely
2013-11-25 15:41 ` ACPI Matthew Garrett
2013-11-26 12:43 ` ACPI Linus Walleij
2013-11-26 12:55 ` ACPI Grant Likely
2013-11-26 13:43 ` ACPI Jürgen Beisert
2013-11-27 12:25 ` ACPI Grant Likely
2013-11-28 13:16 ` ACPI Linus Walleij
2013-11-26 18:33 ` ACPI Matthew Garrett
2013-11-26 23:11 ` ACPI Matt Sealey
2013-11-26 23:32 ` ACPI Matthew Garrett
2013-11-27 11:00 ` ACPI Catalin Marinas
2013-11-27 22:12 ` ACPI Nicolas Pitre
2013-11-27 20:21 ` ACPI Matt Sealey
2013-11-28 6:21 ` ACPI Jon Masters
2013-11-28 18:26 ` ACPI Stefano Stabellini
2013-11-28 18:48 ` ACPI Matthew Garrett
2013-11-28 18:51 ` ACPI Stefano Stabellini
2013-11-27 14:16 ` ACPI Grant Likely
2013-11-27 22:17 ` ACPI Matt Sealey
2013-11-28 13:50 ` ACPI Leif Lindholm
2013-11-28 15:43 ` ACPI Grant Likely
2013-11-27 12:41 ` ACPI Grant Likely
2013-11-26 14:45 ` ACPI Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2023-12-16 9:45 ACPI Heinrich Schuchardt
2023-12-20 5:57 ` ACPI Anup Patel
2009-08-17 11:53 acpi Michael Lestoquoy
2009-01-08 15:50 ACPI Florian Sylla
2008-10-10 20:32 ACPI jd
2008-10-10 21:58 ` ACPI Bryon Roche
2008-10-12 12:30 ` ACPI Avi Kivity
2008-10-07 17:46 ACPI Manuel Alberer
2008-04-13 7:24 ACPI Moshe Aldelmen
2008-04-07 16:54 ACPI Lademann, Klaus
2008-04-07 19:26 ` ACPI Alexey Starikovskiy
2007-10-21 16:20 ACPI Thomas Knox
2004-06-02 2:14 ACPI Zhu, Yi
2004-06-02 1:35 ACPI Bruce Park
2004-04-09 18:04 ACPI Trever L. Adams
2002-05-25 7:54 ACPI Russell Coker
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=201311222131.08787.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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 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.