From: Eli Zaretskii <eliz@gnu.org>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] btrace: set/show record btrace cpu
Date: Mon, 05 Mar 2018 16:16:00 -0000 [thread overview]
Message-ID: <83y3j6sdk9.fsf@gnu.org> (raw)
In-Reply-To: <1520247555-4643-2-git-send-email-markus.t.metzger@intel.com> (message from Markus Metzger on Mon, 5 Mar 2018 11:59:15 +0100)
> From: Markus Metzger <markus.t.metzger@intel.com>
> Date: Mon, 5 Mar 2018 11:59:15 +0100
>
> 2018-03-05 Markus Metzger <markus.t.metzger@intel.com>
>
> gdb/
> * NEWS (New options): announce set/show record btrace cpu.
> * btrace.c: Include record-btrace.h.
> (btrace_compute_ftrace_pt): Skip enabling errata workarounds if the
> vendor is unknown.
> (btrace_compute_ftrace_1): Add cpu parameter. Update callers.
> Maybe overwrite the btrace configuration's cpu.
> (btrace_compute_ftrace): Add cpu parameter. Update callers.
> (btrace_fetch): Add cpu parameter. Update callers.
> (btrace_maint_update_pt_packets): Call record_btrace_get_cpu. Maybe
> overwrite the btrace configuration's cpu. Skip enabling errata
> workarounds if the vendor is unknown.
> * python/py-record-btrace.c: Include record-btrace.h.
> (recpy_bt_begin, recpy_bt_end, recpy_bt_instruction_history)
> (recpy_bt_function_call_history): Call record_btrace_get_cpu.
> * record-btrace.c (record_btrace_cpu_state_kind): New.
> (record_btrace_cpu): New.
> (set_record_btrace_cpu_cmdlist): New.
> (record_btrace_get_cpu): New.
> (require_btrace_thread, record_btrace_info)
> (record_btrace_resume_thread): Call record_btrace_get_cpu.
> (cmd_set_record_btrace_cpu_none): New.
> (cmd_set_record_btrace_cpu_auto): New.
> (cmd_set_record_btrace_cpu): New.
> (cmd_show_record_btrace_cpu): New.
> (_initialize_record_btrace): Initialize set/show record btrace cpu
> commands.
> * record-btrace.h (record_btrace_get_cpu): New.
>
> testsuite/
> * gdb.btrace/cpu.exp: New.
>
> doc/
> * gdb.texinfo: Document set/show record btrace cpu.
OK for the documentation parts.
Thanks.
next prev parent reply other threads:[~2018-03-05 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 10:59 [PATCH v2 1/2] btrace: fix output of "set record btrace" Markus Metzger
2018-03-05 10:59 ` [PATCH v2 2/2] btrace: set/show record btrace cpu Markus Metzger
2018-03-05 16:16 ` Eli Zaretskii [this message]
2018-03-05 16:35 ` [PATCH v2 1/2] btrace: fix output of "set record btrace" Alan Hayward
2018-03-05 16:55 ` Metzger, Markus T
2018-03-06 9:34 ` Alan Hayward
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=83y3j6sdk9.fsf@gnu.org \
--to=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