All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Christoph Lameter <cl@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/5] percpu: Optimize percpu accesses
Date: Wed, 02 Jul 2008 07:04:03 -0700	[thread overview]
Message-ID: <486B8AD3.70007@sgi.com> (raw)
In-Reply-To: <486A483B.2090804@sgi.com>

Mike Travis wrote:
> Ingo Molnar wrote:
>> * Ingo Molnar <mingo@elte.hu> wrote:
>>
>>>> This patchset provides the following:
>>>>
>>>>   * Cleanup: Fix early references to cpumask_of_cpu(0)
>>>>   * Generic: Percpu infrastructure to rebase the per cpu area to zero
>>>>   * x86_64: Fold pda into per cpu area
>>>>   * x86_64: Rebase per cpu variables to zero
>>> thanks Mike - i've started testing it in -tip. One small merge fallout 
>>> fix is below. (it's for the new generic-ipi topic that was not in 
>>> tip/master yet when you merged percpu-zerobased to it)
>> ok, -tip testing found an early boot crash caused by your patchset, on 
>> 64-bit x86:

Hi Ingo,

Which gcc version are you using?

Thanks,
Mike

>>
>> [    0.396000] calling  net_ns_init+0x0/0x143
>> [    0.400000] net_namespace: 944 bytes
>> [    0.403578] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
>> [    0.404000] IP: [<ffffffff80e05b0e>] net_ns_init+0x9f/0x143
>> [    0.404000] PGD 0
>> [    0.404000] Oops: 0000 [1] SMP
>> [    0.404000] CPU 0
>> [...]
>>
>> full bootlog and config can be found at:
>>
>>   http://redhat.com/~mingo/misc/crashlog-Tue_Jul__1_16_48_45_CEST_2008.bad
>>   http://redhat.com/~mingo/misc/config-Tue_Jul__1_16_48_45_CEST_2008.bad
>>
>> (another 64-bit testbox crashed as well, so this should be readily 
>> reproducible.)
>>
>> i've pushed this tree out to tip/tmp.core/percpu-zerobased.Jul__1_16_48 
>> topic branch, that is the 2.6.26-rc8-tip-00250-g90874b0 kernel you can 
>> see in the crashlog.
>>
>> 	Ingo
> 
> Wow, that was quick!
> 
> At least this one gets to someplace debuggable.  Some others that don't
> even get to the first "kernel alive" messages are really annoying.  ;-)
> 
> Thanks,
> Mike


  reply	other threads:[~2008-07-02 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 12:16 [RFC 0/5] percpu: Optimize percpu accesses Mike Travis
2008-07-01 12:16 ` [RFC 1/5] x86_64: Fix early references to cpumask_of_cpu Mike Travis
2008-07-01 12:16 ` [RFC 2/5] x86_64: Fold pda into per cpu area Mike Travis
2008-07-01 12:16 ` [RFC 3/5] x86_64: Reference zero-based percpu variables offset from gs Mike Travis
2008-07-01 12:16 ` [RFC 4/5] x86_64: Replace cpu_pda ops with percpu ops Mike Travis
2008-07-01 12:16 ` [RFC 5/5] x86_64: Replace xxx_pda() operations with x86_xxx_percpu() Mike Travis
2008-07-01 14:54 ` [RFC 0/5] percpu: Optimize percpu accesses Ingo Molnar
2008-07-01 15:03   ` Ingo Molnar
2008-07-01 15:07     ` Mike Travis
2008-07-02 14:04       ` Mike Travis [this message]
2008-07-18  6:52         ` Ingo Molnar
2008-07-01 18:47     ` Mike Travis

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=486B8AD3.70007@sgi.com \
    --to=travis@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.