All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Christoph Lameter <clameter@sgi.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	GOTO <y-goto@jp.fujitsu.com>
Subject: Re: Warning on memory offline (and possible in usual migration?)
Date: Wed, 30 Apr 2008 09:26:20 +0200	[thread overview]
Message-ID: <20080430072620.GI27652@wotan.suse.de> (raw)
In-Reply-To: <20080430001249.c07ff5c8.akpm@linux-foundation.org>

On Wed, Apr 30, 2008 at 12:12:49AM -0700, Andrew Morton wrote:
> On Wed, 30 Apr 2008 08:56:11 +0200 Nick Piggin <npiggin@suse.de> wrote:
> 
> > On Tue, Apr 29, 2008 at 04:20:16PM +0900, KAMEZAWA Hiroyuki wrote:
> > > I myself want to this patch to be included (to next -mm) and put this under
> > > test. How do you think ? Nick ? Christoph ?
> > 
> > I think it should go upstream, yes. I imagine Andrew is probably just busy
> > with merging at the moment. I guess we should resubmit if it isn't picked
> > up in the next few days.
> 
> Well I'm actually waiting for something which looks like a patch to fly
> past.  The last thing I saw was labelled "here is my proposed (uncompiled,
> untested) fix".

OK.. I don't have a good setup for testing page migration which is why
I didn't test it.

But it was since tested and found to solve the problem (or at least the
warning went away). Christoph, do you have a regression test suite or
something to run it through?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-04-30  7:26 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14  5:58 Warning on memory offline (and possible in usual migration?) KAMEZAWA Hiroyuki
2008-04-14 17:46 ` Christoph Lameter
2008-04-15 10:13   ` KAMEZAWA Hiroyuki
2008-04-15 19:31     ` Christoph Lameter
2008-04-16  0:23       ` KAMEZAWA Hiroyuki
2008-04-16  2:23         ` KAMEZAWA Hiroyuki
2008-04-16  3:10           ` KAMEZAWA Hiroyuki
2008-04-16  5:22             ` KAMEZAWA Hiroyuki
2008-04-16 18:04             ` Christoph Lameter
2008-04-16 11:00   ` KAMEZAWA Hiroyuki
2008-04-16 18:36     ` Andrew Morton
2008-04-17  0:19       ` KAMEZAWA Hiroyuki
2008-04-17  6:38         ` Warning on memory offline (possible in migration ?) KAMEZAWA Hiroyuki
2008-04-17  6:38           ` KAMEZAWA Hiroyuki
2008-04-17  6:43           ` Andrew Morton
2008-04-17  6:43             ` Andrew Morton
2008-04-17  6:55             ` KAMEZAWA Hiroyuki
2008-04-17  6:55               ` KAMEZAWA Hiroyuki
2008-04-22  4:41       ` Warning on memory offline (and possible in usual migration?) Nick Piggin
2008-04-22  4:52   ` Nick Piggin
2008-04-22  7:56     ` KAMEZAWA Hiroyuki
2008-04-22  9:43       ` Nick Piggin
2008-04-22  9:57         ` KAMEZAWA Hiroyuki
2008-04-22 19:16         ` Christoph Lameter
2008-04-23  0:48           ` Nick Piggin
2008-04-23  1:37             ` KAMEZAWA Hiroyuki
2008-04-23  2:41             ` KAMEZAWA Hiroyuki
2008-04-23  2:53               ` Nick Piggin
2008-04-23  3:44                 ` KAMEZAWA Hiroyuki
2008-04-23 15:28                   ` Nick Piggin
2008-04-24  1:34                     ` KAMEZAWA Hiroyuki
2008-04-23 17:50                   ` Christoph Lameter
2008-04-24  1:36                     ` KAMEZAWA Hiroyuki
2008-04-24 19:11                       ` Christoph Lameter
2008-04-25  0:11                         ` KAMEZAWA Hiroyuki
2008-04-23 17:47                 ` Christoph Lameter
2008-04-24  2:13                   ` Nick Piggin
2008-04-29  7:20             ` KAMEZAWA Hiroyuki
2008-04-30  6:56               ` Nick Piggin
2008-04-30  7:04                 ` KAMEZAWA Hiroyuki
2008-04-30  7:12                 ` Andrew Morton
2008-04-30  7:22                   ` KAMEZAWA Hiroyuki
2008-04-30  7:26                   ` Nick Piggin [this message]
2008-04-30 17:59                     ` Christoph Lameter
2008-04-30 18:01                     ` Christoph Lameter
2008-04-30 23:29                       ` kamezawa.hiroyu
2008-05-01  0:34                         ` Badari Pulavarty
2008-05-01  8:36                           ` kamezawa.hiroyu
2008-05-01  1:44                       ` Nick Piggin
2008-05-01 19:25                         ` Christoph Lameter
2008-05-02  0:44                           ` Nick Piggin
2008-05-02  1:07                             ` Christoph Lameter
2008-05-02  1:23                               ` Nick Piggin
2008-05-02  1:37                                 ` Christoph Lameter
2008-05-02 21:16                                   ` Christoph Lameter
2008-05-05  4:27                                     ` Nick Piggin
2008-05-05 17:28                                       ` Christoph Lameter
2008-05-06  8:52                                         ` Nick Piggin
2008-05-06 17:49                                           ` Christoph Lameter
2008-04-22  4:50 ` Nick Piggin

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=20080430072620.GI27652@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=y-goto@jp.fujitsu.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 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.