From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/12341] deref()/store_deref() variations between arches
Date: Mon, 12 Dec 2011 15:21:00 -0000 [thread overview]
Message-ID: <bug-12341-6586-DZW2TMGjkJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12341-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12341
Mark Wielaard <mjw at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
AssignedTo|mjw at redhat dot com |systemtap at sourceware dot
| |org
--- Comment #5 from Mark Wielaard <mjw at redhat dot com> 2011-12-10 20:08:37 UTC ---
The deref/store_deref functions were split into user and kernel versions to
accommodate the s390x setup which uses different address spaces for user and
kernel addresses.
commit f1e8e7e0a601d1378262ba69890ce3e7d4519ab5
Author: Mark Wielaard <mjw@redhat.com>
Date: Fri Nov 25 15:11:00 2011 +0100
loc2c-runtime.h: Split deref and store_deref into user and kernel version.
All references to deref have been updated to use either the user or kernel
variant where appropriate, but kderef is currently still defined as uderef,
and store_kderef as store_uderef. Which should work fine for all arches
except s390.
There are still separate variants for the different architectures.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next parent reply other threads:[~2011-12-10 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12341-6586@http.sourceware.org/bugzilla/>
2011-12-12 15:21 ` mjw at redhat dot com [this message]
2012-02-06 20:49 ` dsmith at redhat dot com
2010-12-22 20:54 [Bug runtime/12341] New: " dsmith at redhat dot com
2011-01-04 21:50 ` [Bug runtime/12341] " dsmith at redhat dot com
2011-01-06 20:58 ` dsmith at redhat dot com
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=bug-12341-6586-DZW2TMGjkJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).