From: Andi Kleen <ak@muc.de>
To: "Guo, Racing" <racing.guo@intel.com>
Cc: Andrew Morton <akpm@osdl.org>, "Yu, Luming" <luming.yu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]porting lockless mce from x86_64 to i386
Date: 2 May 2005 18:10:29 +0200
Date: Mon, 2 May 2005 18:10:29 +0200 [thread overview]
Message-ID: <20050502161029.GF27150@muc.de> (raw)
In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD305750162F6F1@pdsmsx402.ccr.corp.intel.com>
On Mon, May 02, 2005 at 09:01:53AM +0800, Guo, Racing wrote:
> >
> >If Luming would not move the mce.c file from x86-64 to i386 then
> >his patch would be only 1/4 as big. I dont know why he does this
> >anyways, it seems completely pointless.
>
> mce.c mce.h and mce_intel.c are moved from x86_64 to i386. so the
> patch is very big. The motivation is to share mce code between
> x86_64 and i386 and avoid duplicate code in x86_64 and i386.
> I don't know whether I completely understand what you point.
> Correct me if I am wrong.
You can share code as well by linking it from x86-64 into i386,
not only the other way round. This is already done for earlyprintk
for example.
-Andi
next prev parent reply other threads:[~2005-05-02 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 1:01 [PATCH]porting lockless mce from x86_64 to i386 Guo, Racing
2005-05-02 16:10 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-02 16:15 Pallipadi, Venkatesh
2005-05-02 17:15 ` Andi Kleen
2005-05-02 18:31 ` Andrew Morton
2005-05-02 19:11 ` Andi Kleen
2005-05-02 19:36 ` Andrew Morton
2005-05-05 15:14 ` Adrian Bunk
2005-05-03 16:16 ` Bill Davidsen
2005-04-29 16:42 Yu, Luming
[not found] <200504261327.30928.luming.yu@intel.com>
2005-04-27 12:38 ` Andi Kleen
2005-04-27 18:38 ` Andrew Morton
2005-04-29 15:27 ` Andi Kleen
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=20050502161029.GF27150@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=racing.guo@intel.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