From: Christoph Lameter <clameter@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: travis@sgi.com, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: x86: Unify current.h
Date: Tue, 6 May 2008 11:00:34 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0805061059170.23336@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080506125128.GA5051@elte.hu>
On Tue, 6 May 2008, Ingo Molnar wrote:
> i suspect the __ASSEMBLY__ protections in the unified file are not wide
> enough?
Duh. yes. The x86_64 __ASSEMBLY__ protection is no longer there. We could
move the task_struct def back into the arch specific portion. Sigh.
---
include/asm-x86/current.h | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
Index: linux-2.6/include/asm-x86/current.h
===================================================================
--- linux-2.6.orig/include/asm-x86/current.h 2008-05-06 10:58:03.000000000 -0700
+++ linux-2.6/include/asm-x86/current.h 2008-05-06 10:58:40.000000000 -0700
@@ -1,12 +1,12 @@
#ifndef _X86_CURRENT_H
#define _X86_CURRENT_H
-struct task_struct;
-
#ifdef CONFIG_X86_32
#include <linux/compiler.h>
#include <asm/percpu.h>
+struct task_struct;
+
DECLARE_PER_CPU(struct task_struct *, current_task);
static __always_inline struct task_struct *get_current(void)
{
@@ -18,6 +18,8 @@ static __always_inline struct task_struc
#ifndef __ASSEMBLY__
#include <asm/pda.h>
+struct task_struct;
+
static __always_inline struct task_struct *get_current(void)
{
return read_pda(pcurrent);
prev parent reply other threads:[~2008-05-06 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 18:48 Christoph Lameter
2008-05-06 12:28 ` Ingo Molnar
2008-05-06 12:51 ` Ingo Molnar
2008-05-06 18:00 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0805061059170.23336@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=travis@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 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®