From: Linus Torvalds <torvalds@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: [x86] Unify semaphore_32.S and rwlock_64.S
Date: Wed, 20 Jan 2010 15:46:16 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001201542000.13231@localhost.localdomain> (raw)
In-Reply-To: <4B57641E.5060303@zytor.com>
On Wed, 20 Jan 2010, H. Peter Anvin wrote:
>
> The motivation for rwsem_count_t seemed to be making it easier to switch
> over. I leave it up to Linus to motivate the typedef...
Indeed. I wanted to separate the issue of cleaning up the mask values from
cleaning up the code. That required that we'd have a separate type that
can change in _one_ place with the bias values.
It was also an unholy type mess before, so the rwsem_count_t also was
about making that unholy mess clearer. That's especially true since the
type will also have to percolate down to the slow cases before you can
actually fix the BIAS values.
As to keeping the 64-bit and 32-bit slow case wrappers separate: this is
very much one case where we _have_ to. Trying to pretend that 32-bit code
and 64-bit code is similar in this case is just lying. The calling
conventions are totally different, there is nothing similar there at all
(different argument registers, different clobbered registers, different
_everything_ that matters for the wrapper).
Linus
prev parent reply other threads:[~2010-01-20 23:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 22:21 Christoph Lameter
2010-01-19 22:30 ` H. Peter Anvin
2010-01-20 19:49 ` Christoph Lameter
2010-01-20 20:14 ` H. Peter Anvin
2010-01-20 20:51 ` Christoph Lameter
2010-01-20 23:57 ` Linus Torvalds
2010-01-21 0:02 ` H. Peter Anvin
2010-01-21 6:28 ` H. Peter Anvin
2010-01-21 0:46 ` Linus Torvalds
2010-01-21 0:55 ` H. Peter Anvin
2010-01-20 23:46 ` Linus Torvalds [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=alpine.LFD.2.00.1001201542000.13231@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®