From: Paul Mackerras <paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Stephan Mueller
<stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: subpage_prot() man page
Date: Wed, 27 Oct 2010 10:01:44 +1100 [thread overview]
Message-ID: <20101026230144.GA30272@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <AANLkTi=GZ5hxhbG7Frak-Hb+PC8=4uXcnBEgpcbCrmPG-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sun, Oct 10, 2010 at 07:53:35AM +0200, Michael Kerrisk wrote:
> Paul, would you be willing to review this page for the system call
> that you added?
Thanks for doing this. It looks fine, with just a couple of small
comments:
> .SH RETURN VALUE
> On success,
> .BR subpage_prot ()
> returns 0.
> Otherwise, one of the negated error codes specified below is returned.
Actually, by the time it gets back out to userland, it follows the
usual convention for error codes on PowerPC: for an error, the
positive error code is returned (in r3) with the CR0.SO bit (bit 3 in
the condition code register) set to indicate error. CR0.S0 is cleared
if there is no error.
So I would just remove the word "negated".
> .\" Perhaps we don't need to document this implementation detail:
> .\"
> .\" Implicit in this is that the regions of the address space that are
> .\" protected are switched to use 4k hardware pages rather than 64k
> .\" hardware pages (on machines with hardware 64k page support).
> .\" In fact the whole process is switched to use 4k hardware pages when the
> .\" subpage_prot system call is used, but this could be improved in future
> .\" to switch only the affected segments.
I'm pretty sure we now only switch the affected segment, not the whole
process.
Paul.
--
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
next prev parent reply other threads:[~2010-10-26 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 5:53 subpage_prot() man page Michael Kerrisk
[not found] ` <AANLkTi=GZ5hxhbG7Frak-Hb+PC8=4uXcnBEgpcbCrmPG-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-24 14:54 ` Michael Kerrisk
2010-10-26 23:01 ` Paul Mackerras [this message]
[not found] ` <20101026230144.GA30272-oklZEfemRj05kJ7NmlRacFaTQe2KTcn/@public.gmane.org>
2010-10-30 5:17 ` Michael Kerrisk
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=20101026230144.GA30272@brick.ozlabs.ibm.com \
--to=paulus-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.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