public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Metzger, Markus T" <markus.t.metzger@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v4 10/10] btrace: Extend ptwrite event decoding.
Date: Wed, 11 May 2022 08:19:22 +0000	[thread overview]
Message-ID: <MN2PR11MB4566048C5D55CDF37A4393A68EC89@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <83sfphsciu.fsf@gnu.org>

> -----Original Message-----
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Dienstag, 10. Mai 2022 16:12
> To: Willgerodt, Felix <felix.willgerodt@intel.com>
> Cc: Metzger, Markus T <markus.t.metzger@intel.com>; gdb-
> patches@sourceware.org
> Subject: Re: [PATCH v4 10/10] btrace: Extend ptwrite event decoding.
> 
> > From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
> > CC: "Metzger, Markus T" <markus.t.metzger@intel.com>,
> > 	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> > Date: Tue, 10 May 2022 13:43:02 +0000
> >
> > > The last line is too long, and will cause overfull hbox errors when
> > > producing the printed manual.  Please make it shorter, or break into 2
> > > lines.
> > >
> >
> > I made it shorter. Is there any easy way to figure this out? I don't know
> what
> > Is short enough
> 
> I think the rule of thumb is that anything longer than 70 characters
> in @smallexample should be split.
>

Thanks that is good to know!

> > and I couldn't see any  "Overfull \hbox" message for
> > python.texi in gdb.log or in the output for "make pdf".
> 
> I believe that's because we have @finalout in gdb.texinfo.
>

For what it's worth: There are some overfull messages, even
for python.texi. Just not for my changes.

> > > You say "hardware and operating system support", but say nothing about
> > > the OSes on which this can be supported.
> > >
> >
> > Any OS can choose to support it at some point. Right now it is Linux only
> afaik.
> > But do we want to say that? It might be out-dated at some point.
> 
> I don't know.  How probable is it that this will be supported on other
> systems soon enough?

I don't know. Microsoft has added some IPT support for performance
monitoring recently:
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/performance-monitoring-hardware
I am not aware what that means for debuggers. GDB currently doesn't
Support IPT on Windows afaik, but I have never tried it.
But it certainly doesn't seem completely out of the picture for the future.

Thanks,
Felix
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2022-05-11  8:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 11:40 [PATCH v4 01/10] btrace: Introduce auxiliary instructions Felix Willgerodt
2022-05-06 11:40 ` [PATCH v4 02/10] btrace: Enable auxiliary instructions in record instruction-history Felix Willgerodt
2022-05-06 11:46   ` Eli Zaretskii
2022-05-06 11:40 ` [PATCH v4 03/10] btrace: Enable auxiliary instructions in record function-call-history Felix Willgerodt
2022-05-06 11:48   ` Eli Zaretskii
2022-05-06 11:40 ` [PATCH v4 04/10] btrace: Handle stepping and goto for auxiliary instructions Felix Willgerodt
2022-05-06 11:40 ` [PATCH v4 05/10] python: Introduce gdb.RecordAuxiliary class Felix Willgerodt
2022-05-06 11:49   ` Eli Zaretskii
2022-05-06 11:40 ` [PATCH v4 06/10] python: Add clear() to gdb.Record Felix Willgerodt
2022-05-06 11:50   ` Eli Zaretskii
2022-05-10 13:42     ` Willgerodt, Felix
2022-05-10 14:04       ` Eli Zaretskii
2022-05-11  8:22         ` Willgerodt, Felix
2022-05-11 11:43           ` Eli Zaretskii
2022-05-06 11:40 ` [PATCH v4 07/10] btrace, gdbserver: Add ptwrite to btrace_config_pt Felix Willgerodt
2022-05-06 11:53   ` Eli Zaretskii
2022-05-10 13:42     ` Willgerodt, Felix
2022-05-06 11:40 ` [PATCH v4 08/10] btrace, linux: Enable ptwrite packets Felix Willgerodt
2022-05-06 11:40 ` [PATCH v4 09/10] btrace, python: Enable ptwrite listener registration Felix Willgerodt
2022-05-06 11:40 ` [PATCH v4 10/10] btrace: Extend ptwrite event decoding Felix Willgerodt
2022-05-06 12:04   ` Eli Zaretskii
2022-05-10 13:43     ` Willgerodt, Felix
2022-05-10 14:11       ` Eli Zaretskii
2022-05-11  8:19         ` Willgerodt, Felix [this message]
2022-05-06 11:47 ` [PATCH v4 01/10] btrace: Introduce auxiliary instructions Eli Zaretskii
2022-05-10 13:42   ` Willgerodt, Felix

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=MN2PR11MB4566048C5D55CDF37A4393A68EC89@MN2PR11MB4566.namprd11.prod.outlook.com \
    --to=felix.willgerodt@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).