From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 8/9] btrace: identify cpu
Date: Thu, 05 Feb 2015 18:31:00 -0000 [thread overview]
Message-ID: <54D3B716.2070409@redhat.com> (raw)
In-Reply-To: <1423150072-21229-9-git-send-email-markus.t.metzger@intel.com>
On 02/05/2015 04:27 PM, Markus Metzger wrote:
> Add a struct for identifying a processor and use it in linux-btrace.c when
> identifying the processor we're running on.
>
> We will need this feature for the new btrace format.
>
> 2015-02-05 Markus Metzger <markus.t.metzger@intel.com>
>
> gdb/
> * common/btrace-common.h (btrace_cpu_vendor, btrace_cpu): New.
> * nat/linux-btrace.c: Include x86-cpuid.h.
This looks stale.
> (btrace_this_cpu): New.
> (cpu_supports_bts): Call btrace_this_cpu.
> (intel_supports_bts): Add cpu parameter.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-02-05 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 15:27 [PATCH v4 0/9] record btrace: prepare for a new trace format Markus Metzger
2015-02-05 15:28 ` [PATCH v4 8/9] btrace: identify cpu Markus Metzger
2015-02-05 18:31 ` Pedro Alves [this message]
2015-02-05 15:28 ` [PATCH v4 7/9] btrace: extend struct btrace_insn Markus Metzger
2015-02-05 15:28 ` [PATCH v4 3/9] btrace, linux: add perf event buffer abstraction Markus Metzger
2015-02-05 15:28 ` [PATCH v4 2/9] btrace: add format argument to supports_btrace Markus Metzger
2015-02-05 15:28 ` [PATCH v4 9/9] record-btrace: indicate gaps Markus Metzger
2015-02-05 15:28 ` [PATCH v4 6/9] btrace: update btrace_compute_ftrace parameters Markus Metzger
2015-02-05 15:28 ` [PATCH v4 4/9] record btrace: add configuration struct Markus Metzger
2015-02-05 16:27 ` Eli Zaretskii
2015-02-05 18:31 ` Pedro Alves
2015-02-05 15:28 ` [PATCH v4 1/9] btrace: add struct btrace_data Markus Metzger
2015-02-05 15:28 ` [PATCH v4 5/9] record-btrace: add bts buffer size configuration option Markus Metzger
2015-02-05 16:25 ` Eli Zaretskii
2015-02-05 18:33 ` [PATCH v4 0/9] record btrace: prepare for a new trace format Pedro Alves
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=54D3B716.2070409@redhat.com \
--to=palves@redhat.com \
--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