From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Keno Fischer <keno@juliacomputing.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-man <linux-man@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH] ptrace.2: Describe PTRACE_SET/GETREGSET on NT_X86_XSTATE
Date: Wed, 20 May 2020 07:08:25 +0200 [thread overview]
Message-ID: <CAKgNAkgEz5fKjrhZz7yR6Jk7UJ1Lrbfje6eKMhwrPNS_WdAVvg@mail.gmail.com> (raw)
In-Reply-To: <CABV8kRy7XTSv=hJbVSyyKPbT6US7y9AgmG5r9g8AjBJCiVSntw@mail.gmail.com>
On Wed, 20 May 2020 at 05:30, Keno Fischer <keno@juliacomputing.com> wrote:
>
> > > +.SS The layout and operation of the NT_X86_XSTATE regset
> >
> > Should rather have a complete table of NT_* entries first. The others
> > can be dummies for now.
>
> Oh boy, I'm not sure my man-page-formatting-fu is up to the task of
> creating a nice looking table :).
> Michael, can you help?
The general form is simple enough. Assuming, say, a three-column
table, write something like this:
.TS
l l l
---
l l l.
HEAD1<tab>HEAD2<tab>HEAD3
val<tab>val<tab>val<tab>
val<tab>val<tab>val<tab>
...
.TE
I've simplified things somewhat, but if you write your table like
that, I'll fix up any needed formatting afterwards.
For a more complicated example, see the source of syscalls(2).
Thanks,
Michael
next prev parent reply other threads:[~2020-05-20 5:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 3:00 [PATCH] ptrace.2: Describe PTRACE_SET/GETREGSET on NT_X86_XSTATE Keno Fischer
2020-05-19 20:44 ` Michael Kerrisk (man-pages)
2020-05-19 21:29 ` Denys Vlasenko
2020-05-19 22:46 ` Keno Fischer
2020-05-20 10:03 ` Denys Vlasenko
2020-05-20 1:19 ` Andi Kleen
2020-05-20 3:30 ` Keno Fischer
2020-05-20 5:08 ` Michael Kerrisk (man-pages) [this message]
2020-05-20 13:56 ` Andi Kleen
2020-06-08 15:46 ` Michael Kerrisk (man-pages)
2020-06-08 22:07 ` Keno Fischer
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=CAKgNAkgEz5fKjrhZz7yR6Jk7UJ1Lrbfje6eKMhwrPNS_WdAVvg@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=keno@juliacomputing.com \
--cc=linux-man@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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).