From: Ingo Molnar <mingo@elte.hu>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, tglx@linutronix.de,
ak@suse.de, "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
akpm@linux-foundation.org
Subject: Re: [patch 1/2] x86, ptrace: support for branch trace store(BTS)
Date: Thu, 29 Nov 2007 11:43:25 +0100 [thread overview]
Message-ID: <20071129104325.GF10577@elte.hu> (raw)
In-Reply-To: <029E5BE7F699594398CA44E3DDF5544401024076@swsmsx413.ger.corp.intel.com>
* Metzger, Markus T <markus.t.metzger@intel.com> wrote:
> Changes to previous version(s):
> - moved task arrives/departs notifications to __switch_to_xtra()
> - added _TIF_BTS_TRACE and _TIF_BTS_TRACE_TS to _TIF_WORK_CTXSW_*
> - split _TIF_WORK_CTXSW into ~_PREV and ~_NEXT for x86_64
> - ptrace_bts_init_intel() function called from init_intel()
> - removed PTRACE_BTS_INIT ptrace command
> - cache DEBUGCTRL MSR
> - replace struct declarations and operations struct with
> configuration struct defining offset/size pairs and
> generic operations
> - added a patch for the ptrace.2 man page for discussing the API
> in this forum
i tried to apply your patches to x86.git, but your patches were
linewrapped and had strange artifacts in them:
| @@ -610,6 +612,32 @@
| (struct user_desc __user *)
| data);
| break;
| =20
| + case PTRACE_BTS_ALLOCATE_BUFFER:
| +
could you please resend with this fixed (preferably against x86.git,
which has Roland's ptrace cleanups?).
Ingo
next prev parent reply other threads:[~2007-11-29 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 8:14 [patch 1/2] x86, ptrace: support for branch trace store(BTS) Metzger, Markus T
2007-11-29 10:43 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-30 10:52 Markus Metzger
2007-11-30 11:05 ` Ingo Molnar
2007-11-30 15:59 Markus Metzger
2007-12-04 18:04 Markus Metzger
2007-12-05 15:32 ` Ingo Molnar
2007-12-05 18:59 Markus Metzger
2007-12-05 20:26 ` Ingo Molnar
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=20071129104325.GF10577@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.