mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	keith maanthey <kmannth@us.ibm.com>
Subject: Re: [PATCH] linux-2.5.69_subarch-fix_A0.patch
Date: 15 May 2003 10:46:03 -0700	[thread overview]
Message-ID: <1053020763.9629.104.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <20030515172855.GA10831@Wotan.suse.de>

On Thu, 2003-05-15 at 10:28, Andi Kleen wrote:
> > You did get around it in the generic subarch (which I love, by the way,
> > thanks so much for doing that work), but in a roundabout way. (via
> > #ifdef APIC_DEFINITION trickery). 
> 
> The best fix is probably to just remove the summit selection and replace
> it with the generic architecture.

I'd agree (long term even more strongly), although along with that I'd
like to be able to pick and choose my subarch. So I can have a kernel
that supports say, PC and BigSMP, but not NUMAQ or whatever. I believe
this is doable with your infrastructure, but I'm not sure how much work
it will take. 

And before we make any larger changes, I'd like to just get stuff
compiling first (Keith's apic patch landing about the same time and
broke generic, and generic broke summit so right now neither subarch
builds properly). 

thanks
-john





  reply	other threads:[~2003-05-15 17:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  2:37 john stultz
2003-05-15  6:51 ` Andi Kleen
2003-05-15 17:20   ` john stultz
2003-05-15 17:28     ` Andi Kleen
2003-05-15 17:46       ` john stultz [this message]
2003-05-15 19:00         ` Andi Kleen
2003-05-15 19:19           ` William Lee Irwin III
2003-05-15 17:17             ` Martin J. Bligh
2003-05-15 19:50             ` Andi Kleen
2003-05-15 19:55               ` William Lee Irwin III
2003-05-15 17:45                 ` Martin J. Bligh

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=1053020763.9629.104.camel@w-jstultz2.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=ak@suse.de \
    --cc=akpm@digeo.com \
    --cc=kmannth@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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
all inboxes | Powered by JetHome®