From: Andi Kleen <ak@muc.de>
To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@unisys.com>
Cc: xen-devel@lists.xensource.com, 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: 20 May 2005 21:07:50 +0200
Date: Fri, 20 May 2005 21:07:50 +0200 [thread overview]
Message-ID: <20050520190750.GC57598@muc.de> (raw)
In-Reply-To: <EF8D308BE33AF54D8934DF26520252D301D206CC@USTR-EXCH5.na.uis.unisys.com>
On Thu, May 19, 2005 at 05:10:02PM -0400, Puthiyaparambil, Aravindh wrote:
> For the moment I think it is best we follow Natasha's suggestion and
> work towards bringing in the i386 genapic mode.
>
> Comments?
(as having written i386 genapic originally) All this would
get you is much historical cruft that Xen really doesnt need.
-Andi
next prev parent reply other threads:[~2005-05-20 19:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 21:10 Genapic Puthiyaparambil, Aravindh
2005-05-20 19:07 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-24 19:58 Genapic Puthiyaparambil, Aravindh
2005-05-24 20:22 ` Genapic Keir Fraser
2005-05-25 15:26 ` Genapic Andi Kleen
2005-05-25 15:21 ` 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=20050520190750.GC57598@muc.de \
--to=ak@muc.de \
--cc=Bruce.Vessey@unisys.com \
--cc=aravindh.puthiyaparambil@unisys.com \
--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.