From: Arnd Bergmann <arnd@arndb.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add FUTEX_CMP_REQUEUE futex op
Date: Thu, 10 Jun 2004 00:08:20 +0200 [thread overview]
Message-ID: <200406100008.20692.arnd@arndb.de> (raw)
In-Reply-To: <20040609130406.7942507c@lembas.zaitcev.lan>
On Wednesday 09 June 2004 22:04, Pete Zaitcev wrote:
> Is it just me, or this could he above stand a use of STACK_FRAME_OVERHEAD
> instead of 160? I envision a time when Ulrich Weigand comes out with
> a gcc -fkernel, and at that time we'll need all such references
> configurable.
It wouldn't hurt, but even if we get -mkernel support in gcc, that doesn't
mean that the stack frame size has to change: You can easily have %r15
point to 160 bytes above the register save area without actually using all
that space for saving registers. The only thing that would need to change is
the location of the backchain pointer.
> Why not to place the necessary word outside of the struct?
> It just logically doesn't belong. Might be just as easy to
> do that mvc to other place.
That actually was what Martin tried in his first implementation (well, the
last one before the one he submitted). It didn't work out because some code
relied on the stack starting right after pt_regs. Martin can probably clarify
that on Friday.
Arnd <><
next prev parent reply other threads:[~2004-06-09 21:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1086629984.12568.linux-kernel2news@redhat.com>
2004-06-09 20:04 ` [PATCH] Add FUTEX_CMP_REQUEUE futex op Pete Zaitcev
2004-06-09 22:08 ` Arnd Bergmann [this message]
2004-06-11 8:35 ` Martin Schwidefsky
2004-06-07 16:03 Martin Schwidefsky
-- strict thread matches above, loose matches on Subject: below --
2004-05-20 9:38 Jakub Jelinek
2004-05-20 22:52 ` Andrew Morton
2004-05-21 6:06 ` Ulrich Drepper
2004-05-21 6:36 ` Andrew Morton
2004-05-21 7:15 ` Ulrich Drepper
2004-05-21 7:43 ` Jakub Jelinek
2004-05-22 16:58 ` Arnd Bergmann
2004-05-24 7:34 ` Jakub Jelinek
2004-05-24 8:12 ` Andrew Morton
2004-05-24 8:19 ` Jakub Jelinek
2004-05-24 8:27 ` bert hubert
2004-05-24 17:34 ` Arnd Bergmann
2004-05-21 7:05 ` Ingo Molnar
2004-05-21 23:05 ` Andrew Morton
2004-05-22 10:10 ` Ingo Oeser
2004-05-23 17:33 ` Jakub Jelinek
2004-05-29 3:13 ` Rusty Russell
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=200406100008.20692.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=zaitcev@redhat.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