All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <ak@suse.de>, Christoph Lameter <clameter@sgi.com>,
	Jack Steiner <steiner@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] x86: Convert cpuinfo_x86 array to a per_cpu array v3
Date: Fri, 03 Aug 2007 18:15:55 -0700	[thread overview]
Message-ID: <46B3D34B.6010105@sgi.com> (raw)
In-Reply-To: <20071016011827.91350174.akpm@linux-foundation.org>

Andrew Morton wrote:
...
>> ...  This patch deals with the cpu_data array of
>> cpuinfo_x86 structs.  The model that was used in sparc64
>> architecture was adopted for x86.
>>
> 
> This has mysteriously started to oops on me, only on x86_64.
> 
> http://userweb.kernel.org/~akpm/config-x.txt
> http://userweb.kernel.org/~akpm/dsc00001.jpg
> 
> which is a bit strange since this patch doesn't touch sched.c.  Maybe
> there's something somewhere else in the -mm lineup which when combined with
> this prevents it from oopsing, dunno.  I'll hold it back for now and will
> see what happens.
> 

I'll take a look at this right away.

Thanks,
Mike


WARNING: multiple messages have this Message-ID (diff)
From: Mike Travis <travis@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <ak@suse.de>, Christoph Lameter <clameter@sgi.com>,
	Jack Steiner <steiner@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] x86: Convert cpuinfo_x86 array to a per_cpu array v3
Date: Fri, 03 Aug 2007 18:15:55 -0700	[thread overview]
Message-ID: <46B3D34B.6010105@sgi.com> (raw)
In-Reply-To: <20071016011827.91350174.akpm@linux-foundation.org>

Andrew Morton wrote:
...
>> ...  This patch deals with the cpu_data array of
>> cpuinfo_x86 structs.  The model that was used in sparc64
>> architecture was adopted for x86.
>>
> 
> This has mysteriously started to oops on me, only on x86_64.
> 
> http://userweb.kernel.org/~akpm/config-x.txt
> http://userweb.kernel.org/~akpm/dsc00001.jpg
> 
> which is a bit strange since this patch doesn't touch sched.c.  Maybe
> there's something somewhere else in the -mm lineup which when combined with
> this prevents it from oopsing, dunno.  I'll hold it back for now and will
> see what happens.
> 

I'll take a look at this right away.

Thanks,
Mike

--
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>

  reply	other threads:[~2007-10-17 16:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 21:08 [PATCH 0/1] x86: Convert cpuinfo_x86 array to a per_cpu array v3 travis
2007-09-24 21:08 ` travis
2007-09-24 21:08 ` [PATCH 1/1] " travis
2007-09-24 21:08   ` travis
2007-09-24 22:01   ` roel
2007-09-24 22:01     ` roel
2007-09-24 23:24     ` Dave Jones
2007-09-24 23:24       ` Dave Jones
2007-09-25  0:20       ` roel
2007-09-25  0:20         ` roel
2007-09-25  0:31         ` Dave Jones
2007-09-25  0:31           ` Dave Jones
2007-10-16  8:18 ` [PATCH 0/1] " Andrew Morton
2007-10-16  8:18   ` Andrew Morton
2007-08-04  1:15   ` Mike Travis [this message]
2007-08-04  1:15     ` Mike Travis
2007-10-16 15:02   ` Christoph Lameter
2007-10-16 15:02     ` Christoph Lameter

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=46B3D34B.6010105@sgi.com \
    --to=travis@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=steiner@sgi.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.