From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Header dependencies
Date: Thu, 31 Oct 2002 16:48:35 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805316@msgid-missing> (raw)
I took a look at converting to the asm-offsets.c method for generating
offsets.h that the other architectures are using. Basically, I ran
into the same problem Keith Owens alluded to earlier with the circular
dependencies:
asm/thread-info.h declares:
#define current_thread_info() ((struct thread_info *) ((char *) current + IA64_TASK_SIZE))
To get IA64_TASK_SIZE, it includes asm/offsets.h
To build asm/offsets.h, we need include linux/sched.h which includes
linux/thread_info.h which includes asm/thread_info.h.
I think the basic problem is that thread_info and task_struct are the
wrong way round on the stack. If we put thread_info first then we don't
need IA64_TASK_SIZE in current_thread_info's definition. What would
people think to this rearrangement? I guess some asm code might need
to be changed, and I'm still scared of ia64 assembler ;-)
--
Revolutions do not require corporate support.
next reply other threads:[~2002-10-31 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 16:48 Matthew Wilcox [this message]
2002-10-31 17:46 ` [Linux-ia64] Header dependencies David Mosberger
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=marc-linux-ia64-105590709805316@msgid-missing \
--to=willy@debian.org \
--cc=linux-ia64@vger.kernel.org \
/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.