From: "David S. Miller" <davem@davemloft.net>
To: hpa@zytor.com
Cc: bcrl@kvack.org, klibc@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: sys_mmap2 on different architectures
Date: Wed, 22 Feb 2006 17:03:44 -0800 (PST) [thread overview]
Message-ID: <20060222.170344.84235860.davem@davemloft.net> (raw)
In-Reply-To: <43FD08D8.70300@zytor.com>
From: "H. Peter Anvin" <hpa@zytor.com>
Date: Wed, 22 Feb 2006 16:59:04 -0800
> On the other hand, sys32_mmap2 on SPARC64 matches the SPARC32 sys_mmap2
> in that the shift is hard-coded to 12:
>
> .globl sys32_mmap2
> sys32_mmap2:
> sethi %hi(sys_mmap), %g1
> jmpl %g1 + %lo(sys_mmap), %g0
> sllx %o5, 12, %o5
Another good catch...
> At this point, I'm more than willing to treat SPARC as a special case,
> but I really want to know what the rules actually _ARE_ as opposed to
> what they are supposed to be (which they clearly are not.)
I have to admit I'm totally stumped...
Why are you invoking mmap2() instead of mmap64() btw?
next prev parent reply other threads:[~2006-02-23 1:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 21:45 sys_mmap2 on different architectures H. Peter Anvin
2006-02-22 21:54 ` David S. Miller
2006-02-22 22:00 ` H. Peter Anvin
2006-02-23 0:05 ` H. Peter Anvin
2006-02-23 0:40 ` David S. Miller
2006-02-23 0:41 ` David S. Miller
2006-02-23 0:14 ` Benjamin LaHaise
2006-02-23 0:22 ` H. Peter Anvin
2006-02-23 0:43 ` David S. Miller
2006-02-23 0:59 ` H. Peter Anvin
2006-02-23 1:03 ` David S. Miller [this message]
2006-02-23 1:06 ` H. Peter Anvin
2006-02-23 17:39 ` Benjamin LaHaise
2006-02-23 17:47 ` H. Peter Anvin
2006-02-23 2:56 ` Paul Mackerras
2006-02-23 3:35 ` H. Peter Anvin
2006-02-23 17:32 ` Ralf Baechle
2006-02-23 17:43 ` H. Peter Anvin
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=20060222.170344.84235860.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bcrl@kvack.org \
--cc=hpa@zytor.com \
--cc=klibc@zytor.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).