public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Quentin Barnes <qbarnes@urbana.css.mot.com>
To: systemtap@sources.redhat.com
Subject: 64-bit integeer data types and the Linux kernel
Date: Wed, 02 May 2007 16:33:00 -0000	[thread overview]
Message-ID: <20070502163321.GA12378@urbana.css.mot.com> (raw)

I've been going over some of my ARM port work of the Systemtap
runtime environment in anticipation of sending it out to this list.
The port work brought up a Linux kernel question I had a few years
ago and never got a satisfactory answer.

I noticed in runtime/arith.c, Systemtap has to supply 64-bit support
arithmetic for some architectures.  (I've added ARM support now.)

Why does Systemtap have to do this?  (Rhetorical question!)  Because
the kernel doesn't always have these missing 64-bit integer routines
for all architectures.  Okay, why doesn't the kernel fully support
64-bit integer types for all architectures?

I never got an answer to that last question when I asked it three
years ago when helping someone port a driver who needed to do a
divide of a 64-bit integer.  Can anyone these days give me the
reason or logic as to why?

If it is because of space concerns, then why can't it be made a
configurable kernel option that Systemtap or anyone else can enable
as need be?  (That's a real question.  Can anyone answer that
question for me?)  Has anyone tried this angle with regards to
Systemtap's needs?

I tried googling to see if I could find an old discussion on this
but got way too many hits and none seemed pertinent.  If someone
could point me to old postings on this issue, I'd appreciate it.

Quentin

             reply	other threads:[~2007-05-02 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 16:33 Quentin Barnes [this message]
2007-05-02 16:54 ` Martin Hunt

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=20070502163321.GA12378@urbana.css.mot.com \
    --to=qbarnes@urbana.css.mot.com \
    --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).