From: Andi Kleen <ak@muc.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
Natasha Jarymowycz <natasha@us.ibm.com>,
"Subrahmanian, Raj" <raj.subrahmanian@unisys.com>,
"Davis, Jason" <jason.davis@unisys.com>,
"Vessey, Bruce A" <Bruce.Vessey@unisys.com>
Subject: Re: Genapic
Date: 25 May 2005 17:26:34 +0200
Date: Wed, 25 May 2005 17:26:34 +0200 [thread overview]
Message-ID: <20050525152634.GD86087@muc.de> (raw)
In-Reply-To: <26b3839037396bdeb5cfef7a49efb6f5@cl.cam.ac.uk>
On Tue, May 24, 2005 at 09:22:47PM +0100, Keir Fraser wrote:
>
> On 24 May 2005, at 20:58, Puthiyaparambil, Aravindh wrote:
>
> >I am fine with going down the x86_64 genapic route for Xen. The only
> >thing is that I know that IRQ overrides are not present in the x86_64
> >genapic. So that might have to be brought over for the ES7000.
> >
> >I would like to start working on bringing the x86_64 code over. Will
> >this clash with anyone else?
>
> I'm about halfway through bringing i386 platform code over. I'm working
> on smp bootup and cpumask_t right now, but genapic is next and should
> be quite simple. I'd rather take the more flexible i386 code in the
> first instance (which will immediately support es7000, for example) and
It is actually not more flexible at all for the dynamic case.
With a static compile you have some more choices, should you really
want to support the Numasaurus (aka NUMAQ) or SGI Visual Workstation
(kind of a SGI O2 with a x86 CPU) or Voyager (NUMA 486). Somehow I cannot
imagine you really want that though, these are all quite old and obscure
machines.
A lot of the cruft in the i386 layer even comes from PC98 support
(which was a old Japanese not quite PC x86 platform), which was later
dropped because it was unmaintained. The hooks it needed were
never cleaned up unfortunately.
-Andi
next prev parent reply other threads:[~2005-05-25 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 19:58 Genapic Puthiyaparambil, Aravindh
2005-05-24 20:22 ` Genapic Keir Fraser
2005-05-25 15:26 ` Andi Kleen [this message]
2005-05-25 15:21 ` Genapic Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-05-19 21:10 Genapic Puthiyaparambil, Aravindh
2005-05-20 19:07 ` Genapic Andi Kleen
2005-05-18 18:26 Genapic Nakajima, Jun
2005-05-18 17:44 Genapic Puthiyaparambil, Aravindh
2005-05-18 17:21 Genapic Nakajima, Jun
2005-05-18 15:45 Genapic Puthiyaparambil, Aravindh
2005-05-18 16:36 ` Genapic Andi Kleen
2005-05-18 16:54 ` Genapic Keir Fraser
2005-05-18 16:56 ` Genapic Andi Kleen
2005-05-18 19:45 ` Genapic Natasha Jarymowycz
2005-05-20 19:02 ` Genapic Andi Kleen
2005-05-18 13:59 Genapic Puthiyaparambil, Aravindh
2005-05-18 15:24 ` Genapic Keir Fraser
2005-05-17 21:18 Genapic Puthiyaparambil, Aravindh
2005-05-18 7:34 ` Genapic Keir Fraser
2005-05-18 13:57 ` Genapic Andi Kleen
2005-05-18 15:23 ` Genapic Keir Fraser
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=20050525152634.GD86087@muc.de \
--to=ak@muc.de \
--cc=Bruce.Vessey@unisys.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jason.davis@unisys.com \
--cc=natasha@us.ibm.com \
--cc=raj.subrahmanian@unisys.com \
--cc=xen-devel@lists.xensource.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.