linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jonathan@jonmasters.org (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: ACPI
Date: Thu, 21 Nov 2013 23:05:21 -0500	[thread overview]
Message-ID: <528ED801.8040705@jonmasters.org> (raw)
In-Reply-To: <201311220129.54828.arnd@arndb.de>

Hi Arnd,

On 11/21/2013 07:29 PM, Arnd Bergmann wrote:
> On Thursday 21 November 2013, Mark Brown wrote:
>> On Tue, Nov 19, 2013 at 07:15:57PM +0100, Arnd Bergmann wrote:
>>
>>> of them apply here. You keep saying "servers", but that isn't actually
>>> a feature of how the system is designed, rather than what is running
>>> on them. Given these examples (or any others, you could come up with),
>>> which ones do you actually see as relevant here:
>>
>>> 1. An exterprise server (SPARC enterprise M9000, Power 795, Integrity
>>>    Superdome) with the CPU core changed to run ARM instructions
>>> 2. An ATX whitebox server mainboard with one to four sockets and PC
>>>    peripherals and plug-compatible ARM CPU chips.
>>> 3. A purpose-built server SoC based on standard components
>>> 4. A new server SoC based on an older proprietary embedded or mobile
>>>    SoC design (think Exynos, OMAP, Snapdragon, ... based)
>>> 5. A server built from using a cheap devboard (BeagleBone, Cubieboard, ...
>>>    style) with an unmodified SoC.
>>> 6. A virtual machine running on KVM or Xen.

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.

>> I'd also ask if we need to consider desktops and laptops here - do we
>> really mean distros here rather than servers, even if servers are the
>> primary use case for distros right now?
> 
> Jon has previously said (multiple times) that he cares about servers
> only, so I assume that is still given. If you take the exact same
> hardware and firmware and add a PCIe GPU to turn it into a workstation
> or laptop, I don't see that change anything from the kernel perspective,
> but I'm trying to narrow the scope here, not widen it ;-)

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.

Thanks,

Jon.

  reply	other threads:[~2013-11-22  4:05 UTC|newest]

Thread overview: 45+ 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       ` Jon Masters [this message]
2013-11-22 20:31         ` ACPI Arnd Bergmann
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

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=528ED801.8040705@jonmasters.org \
    --to=jonathan@jonmasters.org \
    --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 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).