From: "Jun Koi" <junkoi2004@gmail.com>
To: "jidong xiao" <jidong.xiao@gmail.com>
Cc: "Satoshi OSHIMA" <satoshi.oshima.fk@hitachi.com>,
systemtap@sourceware.org, "\"平松@RedHat\"" <mhiramat@redhat.com>,
橋本K <hisashi.hashimoto.wh@hitachi.com>,
"Yumiko SUGITA" <yumiko.sugita.yf@hitachi.com>
Subject: Re: Discussion at Linux Foundation Japan Symposium
Date: Thu, 18 Dec 2008 09:28:00 -0000 [thread overview]
Message-ID: <fdaac4d50812180120s5a7ceed1n848f08cf89aa7a64@mail.gmail.com> (raw)
In-Reply-To: <4104961b0812180106n69d1e25ej269d36f39b5426b@mail.gmail.com>
On Thu, Dec 18, 2008 at 6:06 PM, jidong xiao <jidong.xiao@gmail.com> wrote:
> On Thu, Dec 18, 2008 at 4:57 PM, Jun Koi <junkoi2004@gmail.com> wrote:
>> On Thu, Dec 18, 2008 at 5:09 PM, Satoshi OSHIMA
>> <satoshi.oshima.fk@hitachi.com> wrote:
>>> Hi all,
>>>
>>> Long time no see and sorry for my late report.
>>>
>>> I attended 9th Linux Foundation Japan Symposium and
>>> discussed on issues of systemtap project with Ted Ts'o,
>>> James Bottomley and Jonathan Corbet.
>>>
>>> In my understanding, they demand the following things:
>>>
>>> (1) Follow upstream first
>>>
>>> Utrace and uprobe features are currently available only
>>> on Fedora and Red Hat Enterprise Linux, since those
>>> patches are not merged into upstream kernel yet.
>>>
>>> my suggestion:
>>>
>>> To reduce complaints of upstream kernel developers,
>>> systemtap project may need to postpone adding new
>>> uprobe features until getting utrace (and uprobe)
>>> patch set accepted in mainline.
>>>
>>>
>>> (2) Maintain tapset
>>>
>>> Systemtap users (including kernel developers) get
>>> frustrated because tapsets often do not work on
>>> the latest kernel. Moreover, sometimes users
>>> have to fix the tapset incompatibility of kernels.
>>>
>>> my suggestion:
>>>
>>> If systemtap procjet can fix this kind of incompatibilities
>>> within a few hours or days as Myths about systemtap
>>> on the wiki claims, releasing new systemtap minor release
>>> tarball for each upstream kernel release would help users.
>>>
>>>
>>> (3) Make no debuginfo version
>>>
>>> Systemtap always requires kernel debuginfo to use.
>>> Unfortunately, it is hard for users of some distributions
>>> to have debuginfo.
>>>
>>
>> How is it possible to do that without kernel debug info? Currently
>> systemtap extracts lots of information on kernel layout from debug
>> info, so I dont understand why we can survive without that.
>>
>> Thanks,
>> Jun
>>
> But not every distribution contains kernel debuginfo packages,
> therefore this makes many people not easy to use systemtap.
>
But my question is: how can we survive without debug info? In that
case, we cannot tap into kernel anymore? (I guess tap on userspace
still works)
Thanks,
Jun
next prev parent reply other threads:[~2008-12-18 9:21 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 8:33 Satoshi OSHIMA
2008-12-18 8:59 ` KOSAKI Motohiro
2008-12-18 9:07 ` Jun Koi
2008-12-18 9:21 ` jidong xiao
2008-12-18 9:28 ` Jun Koi [this message]
2008-12-18 9:35 ` KOSAKI Motohiro
2008-12-18 9:37 ` Jun Koi
2008-12-18 9:42 ` Jun Koi
2008-12-18 9:46 ` KOSAKI Motohiro
2008-12-18 9:58 ` K.Prasad
2008-12-18 10:02 ` KOSAKI Motohiro
2008-12-18 10:21 ` K.Prasad
2008-12-18 15:52 ` Masami Hiramatsu
2008-12-18 15:41 ` Masami Hiramatsu
2008-12-18 17:11 ` Frank Ch. Eigler
2008-12-19 0:08 ` KOSAKI Motohiro
2008-12-19 0:58 ` Frank Ch. Eigler
2008-12-19 1:39 ` KOSAKI Motohiro
2008-12-19 23:51 ` William Cohen
2008-12-20 1:51 ` Richard J Moore
2008-12-20 14:27 ` Masami Hiramatsu
2008-12-19 0:45 ` Masami Hiramatsu
2008-12-22 18:22 Frank Ch. Eigler
2008-12-22 20:38 ` Theodore Tso
2008-12-22 22:41 ` Frank Ch. Eigler
2008-12-23 0:33 ` Theodore Tso
2008-12-23 0:34 ` Masami Hiramatsu
2008-12-23 0:44 ` Theodore Tso
2008-12-23 21:13 ` Roland McGrath
2008-12-23 22:13 ` Masami Hiramatsu
2008-12-23 14:28 ` Frank Ch. Eigler
2008-12-23 22:21 ` Roland McGrath
2008-12-23 22:33 ` Masami Hiramatsu
2008-12-23 22:44 ` Roland McGrath
2008-12-24 3:40 ` Masami Hiramatsu
2008-12-24 8:48 ` Roland McGrath
2008-12-24 18:14 ` Masami Hiramatsu
2008-12-24 19:26 ` Roland McGrath
2008-12-24 21:02 ` Theodore Tso
2008-12-26 18:17 ` Roland McGrath
2008-12-23 23:27 ` Theodore Tso
2008-12-24 6:11 ` Masami Hiramatsu
2009-01-10 2:48 ` Theodore Tso
2009-01-11 16:29 ` Frank Ch. Eigler
2009-01-12 18:18 ` Masami Hiramatsu
2009-01-12 18:53 ` Frank Ch. Eigler
2009-01-12 19:29 ` Masami Hiramatsu
2009-01-12 19:26 ` Theodore Tso
2009-01-12 20:01 ` Frank Ch. Eigler
2009-01-12 19:05 ` Jason Baron
2009-01-12 19:52 ` Theodore Tso
2009-01-12 20:32 ` Frank Ch. Eigler
2009-01-08 9:22 ` Roland McGrath
2009-01-10 1:33 ` Theodore Tso
2008-12-22 23:34 ` Masami Hiramatsu
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=fdaac4d50812180120s5a7ceed1n848f08cf89aa7a64@mail.gmail.com \
--to=junkoi2004@gmail.com \
--cc=hisashi.hashimoto.wh@hitachi.com \
--cc=jidong.xiao@gmail.com \
--cc=mhiramat@redhat.com \
--cc=satoshi.oshima.fk@hitachi.com \
--cc=systemtap@sourceware.org \
--cc=yumiko.sugita.yf@hitachi.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).