From: Andi Kleen <andi@firstfloor.org>
To: Jack Steiner <steiner@sgi.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <andi@firstfloor.org>,
tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 8/8] x86_64: Support for new UV apic
Date: Sun, 30 Mar 2008 23:18:48 +0200 [thread overview]
Message-ID: <20080330211848.GA29105@one.firstfloor.org> (raw)
In-Reply-To: <20080330210356.GA13383@sgi.com>
> If there was a significant differece between UV and generic kernels
> (or hardware), then I would agree. However, the only significant
> difference is the APIC model on large systems. Small systems are
> exactly compatible.
>
> The problem with subarch is that we want 1 binary kernel to support
x86-64 subarchs are more options than true subarchs. They generally
do not prevent the kernel from running on other systems, just
control addition of some additional code or special data layout. They are
quite different from the i386 subarchs or those of other architectures.
The main reason vSMP is called a subarch is that it pads a lot
of data structures to 4K and you don't really want that on your
normal kernel, but there isn't anything in there that would
prevent booting on a normal system.
The UV option certainly doesn't have this issue.
> both generic hardware AND uv hardware. This restriction is desirable
> for the distros and software vendors. Otherwise, additional kernel
> images would have to be built, released, & certified.
I think an option would be fine, just don't call it a subarch. I don't
feel strongly about it, as you point out it is not really very much
code.
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-03-30 21:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 18:21 Jack Steiner
2008-03-25 10:25 ` Andi Kleen
2008-03-25 17:56 ` Jack Steiner
2008-03-25 18:06 ` Andi Kleen
2008-03-26 2:23 ` Jeremy Fitzhardinge
2008-03-26 3:22 ` Glauber Costa
2008-03-26 7:29 ` Ingo Molnar
2008-03-26 7:38 ` Ingo Molnar
2008-03-30 20:23 ` Yinghai Lu
2008-03-30 21:03 ` Jack Steiner
2008-03-30 21:18 ` Andi Kleen [this message]
2008-03-30 23:29 ` Yinghai Lu
2008-03-31 2:18 ` Jack Steiner
2008-03-31 2:20 ` Yinghai Lu
2008-03-31 12:33 ` Ingo Molnar
2008-03-31 12:52 ` Andi Kleen
2008-03-31 18:42 ` Yinghai Lu
2008-03-31 6:48 ` Andi Kleen
2008-03-25 14:30 ` Ingo Molnar
2008-03-25 16:31 ` Jack Steiner
2008-03-26 3:24 ` Glauber Costa
2008-03-30 20:41 ` Yinghai Lu
2008-03-30 21:08 ` Jack Steiner
2008-03-30 23:24 ` Yinghai Lu
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=20080330211848.GA29105@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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