From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/4037] make staprun 32/64-bit interoperable
Date: Wed, 14 Feb 2007 02:28:00 -0000 [thread overview]
Message-ID: <20070214022801.13236.qmail@sourceware.org> (raw)
In-Reply-To: <20070214005619.4037.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2007-02-14 02:28 -------
> I intentionally disabled it because it was making a lot of code very messy.
Indeed, which made sense in the absence of a target-neutral "wire protocol"
between the kernel and staprun. That is in effect what I am proposing
be developed. Consider it an enhancement if you like.
> [...] I am confused about how this situation occurred and why it is
> desirable to have 32-bit stapruns work on 64-bit kernels.
At the moment, the issue arises on "multilib" (really, multi-ISA) architectures
where a kernel can run more than one type of binary transparently. Hence the
wrong staprun might get installed, even though they both would "work" as far
as being executable is concerned. This gets even more entertaining should the
same machine be equipped to run either 32- or 64-bit kernel, with a primarily
32-bit userspace. It would be nice to avoid requiring reinstalling staprun
just because one rebooted.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
Last reconfirmed|0000-00-00 00:00:00 |2007-02-14 02:28:01
date| |
http://sourceware.org/bugzilla/show_bug.cgi?id=4037
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-02-14 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 0:56 [Bug runtime/4037] New: " fche at redhat dot com
2007-02-14 2:10 ` [Bug runtime/4037] " hunt at redhat dot com
2007-02-14 2:28 ` fche at redhat dot com [this message]
2008-01-11 18:06 ` hunt at redhat dot com
2008-04-30 19:02 ` fche at redhat dot com
2009-11-16 20:47 ` dsmith at redhat dot com
2009-11-18 1:12 ` fche at redhat dot com
2009-11-20 8:39 ` pavan dot naregundi at in dot ibm 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=20070214022801.13236.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).