* arm_fadvise() man page
@ 2010-10-09 4:50 Michael Kerrisk
[not found] ` <AANLkTinQ7xBBa1VqR9oiLoh=7JCiR7BAeFceE3Cgc+TT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Michael Kerrisk @ 2010-10-09 4:50 UTC (permalink / raw)
To: Stephan Mueller; +Cc: linux-man-u79uwXL29TY76Z2rM5mHXA
[Was: man pages for undocumented system calls]
Stephan,
The situation here is similar to sync_file_range, but specific to ARM.
The documentation would better be in the posix_fadvise() page, should
explicitly note that this system call is for ARM only, and should note
why the system call exists. For man-pages-3.29, I applied the patch
below.
Thanks,
Michael
--- a/man2/posix_fadvise.2
+++ b/man2/posix_fadvise.2
@@ -148,6 +149,30 @@ call
or
.BR fdatasync (2)
first.
+.SS arm_fadvise()
+The ARM architecture
+needs 64-bit arguments to be aligned in a suitable pair of registers.
+On this architecture, the call signature of
+.BR posix_fadvise ()
+is flawed, since it forces a register to be wasted as padding between the
+.I fd
+and
+.I len
+arguments.
+Therefore, since Linux 2.6.14, ARM defines a different
+system call that orders the arguments suitably:
+.PP
+.in +4n
+.nf
+.BI "long arm_fadvise64_64(int " fd ", int " advice ,
+.BI " loff_t " offset ", loff_t " len );
+.fi
+.in
+.PP
+The behavior of this system call is otherwise exactly the same as
+.BR posix_fadvise().
+No library support is provided for this system call in glibc.
+.\" No ARM support in glibc.
.SH BUGS
In kernels before 2.6.6, if
.I len
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread[parent not found: <AANLkTinQ7xBBa1VqR9oiLoh=7JCiR7BAeFceE3Cgc+TT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: arm_fadvise() man page [not found] ` <AANLkTinQ7xBBa1VqR9oiLoh=7JCiR7BAeFceE3Cgc+TT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2010-10-09 12:40 ` Stephan Mueller [not found] ` <201010091440.12442.stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org> 0 siblings, 1 reply; 3+ messages in thread From: Stephan Mueller @ 2010-10-09 12:40 UTC (permalink / raw) To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w; +Cc: linux-man-u79uwXL29TY76Z2rM5mHXA Am Samstag, 9. Oktober 2010, um 06:50:29 schrieb Michael Kerrisk: Hi Michael, > [Was: man pages for undocumented system calls] > > Stephan, > > The situation here is similar to sync_file_range, but specific to ARM. > The documentation would better be in the posix_fadvise() page, should > explicitly note that this system call is for ARM only, and should note > why the system call exists. For man-pages-3.29, I applied the patch > below. Same here, I think your approach is better than a stand-alone man page. Nevertheless, are you going to please add a symlink from posix_fadvise.2.gz to arm_fadvise.2.gz? Thanks Stephan -- Stephan Müller Stephan.Mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org +49 172 216 55 78 atsec information security GmbH, Steinstraße 70, 81667 München, Germany Geschäftsführer: Salvatore la Pietra, Staffan Persson HRB: 129439 (Amtsgericht München) atsec it security news blog - atsec-information-security.blogspot.com -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <201010091440.12442.stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>]
* Re: arm_fadvise() man page [not found] ` <201010091440.12442.stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org> @ 2010-10-10 5:57 ` Michael Kerrisk 0 siblings, 0 replies; 3+ messages in thread From: Michael Kerrisk @ 2010-10-10 5:57 UTC (permalink / raw) To: Stephan Mueller; +Cc: linux-man-u79uwXL29TY76Z2rM5mHXA Hi Stephan, On Sat, Oct 9, 2010 at 2:40 PM, Stephan Mueller <stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org> wrote: > Am Samstag, 9. Oktober 2010, um 06:50:29 schrieb Michael Kerrisk: > > Hi Michael, > >> [Was: man pages for undocumented system calls] >> >> Stephan, >> >> The situation here is similar to sync_file_range, but specific to ARM. >> The documentation would better be in the posix_fadvise() page, should >> explicitly note that this system call is for ARM only, and should note >> why the system call exists. For man-pages-3.29, I applied the patch >> below. > > Same here, I think your approach is better than a stand-alone man page. > > Nevertheless, are you going to please add a symlink from posix_fadvise.2.gz to > arm_fadvise.2.gz? Thanks for reminding me of this, but in fact I already made such a link. I added a link arm_fadvise64_64.2, since that is the precise name of the system call. But, on reflection, perhaps it does not hurt to also add a link arm_fadvise.2, so I've also added that one now. Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Author of "The Linux Programming Interface"; http://man7.org/tlpi/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-10-10 5:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-09 4:50 arm_fadvise() man page Michael Kerrisk
[not found] ` <AANLkTinQ7xBBa1VqR9oiLoh=7JCiR7BAeFceE3Cgc+TT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-09 12:40 ` Stephan Mueller
[not found] ` <201010091440.12442.stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
2010-10-10 5:57 ` Michael Kerrisk
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox