public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-arch@vger.kernel.org, Dave Hansen <haveblue@us.ibm.com>,
	Matt Tolentino <matthew.e.tolentino@intel.com>,
	Bob Picco <bob.picco@hp.com>
Subject: Re: sparsemem patches in -mm
Date: Tue, 21 Jun 2005 16:49:11 +0100	[thread overview]
Message-ID: <42B836F7.7060106@shadowen.org> (raw)
In-Reply-To: <20050621095039.GC4171@wotan.suse.de>

Andi Kleen wrote:
> On Tue, Jun 21, 2005 at 02:13:52AM -0700, Andrew Morton wrote:
> 
>>Could I ask the arch maintainers to review the `sparsemem' patches from -mm,
>>please, if you haven't done so...
> 
> 
> The x86-64 part is ok for me from a review standpoint.
> 
> However how much testing has been done on these yet? 
> It would be good to at least boot it on EM64T and AMD 

I've been testing this on a range of test boxes we have here, mostly x86
and ppc.  Mostly with kernbench and the like.  So far no problems have
reared their heads.

I've not been able to get much or a realistic test on amd64 box, I seem
to be struggling with combinations of scsi problems on the machine from
other changes in -mm.   The good news is that it gets far enough to
break with scsi problems and problems in sparsemem generally lead to
death much earlier than this.

-apw

  parent reply	other threads:[~2005-06-21 15:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21  9:13 sparsemem patches in -mm Andrew Morton
2005-06-21  9:50 ` Andi Kleen
2005-06-21 10:09   ` Andrew Morton
2005-06-21 15:49   ` Andy Whitcroft [this message]
2005-06-21 15:58     ` Andi Kleen
2005-06-21 11:00 ` Bob Picco
2005-06-21 15:57   ` Dave Hansen
2005-06-21 16:45     ` Bob Picco
2005-06-21 14:17 ` Matthew Wilcox
2005-06-21 15:51   ` Andy Whitcroft
2005-06-21 20:01     ` Andrew Morton
2005-06-21 23:39       ` Dave Hansen
2005-06-22  5:46 ` David S. Miller
2005-06-22  6:00   ` Andrew Morton
2005-07-27 22:42     ` David S. Miller
2005-06-23 22:48 ` Roman Zippel
2005-06-23 22:56   ` Dave Hansen
2005-06-23 23:53     ` Roman Zippel
  -- strict thread matches above, loose matches on Subject: below --
2005-06-21 15:52 Luck, Tony
2005-06-21 15:58 ` Andy Whitcroft
2005-06-21 16:09 Luck, Tony
2005-06-21 16:17 ` Dave Hansen

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=42B836F7.7060106@shadowen.org \
    --to=apw@shadowen.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=bob.picco@hp.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=matthew.e.tolentino@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