public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-ia64@vger.kernel.org, ashok.raj@intel.com, steiner@sgi.com,
	tony.luck@intel.com,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC][PATCH] ia64 node hotplug -- cpu - node relationship fix [0/2] intro
Date: Fri, 26 May 2006 10:23:07 +0000	[thread overview]
Message-ID: <20060526184011.EEAA.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <20060526175622.13057d7e.kamezawa.hiroyu@jp.fujitsu.com>

> 1. empty-node-fix : avoid creating empty node
>    SRAT's enable bit just shows 'you can read this entry'. But the kernel know
>    this and checks each entries are vaild or not later.
>
>    But pxm_bit/node_online_mask is not treated as they should be.
>    The kernel creates empty node, which has no cpu, no memory.

I would like to mention about background of this more.

I thought if enable bit of each SRAT entry is on, then its entry's
object is usable for OS.

However, SRAT specification says only
"If clear, the OSPM ignores the contents of the Processor Local
 APIC/SAPIC (or Memory) Affinity Structure."

So, our firmware team (or Micro $oft) interprets this
"If enable bit is on, then this entry is just readable by OS.
 The object of its entry MIGHT NOT EXIST. This entry can be used for
 reserve resource for memory/cpu which can be hot-add later."
They implemented it.

I really really hate this. :-(
But, indeed, ACPI spec. says just IGNORE if clear. They are correct.

Current linux code checks memory and cpu existence by other ways.
But, PXM remains even if they don't exist. The first patch is to remove it.

Bye.

-- 
Yasunori Goto 



      parent reply	other threads:[~2006-05-26 10:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26  8:56 [RFC][PATCH] ia64 node hotplug -- cpu - node relationship fix [0/2] KAMEZAWA Hiroyuki
2006-05-26  9:02 ` [RFC][PATCH] ia64 node hotplug -- cpu - node relationship fix [1/2] KAMEZAWA Hiroyuki
2006-05-26  9:05 ` [RFC][PATCH] ia64 node hotplug -- cpu - node relationship fix [2/2] KAMEZAWA Hiroyuki
2006-05-26  9:06 ` [RFC][PATCH] ia64 node hotplug -- cpu - node relationship fix KAMEZAWA Hiroyuki
2006-05-26 10:23 ` Yasunori Goto [this message]

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=20060526184011.EEAA.Y-GOTO@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=ashok.raj@intel.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox