qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brendan Trotter <btrotter@gmail.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: bochs-developers@lists.sourceforge.net, aliguori@us.ibm.com,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Bochs-developers] [PATCH 1/2] create acpi cpu definitions
Date: Sun, 19 Apr 2009 23:34:43 +0930	[thread overview]
Message-ID: <b1ebdcad0904190704k60987835g2f05e9221915aaed@mail.gmail.com> (raw)
In-Reply-To: <20090419111249.GD10126@redhat.com>

Hi,

On Sun, Apr 19, 2009 at 8:42 PM, Gleb Natapov <gleb@redhat.com> wrote:
> On Sun, Apr 19, 2009 at 11:01:09AM +0930, Brendan Trotter wrote:
>> For some reason (unknown to me) some Linux developers made wild
>> assumptions about disabled "Processor Local APIC" entries, and now
>> they're inventing fictitious hardware to support their unfounded
>> assumptions.
>>
>> Please, correct me if I'm wrong...
>>
> Windows 2008 supports CPU hot plug (but not unplug IIRC). How they do it
> if there is not specification about how it should work on 80x86?

Unfortunately, "no specification" typically means hardware
manufacturers are free to make up their own way of doing it - for all
I know Windows 2008 needs a special driver for each system.

I've been unable to find any 80x86 hardware that supports hot-add and
hot-remove of CPUs, and therefore I haven't been able to attempt to
find out how this hardware notifies the OS of capabilities, changes,
etc. The closest thing I did find is redundant CPUs, but I couldn't
find anything with details on how this works, and don't know if the OS
itself is made aware of it at all (the chipset and firmware might
replaced a failing CPU with a spare/redundant CPU without the OS's
knowledge).

I did find a little information for hot add/remove for Itanium
systems, but nothing very detailed. From
"http://www.itaniumsolutions.org/resources/focus_on_dynamic_hardware_partitioning__nec_microsoft_intel":
   "The NEC Express5800/1000 Series of servers, utilizes the Intel
Itanium Machine Check Architecture (for error handling), and adds
another layer of intelligence through a service processor and related
software called the GlobalMaster (managed via either a GUI or CLI), as
shown in Figure 1. The GlobalMaster also communicates with Microsoft
Windows Server 2008 to convey to the operating system that a hot add
(of processors, memory, or I/O) or hot replace (of processors and
memory) is taking place."

This sounds like a lot more involved than just misappropriating a flag
in an ACPI table...



Cheers,

Brendan

  reply	other threads:[~2009-04-19 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 20:57 [Qemu-devel] [PATCH 0/2] CPU hotplug support Glauber Costa
2009-04-17 20:57 ` [Qemu-devel] [PATCH 1/2] create acpi cpu definitions Glauber Costa
2009-04-17 20:57   ` [Qemu-devel] [PATCH 2/2] kvm: bios: remove acpi_build_processor_ssdt Glauber Costa
2009-04-18 21:50   ` [Qemu-devel] Re: [Bochs-developers] [PATCH 1/2] create acpi cpu definitions Sebastian Herbszt
2009-04-19  1:31     ` Brendan Trotter
2009-04-19 11:12       ` Gleb Natapov
2009-04-19 14:04         ` Brendan Trotter [this message]
2009-04-19 21:55         ` Sebastian Herbszt
2009-04-20  5:28           ` Gleb Natapov

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=b1ebdcad0904190704k60987835g2f05e9221915aaed@mail.gmail.com \
    --to=btrotter@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=bochs-developers@lists.sourceforge.net \
    --cc=gleb@redhat.com \
    --cc=qemu-devel@nongnu.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).