From: Bill Davidsen <davidsen@tmr.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Guo, Racing" <racing.guo@intel.com>, Andi Kleen <ak@muc.de>,
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: Tue, 03 May 2005 12:16:48 -0400 [thread overview]
Message-ID: <4277A3F0.1010807@tmr.com> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB60049EED02@scsmsx403.amr.corp.intel.com>
Pallipadi, Venkatesh wrote:
> I think what Andi meant was that instead of copying code from x86-64
> to i386 and making x86-64 link to this i386 copy, you can leave the
> code in x86-64 and link it from i386 part of the tree.
>
> Doing it either way should be OK with this mce code. But I feel,
> despite of the patch size, it is better to keep all the shared
> code in i386 tree and link it from x86-64. Otherwise, it may become
> kind of messy in future, with various links between i386 and x86-64.
> Andi/Andrew: What do you suggest here?
Have you considered having a tree just for the shared code and links
where appropriate? If nothing else that would make it blindingly obvious
that the code was shared, and avoid having someone do something
unsharable because s/he didn't know there was a pointer to the code
elsewhere.
I know it's slightly more complex, but also slightly safer.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-05-03 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 16:15 [PATCH]porting lockless mce from x86_64 to i386 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-02 1:01 Guo, Racing
2005-05-02 16:10 ` Andi Kleen
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=4277A3F0.1010807@tmr.com \
--to=davidsen@tmr.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=racing.guo@intel.com \
--cc=venkatesh.pallipadi@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