All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fake NUMA emulation for PowerPC
Date: Fri, 7 Dec 2007 15:28:17 -0600	[thread overview]
Message-ID: <20071207212817.GA391@lixom.net> (raw)
In-Reply-To: <20071207211425.10223.91240.sendpatchset@balbir-laptop>

Hi,

On Sat, Dec 08, 2007 at 02:44:25AM +0530, Balbir Singh wrote:

> Comments are as always welcome!

Care to explain what this is useful for? (Not saying it's a stupid idea,
just wondering what the reason for doing it is).

> diff -puN arch/powerpc/mm/numa.c~ppc-fake-numa-easy arch/powerpc/mm/numa.c
> --- linux-2.6.24-rc4-mm1/arch/powerpc/mm/numa.c~ppc-fake-numa-easy	2007-12-07 21:25:55.000000000 +0530
> +++ linux-2.6.24-rc4-mm1-balbir/arch/powerpc/mm/numa.c	2007-12-08 02:36:02.000000000 +0530
> @@ -24,6 +24,8 @@
>  
>  static int numa_enabled = 1;
>  
> +char *cmdline __initdata;
> +

Looks like this should be static.

> @@ -702,6 +744,9 @@ static int __init early_numa(char *p)
>  	if (strstr(p, "debug"))
>  		numa_debug = 1;
>  
> +	if (strstr(p, "fake="))
> +		cmdline = p + 5;	/* 5 is faster than strlen("fake=") */

This doesn't look right.

You check if it contains fake=, not if it starts with it. So if someone
did: "numa=foo,fake=bar", or even "numa=debug,fake=", things wouldn't
work right.


-Olof

  reply	other threads:[~2007-12-07 21:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 21:14 [PATCH] Fake NUMA emulation for PowerPC Balbir Singh
2007-12-07 21:14 ` Balbir Singh
2007-12-07 21:28 ` Olof Johansson [this message]
2007-12-07 21:35   ` Balbir Singh
2007-12-07 21:55     ` Kumar Gala
2007-12-07 22:12       ` Balbir Singh
2007-12-07 22:15         ` Kumar Gala
2007-12-07 22:18           ` Balbir Singh
2007-12-07 23:10         ` David Rientjes
2007-12-07 23:10           ` David Rientjes
2007-12-08  4:22           ` Balbir Singh
2007-12-08  4:22             ` Balbir Singh
2007-12-09 13:16             ` Pavel Machek
2007-12-09 13:16               ` Pavel Machek
2007-12-09 13:20               ` Balbir Singh
2007-12-09 13:20                 ` Balbir Singh
2007-12-07 23:06   ` David Rientjes
2007-12-07 23:06     ` David Rientjes
2007-12-07 21:30 ` Geert Uytterhoeven
2007-12-07 21:33   ` Dave Quigley
2007-12-07 21:35   ` Balbir Singh
2007-12-07 21:43     ` Balbir Singh
2007-12-07 21:58       ` Arnd Bergmann
2007-12-07 21:58         ` Arnd Bergmann
2007-12-07 22:03         ` Balbir Singh
2007-12-07 22:03           ` Balbir Singh
2007-12-07 22:01 ` Arnd Bergmann
2007-12-07 22:01   ` Arnd Bergmann
2007-12-07 22:22   ` Balbir Singh
2007-12-07 22:11 ` Nathan Lynch
2007-12-07 22:26   ` Balbir Singh
2007-12-07 23:11     ` David Rientjes
2007-12-07 23:11       ` David Rientjes
2007-12-08  4:32       ` Balbir Singh
2007-12-08  4:45         ` David Rientjes

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=20071207212817.GA391@lixom.net \
    --to=olof@lixom.net \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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.