From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Header dependencies
Date: Thu, 31 Oct 2002 17:46:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805317@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805316@msgid-missing>
>>>>> On Thu, 31 Oct 2002 16:48:35 +0000, Matthew Wilcox <willy@debian.org> said:
Matthew> I think the basic problem is that thread_info and
Matthew> task_struct are the wrong way round on the stack. If we
Matthew> put thread_info first then we don't need IA64_TASK_SIZE in
Matthew> current_thread_info's definition. What would people think
Matthew> to this rearrangement? I guess some asm code might need to
Matthew> be changed, and I'm still scared of ia64 assembler ;-)
I think I tried that back when the thread_info ugliness was
introduced. Making it work would require more changes to the platform
independent portions of the kernel (which may well be the right thing
to do). But my memory may be wrong---if you can make it work, I'd be
OK with the change.
--david
prev parent reply other threads:[~2002-10-31 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 16:48 [Linux-ia64] Header dependencies Matthew Wilcox
2002-10-31 17:46 ` David Mosberger [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=marc-linux-ia64-105590709805317@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox