From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 2/2] btrace: set/show record btrace cpu
Date: Thu, 01 Mar 2018 16:24:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B236964E8FF@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <83muzryhql.fsf@gnu.org>
Hello Eli,
> > > > > @cindex processor errata
> > > > > @dfn{Processor errata} are bugs in processor firmware that can cause
> > > > > a trace not to match the specification. Trace decoders that are
> > > > > unaware of these errata might fail to decode such a trace.
> > > > > @value{GDBN} can detect erroneous trace packets and correct them,
> > > > > thus avoiding the decoding failures. These corrections are known as
> > > > > @dfn{errata workarounds}, and are enabled based on the processor on
> > > > > which the trace was recorded.
> > > >
> > > But that completely loses the explanation of what the errata are.
> > > If my explanation is not accurate, let's correct it, rather than deleting it.
> >
> > I didn't mean to delete your explanation. I only removed the 'firmware' part.
>
> The text I proposed is above. It begins with an explanation of what those errata
> are, and why they are detrimental to btrace. The text you proposed instead is
> this:
>
> Errata may cause the recorded trace to not match the specification.
> This, in turn, may cause trace decode to fail. @value{GDBN} can
> detect erroneous trace packets and correct them, thus avoiding the
> decoding failures. These corrections are known as @dfn{errata
> workarounds}, and are enabled based on the processor on which the
> trace was recorded.
>
> This just says that trace decode can fail, but tells nothing about the phenomenon
> itself. Thus my "completely loses" reaction.
>
> But I don't want to argue. If you feel that the text you wrote is good enough, go
> ahead and push it, even though I'm unhappy.
I'd rather we find a wording we can all agree on.
I added that errata cause the trace to not match the spec and that this would
cause decode to fail.
I removed the bit about errata being in the firmware since that is not correct.
And I replaced "unaware decoders might fail to decode such a trace" with "This,
in turn, may cause trace decode to fail".
The rest I took as you suggested.
Where do you think we need to improve the wording?
Thanks,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2018-03-01 16:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 9:52 [PATCH 1/2] btrace: fix output of "set record btrace" Markus Metzger
2018-02-23 9:52 ` [PATCH 2/2] btrace: set/show record btrace cpu Markus Metzger
2018-02-23 13:52 ` Eli Zaretskii
2018-02-26 15:45 ` Metzger, Markus T
2018-02-26 19:13 ` Eli Zaretskii
2018-02-27 11:41 ` Metzger, Markus T
2018-02-27 18:23 ` Eli Zaretskii
2018-02-28 7:38 ` Metzger, Markus T
2018-02-28 15:37 ` Eli Zaretskii
2018-03-01 7:05 ` Metzger, Markus T
2018-03-01 14:48 ` Eli Zaretskii
2018-03-01 16:24 ` Metzger, Markus T [this message]
2018-03-01 19:08 ` Eli Zaretskii
2018-03-02 7:09 ` Metzger, Markus T
2018-03-02 14:50 ` Maciej W. Rozycki
2018-03-02 15:39 ` Eli Zaretskii
2018-03-02 19:04 ` Maciej W. Rozycki
2018-03-02 19:49 ` Maciej W. Rozycki
2018-03-05 10:58 ` Metzger, Markus T
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=A78C989F6D9628469189715575E55B236964E8FF@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).