From: James Cleverdon <jamesclv@us.ibm.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org, James.Bottomley@steeleye.com,
torvalds@transmeta.com, alan@redhat.com, mingo@redhat.com
Subject: Re: [PATCH] Summit patch for 2.5.34
Date: Mon, 16 Sep 2002 14:24:14 -0700 [thread overview]
Message-ID: <200209161424.14865.jamesclv@us.ibm.com> (raw)
In-Reply-To: <20020916175545.A21875@suse.de>
On Monday 16 September 2002 08:55 am, Dave Jones wrote:
> On Thu, Sep 12, 2002 at 08:35:14PM -0700, James Cleverdon wrote:
> > Patch that allows IBM x440 boxes to on-line all CPUs and interrupt
> > routing for x360s. Fixed x360 ID bug.
>
> Couple questions/comments.
>
> - Is this the same summit code as is in 2.4-ac ?
> (Ie, the one that boots on non summit systems too)
Yes, save for the dynamic TPR enhancement. (Already addressed by Alan, etc,
in other postings.)
> - I believe the way forward here is to work with James Bottomley,
> who has a nice abstraction of the areas your patch touches for
> his Voyager sub-architecture.
> Linus has however been completley silent on the x86-subarch idea
> despite heavyweights like Alan and Ingo adding their support...
> If you go this route, James' base needs to go in first
> (converting just the in-kernel visws support). After which, adding
> support for Voyager, Summit and any other wacky x86esque hardware
> is a simple non-intrusive patch that touches subarch specific areas.
> - Some of the code you've added looks along the lines of..
>
> if (numaq)
> foo();
> else if (summit)
> foo2();
> else
> foo3();
>
> Would it be over-abstracting to have some form of APIC struct,
> defining pointers to various routines instead of lots of ugly
> if's/switches/fall-through's.
>
> However, the last point may be completley pointless after adapting to
> use what James B has come up with..
>
> Dave
All the if/else chains are in init code, where a few more microseconds for
some extra branches isn't important. However, a nice sub-arch abstraction
would be welcome.
Thanks!
--
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com
prev parent reply other threads:[~2002-09-16 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 3:35 [PATCH] Summit patch for 2.5.34 James Cleverdon
2002-09-16 15:55 ` Dave Jones
2002-09-16 16:15 ` Alan Cox
2002-09-16 16:27 ` Dave Jones
2002-09-16 19:03 ` James Cleverdon
2002-09-16 21:24 ` James Cleverdon [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=200209161424.14865.jamesclv@us.ibm.com \
--to=jamesclv@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=alan@redhat.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@transmeta.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 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.