From: Benjamin LaHaise <bcrl@kvack.org>
To: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
fastboot@lists.osdl.org, ebiederm@xmission.com, ak@suse.de,
akpm@linux-foundation.org, judith@linux-foundation.org
Subject: Re: [PATCH RFC 0/5] hard_smp_processor_id overhaul
Date: Thu, 1 Mar 2007 09:06:48 -0500 [thread overview]
Message-ID: <20070301140648.GX26583@kvack.org> (raw)
In-Reply-To: <1172733373.1498.264.camel@sebastian.intellilink.co.jp>
On Thu, Mar 01, 2007 at 04:16:13PM +0900, Fernando Luis Vázquez Cao wrote:
> As a consequence, the hardcoding of hard_smp_processor_id() to 0 on UP
> systems (see "linux/smp.h") is not correct.
>
> This patch-set does the following:
>
> 1- Remove hardcoding of hard_smp_processor_id on UP systems.
NAK. This has to be configurable, as many embedded systems don't even
have APICs. Please rework the patch set so that there is not any overhead
for existing UP systems.
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <zyntrop@kvack.org>.
next prev parent reply other threads:[~2007-03-01 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 7:16 [PATCH RFC 0/5] hard_smp_processor_id overhaul Fernando Luis Vázquez Cao
2007-03-01 14:06 ` Benjamin LaHaise [this message]
2007-03-02 3:10 ` Fernando Luis Vázquez Cao
2007-03-02 4:14 ` [Fastboot] " Vivek Goyal
2007-03-02 8:06 ` Fernando Luis Vázquez Cao
2007-03-02 8:16 ` [PATCH] hard_smp_processor_id definition for UP systems without APIC (i386) Fernando Luis Vázquez Cao
2007-03-02 7:23 ` [Fastboot] [PATCH RFC 0/5] hard_smp_processor_id overhaul Horms
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=20070301140648.GX26583@kvack.org \
--to=bcrl@kvack.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=fernando@oss.ntt.co.jp \
--cc=judith@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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.