From: "Maciej W. Rozycki" <macro@mips.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <markus.t.metzger@intel.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] btrace: set/show record btrace cpu
Date: Fri, 02 Mar 2018 19:04:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1803021821430.10166@tp.orcam.me.uk> (raw)
In-Reply-To: <838tbawkpa.fsf@gnu.org>
On Fri, 2 Mar 2018, Eli Zaretskii wrote:
> > So how about:
> >
> > Processor errata are known to exist 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 or workarounds are enabled based on the processor on
> > which the trace was recorded.
>
> That still doesn't explain what are those errata.
>
> How about replacing the first sentence above with these two:
>
> Processor errata are defects in processor operation, caused by its
> design or manufacture. They can cause a trace not to match the
> specification.
Fine with me.
Maciej
next prev parent reply other threads:[~2018-03-02 19:04 UTC|newest]
Thread overview: 17+ 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
[not found] ` <A78C989F6D9628469189715575E55B236964DCE6@IRSMSX104.ger.corp.intel.com>
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
2018-03-01 19:08 ` Eli Zaretskii
2018-03-02 7:09 ` Metzger, Markus T
[not found] ` <alpine.DEB.2.00.1803021350500.10166@tp.orcam.me.uk>
2018-03-02 15:39 ` Eli Zaretskii
2018-03-02 19:04 ` Maciej W. Rozycki [this message]
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=alpine.DEB.2.00.1803021821430.10166@tp.orcam.me.uk \
--to=macro@mips.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
/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