From: Heiko Carstens <heiko.carstens-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Martin Schwidefsky
<schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
QingFeng Hao
<haoqf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
Jan Glauber
<jang-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
Alexey Ishchuk
<aishchuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: Re: [man-pages PATCH 5/5] man2: describe s390_guarded_storage s390-specific system call
Date: Sat, 20 Jan 2018 13:23:49 +0100 [thread overview]
Message-ID: <20180120122349.GE6287@osiris> (raw)
In-Reply-To: <20180114185643.GA23919-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
On Sun, Jan 14, 2018 at 07:56:43PM +0100, Eugene Syromyatnikov wrote:
> ---
> man2/s390_guarded_storage.2 | 150 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 150 insertions(+)
> create mode 100644 man2/s390_guarded_storage.2
>
> diff --git a/man2/s390_guarded_storage.2 b/man2/s390_guarded_storage.2
> +.B GS_ENABLE
> +Enable the guarded storage facility for the current task.
> +The initial content of the guarded storage control block will be all zeros.
> +After the enalement, the user space code can use the "Load Guarded Storage
enablement
> +.SH ERRORS
> +.TP
> +.B EFAULT
> +.I command
> +was
> +.BR GS_SET_BC_CB
> +and the copying of the guarded storage control block structure pointed by the
> +.I gs_cb
> +argument has failed.
> +.TP
> +.B EINVAL
> +The value of
> +.I command
> +is not recognised.
Maybe: "The value specified for command is not a valid command." ?
> +.B EOPNOTSUPP
> +The guarded storage is not supported by the hardware.
"The guarded storage facility is not available."
Thanks for providing the man page!
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: linux-s390@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [man-pages PATCH 5/5] man2: describe s390_guarded_storage s390-specific system call
Date: Sat, 20 Jan 2018 12:23:49 +0000 [thread overview]
Message-ID: <20180120122349.GE6287@osiris> (raw)
In-Reply-To: <20180114185643.GA23919@asgard.redhat.com>
On Sun, Jan 14, 2018 at 07:56:43PM +0100, Eugene Syromyatnikov wrote:
> ---
> man2/s390_guarded_storage.2 | 150 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 150 insertions(+)
> create mode 100644 man2/s390_guarded_storage.2
>
> diff --git a/man2/s390_guarded_storage.2 b/man2/s390_guarded_storage.2
> +.B GS_ENABLE
> +Enable the guarded storage facility for the current task.
> +The initial content of the guarded storage control block will be all zeros.
> +After the enalement, the user space code can use the "Load Guarded Storage
enablement
> +.SH ERRORS
> +.TP
> +.B EFAULT
> +.I command
> +was
> +.BR GS_SET_BC_CB
> +and the copying of the guarded storage control block structure pointed by the
> +.I gs_cb
> +argument has failed.
> +.TP
> +.B EINVAL
> +The value of
> +.I command
> +is not recognised.
Maybe: "The value specified for command is not a valid command." ?
> +.B EOPNOTSUPP
> +The guarded storage is not supported by the hardware.
"The guarded storage facility is not available."
Thanks for providing the man page!
next prev parent reply other threads:[~2018-01-20 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 18:56 [man-pages PATCH 5/5] man2: describe s390_guarded_storage s390-specific system call Eugene Syromyatnikov
[not found] ` <20180114185643.GA23919-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2018-01-20 12:23 ` Heiko Carstens [this message]
2018-01-20 12:23 ` Heiko Carstens
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=20180120122349.GE6287@osiris \
--to=heiko.carstens-ta70fqpds9bqt0dzr+alfa@public.gmane.org \
--cc=aishchuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=haoqf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=jang-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=schwidefsky-tA70FqPdS9bQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.