public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Simon Sobisch <simonsobisch@gnu.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: How to get software recording to work?
Date: Mon, 24 Jan 2022 09:27:40 +0000	[thread overview]
Message-ID: <DM8PR11MB57490806BED63E931C95F44CDE5E9@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <932be60f-b2d3-11fe-929c-4ad9d702be8c@gnu.org>

Hello Simon,

>Thanks Markus for your answers (just in case: they weren't CC'ed to the
>mailing list, not sure if this was by intent).

It was not.  My email client sometimes removes mailing lists when I 'reply all' and I forgot to re-add it.  Thanks for pointing it out.


>> The issue is lack of AVX support in the record full instruction decoder.
>>
>>> Can this recording be done reliably? Which places would need to be fixed
>>> / adjusted to get this working?
>>
>> AFAIK record full also has issues with multi-threaded processes.  To fix the
>instruction decode issue, the best approach IMHO would be to extend the
>instruction decoder that is used for disassembly and use that for record full.
>
>Is this something Intel may have a look at?
>
>I guess Instruction/Processor specific instructions are possibly best
>implemented by the vendors, aren't them?

Intel is maintaining the binutils disassembler.  It is a bit unfortunate that record full uses a separate instruction decoder.

Given the issues with multi-threaded debuggee processes, I'm not sure how usable record full would be.  Or how much it would be used if we were to enable AVX.  I remember it adding significant recording overhead.

Regards,
Markus.
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

      parent reply	other threads:[~2022-01-24  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 15:15 Simon Sobisch
     [not found] ` <DM8PR11MB5749520182B9D686E8254730DE5E9@DM8PR11MB5749.namprd11.prod.outlook.com>
     [not found]   ` <932be60f-b2d3-11fe-929c-4ad9d702be8c@gnu.org>
2022-01-24  9:27     ` 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=DM8PR11MB57490806BED63E931C95F44CDE5E9@DM8PR11MB5749.namprd11.prod.outlook.com \
    --to=markus.t.metzger@intel.com \
    --cc=gdb@sourceware.org \
    --cc=simonsobisch@gnu.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).