From: Ashok Raj <ashok.raj@intel.com>
To: Paul Jackson <pj@sgi.com>
Cc: akpm@osdl.org, ashok.raj@intel.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: ia64-cpu-hotplug-cpu_present.patch?
Date: Wed, 28 Apr 2004 07:52:55 -0700 [thread overview]
Message-ID: <20040428075255.A8859@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040427225741.2fe78d88.pj@sgi.com>; from pj@sgi.com on Tue, Apr 27, 2004 at 10:57:41PM -0700
On Tue, Apr 27, 2004 at 10:57:41PM -0700, Paul Jackson wrote:
Hi Paul,
sorry for the trouble. I will try to address them, and will try to resolve the compile problem
you are having.
> I cannot find any mention of it on lkml or any other email list that
> either Google or I track.
>
> Is there some backdoor path to Andrew's patch directory I don't know of ;)?
I sent the patch to linux-ia64, but forgot to copy lkml. No... i did not buy crispy
cream for andrew.. although that did cross my mine :-)
Some of the points you raise, i will look into, but here is a quick summary fo Paul's top 10
list!.
cpu_present is required so that when cpu_up is called in smp_init() we dont call for all
possible cpu's but just for cpu's physically present.
cpu_possible - indicates cpu may be available, but may not be present in the system. Hence
different from phys_cpu_present_mask
cpu_possible wont change dynamically but present_map can change depending on the arrival of
cpu's in a system. I implemented it for only ia64, and expection is that ACPI or its equilvalent
would populate cpu_present_map dynamically.
In architectures that dont have cpu_hotplug capability, i have kept cpu_present and possible the same.
Once i take a look at the failures, i will send you an updated patch. again really sorry for the
inconvenience.
Cheers,
ashok
next prev parent reply other threads:[~2004-04-28 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 5:57 ia64-cpu-hotplug-cpu_present.patch? Paul Jackson
2004-04-28 14:52 ` Ashok Raj [this message]
2004-04-28 16:05 ` ia64-cpu-hotplug-cpu_present.patch? Paul Jackson
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=20040428075255.A8859@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=akpm@osdl.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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