From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Dave Watson <davejwatson@fb.com>, Paul Turner <pjt@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Russell King <linux@arm.linux.org.uk>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Andi Kleen <andi@firstfloor.org>, Chris Lameter <cl@linux.com>,
Ben Maurer <bmaurer@fb.com>, Steven Rostedt <rostedt@goodmis.org>,
Josh Triplett <josh@joshtriplett.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Joel Fernandes <joelaf@google.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [RFC PATCH 0/2] rseq/selftests: debugger single-stepping helper sections
Date: Thu, 14 Mar 2019 15:03:44 -0400 [thread overview]
Message-ID: <20190314190346.24744-1-mathieu.desnoyers@efficios.com> (raw)
Hi,
Those RFC patches improves the rseq selftests to properly expose data
sections helping debuggers to step over rseq critical sections.
* Add a new __rseq_exit_point_array section describing all rseq critical
section exit points so debuggers can properly step over those. This is
based on discussions with gdb and DynamoRIO developers.
* The __rseq_table section contains structures that are aligned on 32
bytes, and in some cases the entries may not be aligned with the
beginning of the section. Rename this section to __rseq_cs, and create
a new __rseq_cs_ptr_array section containing packed 64-bit pointers to
those __rseq_cs entries.
Thanks,
Mathieu
Mathieu Desnoyers (2):
rseq/selftests: Add __rseq_exit_point_array section for debuggers
rseq/selftests: Introduce __rseq_cs_ptr_array, rename __rseq_table to
__rseq_cs
tools/testing/selftests/rseq/rseq-arm.h | 80 +++++++++++++++++++----
tools/testing/selftests/rseq/rseq-arm64.h | 57 +++++++++++++++-
tools/testing/selftests/rseq/rseq-mips.h | 81 +++++++++++++++++++----
tools/testing/selftests/rseq/rseq-ppc.h | 80 +++++++++++++++++++++--
tools/testing/selftests/rseq/rseq-s390.h | 65 +++++++++++++++++-
tools/testing/selftests/rseq/rseq-x86.h | 105 +++++++++++++++++++++++++++++-
6 files changed, 435 insertions(+), 33 deletions(-)
--
2.11.0
next reply other threads:[~2019-03-14 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 19:03 Mathieu Desnoyers [this message]
2019-03-14 19:03 ` [RFC PATCH 1/2] rseq/selftests: Add __rseq_exit_point_array section for debuggers Mathieu Desnoyers
2019-03-14 19:03 ` [RFC PATCH 2/2] rseq/selftests: Introduce __rseq_cs_ptr_array, rename __rseq_table to __rseq_cs Mathieu Desnoyers
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=20190314190346.24744-1-mathieu.desnoyers@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bmaurer@fb.com \
--cc=boqun.feng@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=davejwatson@fb.com \
--cc=hpa@zytor.com \
--cc=joelaf@google.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®