This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: s390x help needed - kernel read faults
- From: Mark Wielaard <mjw at redhat dot com>
- To: David Smith <dsmith at redhat dot com>
- Cc: Heiko Carstens <heiko dot carstens at de dot ibm dot com>, Ananth N Mavinakayanahalli <ananth at in dot ibm dot com>, Systemtap List <systemtap at sourceware dot org>
- Date: Mon, 7 Nov 2011 18:17:37 +0100
- Subject: Re: s390x help needed - kernel read faults
- References: <4E9C76F7.6010802@redhat.com> <20111018052305.GA22831@in.ibm.com> <20111018081753.GA2578@osiris.boeblingen.de.ibm.com> <4E9D8577.9030705@redhat.com> <20111028124058.GA2475@osiris.boeblingen.de.ibm.com> <4EAAF791.1060109@redhat.com> <20111031102934.GA4768@osiris.boeblingen.de.ibm.com> <4EB80147.8050303@redhat.com>
On Mon, Nov 07, 2011 at 10:03:19AM -0600, David Smith wrote:
> I'm not sure why we provided our own functions, that decision was made a
> long time ago. If we can't look at the address and know whether it is a
> user space or kernel space address, then I don't see much choice than to
> break up our memory accesses and require the callers to know whether
> they are accessing kernel space or user space.
Yes, it seems not that hard to track fully, we mostly do know already.
The only place where it would be helpful to determine whether or not
a address is valid for either kernel or user space would be in the
unwinder. There we walk the stack and stop and/or switch from kernel
to user stack walking based on whether the PC address is a valid
kernel or user space address. Is there really no way to tell the
difference on s390x from kernel space?
Thanks,
Mark