From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Frederic Weisbecker <fweisbec@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH 0/5] [GIT PULL][v3.2] x86: Consolidate 32 and 64 bit thread_info
Date: Thu, 28 Jul 2011 21:42:15 -0400 [thread overview]
Message-ID: <20110729014215.328710900@goodmis.org> (raw)
Thomas, Ingo, and Peter(s),
On IRC, Peter Zijlstra mentioned to me the difference between
32bit and 64bit x86 on how thread_info is handled with interrupts.
I mentioned that they should be more the same, and Peter agreed.
I decided to do so, and ended up with the following patches.
I marked this for v3.2 as it should be tested a bit before going into
mainline. I've ran several configs on it, but more testing should be done.
Some of the patches are clean ups, but the main ones are patch 3 and 4
that do the work to convert 32bit of thread_info to be more like
the 64bit.
-- Steve
Please pull the latest tip/x86/thread_info tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/x86/thread_info
Head SHA1: a9db5af270460d73139d83e39d1dabc9c475a821
Steven Rostedt (5):
x86: Do not differentiate between x86_64 and i386 with init_per_cpu
x86: Nuke the supervisor_stack field in i386 thread_info
x86: Remove previous_esp from i386 thread_info structure
x86: Keep thread_info on thread stack in x86_32
x86: Clean up dumpstack_64.c code
----
arch/x86/include/asm/percpu.h | 4 +-
arch/x86/include/asm/processor.h | 9 +++
arch/x86/include/asm/thread_info.h | 56 +++--------------
arch/x86/kernel/cpu/common.c | 8 +-
arch/x86/kernel/dumpstack_32.c | 44 ++++++++++++-
arch/x86/kernel/dumpstack_64.c | 121 +++++++++++++++++++++++++-----------
arch/x86/kernel/irq_32.c | 86 +++++++++++---------------
arch/x86/kernel/process_32.c | 4 +
arch/x86/kernel/smpboot.c | 2 +-
9 files changed, 191 insertions(+), 143 deletions(-)
next reply other threads:[~2011-07-29 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 1:42 Steven Rostedt [this message]
2011-07-29 1:42 ` [PATCH 1/5] x86: Do not differentiate between x86_64 and i386 with init_per_cpu Steven Rostedt
2011-07-29 4:18 ` Brian Gerst
2011-07-29 11:41 ` Steven Rostedt
2011-07-29 1:42 ` [PATCH 2/5] x86: Nuke the supervisor_stack field in i386 thread_info Steven Rostedt
2011-07-29 1:42 ` [PATCH 3/5] x86: Remove previous_esp from i386 thread_info structure Steven Rostedt
2011-07-29 1:42 ` [PATCH 4/5] x86: Keep thread_info on thread stack in x86_32 Steven Rostedt
2011-07-29 1:42 ` [PATCH 5/5] x86: Clean up dumpstack_64.c code Steven Rostedt
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=20110729014215.328710900@goodmis.org \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox