From: Mark Wielaard <mjw@redhat.com>
To: David Smith <dsmith@redhat.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Systemtap List <systemtap@sourceware.org>
Subject: Re: s390x help needed - kernel read faults
Date: Mon, 07 Nov 2011 17:18:00 -0000 [thread overview]
Message-ID: <20111107171736.GA11606@hermans.wildebeest.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-11-07 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 18:42 David Smith
[not found] ` <20111018052305.GA22831@in.ibm.com>
[not found] ` <20111018081753.GA2578@osiris.boeblingen.de.ibm.com>
[not found] ` <4E9D8577.9030705@redhat.com>
[not found] ` <20111028124058.GA2475@osiris.boeblingen.de.ibm.com>
2011-10-28 18:43 ` David Smith
2011-10-31 10:29 ` Heiko Carstens
2011-11-07 16:03 ` David Smith
2011-11-07 17:18 ` Mark Wielaard [this message]
2011-11-08 12:18 ` Heiko Carstens
2011-11-26 1:50 ` Mark Wielaard
2011-11-28 11:20 ` Mark Wielaard
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=20111107171736.GA11606@hermans.wildebeest.org \
--to=mjw@redhat.com \
--cc=ananth@in.ibm.com \
--cc=dsmith@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=systemtap@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).