From: "L. A. Walsh" <lkml@tlinx.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org
Subject: Re: i386 requires x86_64?
Date: Tue, 31 Jan 2006 18:56:00 -0800 [thread overview]
Message-ID: <43E02340.2020406@tlinx.org> (raw)
In-Reply-To: <1138712535.7088.5.camel@localhost.localdomain>
Steven Rostedt wrote:
> On Mon, 2006-01-30 at 19:31 -0800, Randy.Dunlap wrote:
>
>> Yes, there are bits in i386 that use x86_64 and there are
>> bits in x86_64 that use i386 code, so that the source code
>> won't have to be duplicated.
>>
> Perhaps we need an arch/x86_common that has this code. Not just to help
> those that like to delete other archs, but also to make it easier for us
> that might modify the code and know that this code is shared. It's
> better design to have a arch/x86_common that is compiled with i386 and
> x86_64 than to have code with - #include "../../x86_64/kernel/blah.c" -
> in it.
>
>
I'd tend to agree (unless it is a big problem).
It seems an unsound design principle to manually be
including code via direct references to a different architecture
tree.
Linda
next prev parent reply other threads:[~2006-02-01 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 3:10 i386 requires x86_64? L. A. Walsh
2006-01-31 3:31 ` Randy.Dunlap
2006-01-31 13:02 ` Steven Rostedt
2006-02-01 2:56 ` L. A. Walsh [this message]
2006-01-31 3:34 ` Nish Aravamudan
2006-01-31 8:54 ` Jesper Juhl
2006-01-31 13:17 ` Steven Rostedt
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=43E02340.2020406@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rostedt@goodmis.org \
/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.