From: Steven Rostedt <rostedt@goodmis.org>
To: Brian Gerst <brgerst@gmail.com>
Cc: linux-kernel@vger.kernel.org, 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: Re: [PATCH 1/5] x86: Do not differentiate between x86_64 and i386 with init_per_cpu
Date: Fri, 29 Jul 2011 07:41:56 -0400 [thread overview]
Message-ID: <1311939716.21143.24.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <CAMzpN2jAKphUcp2eFfyVtn+ut+=oRqr40G3tTbDMziEg+TEuhw@mail.gmail.com>
On Fri, 2011-07-29 at 00:18 -0400, Brian Gerst wrote:
> Even though 32-bit doesn't currently use these macros, please keep the
> current define, since only 64-bit SMP is special in this regard.
> 64-bit SMP uses a zero-based percpu segment, which requires the linker
> fixup for statically initialized percpu pointers. This fixup isn't
> needed on 32-bit SMP (or UP).
OK, fine, I'll remove this patch from the set and rebase.
Thanks,
-- Steve
next prev parent reply other threads:[~2011-07-29 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 1:42 [PATCH 0/5] [GIT PULL][v3.2] x86: Consolidate 32 and 64 bit thread_info Steven Rostedt
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 [this message]
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=1311939716.21143.24.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=brgerst@gmail.com \
--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
all inboxes | Powered by JetHome®