From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Chris Wright <chrisw@sous-sol.org>,
Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@muc.de>,
Glauber de Oliveira Costa <glommer@gmail.com>
Subject: Re: [RFC/PATCH 00/59] Make common x86 arch area for i386 and x86_64
Date: Wed, 14 Mar 2007 13:49:07 +0100 [thread overview]
Message-ID: <20070314124906.GA11966@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0703131432400.9690@woody.linux-foundation.org>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> We've started to notice that the i386 build gets broken now that most
> developers tend to have newer CPU's and run mostly on x86-64 (and yes,
> that's me too), and while I don't think unifying things will guarantee
> that doesn't happen in the future, it will hopefully at least help
> make it not get much *worse*.
actually, even for 'cutting edge' testers, the number of 32-bit x86
systems outnumber the number of 64-bit test-systems by a factor of 5.
For distributions with real users, the ratio is closer to 1:10...
so i typically get bugs reported on 32-bit first, and for 64-bit it is
usually only reported if the bug is 64-bit /only/. That basic property
is true for both upstream, -rt and rawhide kernels.
Andi's x86 merge tree /does/ break quite often on 32-bit, but that's not
really due to testers, that's due to Andi being primarily the 64-bit
maintainer ;)
Ingo
next prev parent reply other threads:[~2007-03-14 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1173820919.28042.3.camel@localhost.localdomain>
2007-03-13 21:39 ` Linus Torvalds
2007-03-14 1:02 ` Steven Rostedt
2007-03-14 10:12 ` Andi Kleen
2007-03-14 22:05 ` Rusty Russell
2007-03-14 12:49 ` Ingo Molnar [this message]
2007-03-13 21:45 ` Chris Wright
2007-03-14 1:05 ` 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=20070314124906.GA11966@elte.hu \
--to=mingo@elte.hu \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®