public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: "Maciej W. Rozycki" <macro@mips.com>, 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: Mon, 05 Mar 2018 10:58:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B236964F930@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1803021910080.10166@tp.orcam.me.uk>

Hello Eli, Maciej,

> > >  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.

Fine with me, as well.  I will send out the full series with the updated
wording and a reduced column limit.

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

      reply	other threads:[~2018-03-05 10:58 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
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 [this message]

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=A78C989F6D9628469189715575E55B236964F930@IRSMSX104.ger.corp.intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@mips.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).