Re: [PATCH 00/18] Make common x86 arch area for i386 and x86_64 - Take 2

On Thu, 2007-03-15 at 12:47 -0400, Steven Rostedt wrote:
On Thu, 2007-03-15 at 17:06 +0100, Andi Kleen wrote:

Well I just see a lot of pain from these patches but I doubt
they will avoid any bugs. If people don't compile test both
archs they will always likely break on another. There are lots
of subtle dependencies that are not expressed in the pathname
even after this intrusive operation (e.g. in the includes).

[...]

With the proposed patch set, what can break i386 by modifying something
in arch/x86_64, or what can break x86_64 by modifying something in
arch/i386? (not counting the unfinished pci shared code).

Oops, sorry, you did say "in the includes". Yeah, that holds the same
crap that I'm talking about.

$ cat include/asm-i386/stacktrace.h
#include <asm-x86_64/stacktrace.h>

Which isn't something that I would like to stay either. So it's just
something else that needs to be fixed. Not something that will
circumvent what the current patch set is trying to do.

-- Steve


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [RFC] VM: I have a dream...
    ... You have to remember that change introduces bugs which then have to be located and removed again, so change is not necessarily cheap. ... Other reasons are that sometimes you really _do_ want a nonlinear mapping of data/files/libs/etc. ... Please provide technical points and reasons why it _is_ indead shorter/better/faster, and then you can still leave out the analogy because the technical argument is sufficient. ... Even if there were 64bit archs available in the past, this did not mean that moving into native 64bits would be commercially viable, due to its unavailability on the mass-market. ...
    (Linux-Kernel)
  • Re: [PATCH 00/18] Make common x86 arch area for i386 and x86_64 - Take 2
    ... If people don't compile test both ... archs they will always likely break on another. ... memmap support may require a large chunk of virtual memory space that is ...
    (Linux-Kernel)