This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC PATCH 08/10] arm64/sve: ptrace: Wire up vector length control and reporting
- From: Dave Martin <Dave dot Martin at arm dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>
- Cc: linux-arch at vger dot kernel dot org, Florian Weimer <fweimer at redhat dot com>, libc-alpha at sourceware dot org, Ard Biesheuvel <ard dot biesheuvel at linaro dot org>, Marc Zyngier <Marc dot Zyngier at arm dot com>, gdb at sourceware dot org, Joseph Myers <joseph at codesourcery dot com>, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, linux-arm-kernel at lists dot infradead dot org, Alan Hayward <alan dot hayward at arm dot com>, Torvald Riegel <triegel at redhat dot com>, Christoffer Dall <christoffer dot dall at linaro dot org>
- Date: Mon, 16 Jan 2017 13:32:31 +0000
- Subject: Re: [RFC PATCH 08/10] arm64/sve: ptrace: Wire up vector length control and reporting
- Authentication-results: sourceware.org; auth=none
- References: <1484220369-23970-1-git-send-email-Dave.Martin@arm.com> <1484220369-23970-9-git-send-email-Dave.Martin@arm.com> <20170116122038.GG28060@E107787-LIN>
On Mon, Jan 16, 2017 at 12:20:38PM +0000, Yao Qi wrote:
> On 17-01-12 11:26:07, Dave Martin wrote:
> > This patch adds support for manipulating a task's vector length at
> > runtime via ptrace.
> >
>
> I hope kernel doesn't provide such interface to ptracer to change vector
> length.
It does, with this patch, beacuse...
> The vector length is sort of a read-only property of thread/process/
> program to debugger, unless we really have a clear requirement to modify
> vector length in debugging. I may miss something because I haven't debug
> SVE code yet.
...the vector length is no longer read-only for the task, thanks to
the new prctls().
This does add complexity, but I figured that any programmer's model
state that the thread can modify for itself should be modifiable by the
debugger, if for no other reason than the user may want to experiment to
see what happens. Without a ptrace interface, it would be necessary
to inject a prctl() call into the target, which is possible but awkward.
gdb must already re-detect the vector length on stop, since the target
could have called the prctl() in the meantime.
Access via ptrace also allows things like trapping on exec, fork or
clone and changing the vector length for the new process or thread
before it starts to run. I'm guessing here, but such a scenario seems
legitimate (?)
[...]
Cheers
---Dave