All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Lameter <clameter@sgi.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@suse.de>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
Date: Fri, 30 Nov 2007 21:43:55 +0100	[thread overview]
Message-ID: <20071130204355.GA31865@elte.hu> (raw)
In-Reply-To: <20071130202622.GA15006@elte.hu>


btw., this is the list of patches i've picked up for testing:

modules-include-sectionsh-to-avoid-defining-linker-variables.patch
modules-handle-symbols-that-have-a-zero-value.patch
modules-fold-percpu_modcopy-into-modulec-and-get-rid-of-the-macro-from-hell.patch

percpu1-percpu-use-a-kconfig-variable-to-signal-arch-specific-percpu-setup.patch
percpu1-percpu-move-arch-xx-per-cpu-xx-definitions-into-linux-percpu-h.patch
percpu1-percpu-make-the-asm-generic-percpu-h-more-generic-.patch
percpu1-x86-32-use-generic-percpu-h.patch
percpu1-x86-64-use-generic-percpu.patch
percpu1-s390-use-generic-percpu.patch
percpu1-powerpc-use-generic-per-cpu.patch
percpu1-sparc64-use-generic-percpu.patch
percpu1-ia64-use-generic-percpu.patch
percpu1-x86-unify-percpu-h.patch

percpu2-percpu-infrastructure-to-rebase-the-per-cpu-area-to-0ul.patch
percpu2-x86-64-declare-pda-as-per-cpu-data-thereby-moving-it-into-the-cpu-area.patch
percpu2-x86-64-make-the-x86-32-percpu-operations-usable-on-x86-64.patch

the first 3 are from -mm, the rest from lkml. This series applied 
cleanly without any rejects but i still got the spontaneous reboot 
during bootup on UP 32-bit x86.

So either i'm still missing some essential patch, or this tree somehow 
triggers the problem more likely than in -mm. I've bisected it down to:

 percpu1-percpu-move-arch-xx-per-cpu-xx-definitions-into-linux-percpu-h.patch

that patch looks harmless though. Anyway, we can certainly revisit this 
issue after you get back on Dec 13th.

	Ingo

  reply	other threads:[~2007-11-30 20:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30  6:43 [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64 Christoph Lameter
2007-11-30  6:43 ` [patch 1/3] Percpu infrastructure to rebase the per cpu area to 0UL Christoph Lameter
2007-12-02  3:04   ` Rusty Russell
2007-12-02  3:13   ` Rusty Russell
2007-11-30  6:43 ` [patch 2/3] X86_64: Declare pda as per cpu data thereby moving it into the cpu area Christoph Lameter
2007-11-30  6:43 ` [patch 3/3] x86_64: Make the x86_32 percpu operations usable on x86_64 Christoph Lameter
2007-11-30 20:07   ` Christoph Lameter
2007-11-30 11:24 ` [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops " Ingo Molnar
2007-11-30 11:26   ` Ingo Molnar
2007-11-30 17:08     ` Christoph Lameter
2007-11-30 17:19     ` Christoph Lameter
2007-11-30 18:00       ` Ingo Molnar
2007-11-30 18:24         ` Christoph Lameter
2007-11-30 18:35           ` Ingo Molnar
2007-11-30 18:47             ` Christoph Lameter
2007-11-30 19:45               ` Ingo Molnar
2007-11-30 19:59                 ` Christoph Lameter
2007-11-30 20:06                   ` Ingo Molnar
2007-11-30 20:09                     ` Christoph Lameter
2007-11-30 20:26                   ` Ingo Molnar
2007-11-30 20:43                     ` Ingo Molnar [this message]
2007-11-30 18:41           ` Ingo Molnar
2007-11-30 18:43             ` 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=20071130204355.GA31865@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    /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.