From: Masami Hiramatsu <mhiramat@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Theodore Tso <tytso@mit.edu>, systemtap@sources.redhat.com
Subject: Re: Discussion at Linux Foundation Japan Symposium
Date: Mon, 12 Jan 2009 19:29:00 -0000 [thread overview]
Message-ID: <496B9A25.1070405@redhat.com> (raw)
In-Reply-To: <20090112185217.GE18407@redhat.com>
Hi Frank,
Frank Ch. Eigler wrote:
> Hi -
>
> On Mon, Jan 12, 2009 at 01:17:49PM -0500, Masami Hiramatsu wrote:
>> [...]
>> Frank Ch. Eigler wrote:
>>> That is one possible solution for this specific problem -- rawhide
>>> systemtap users who're unable/unwilling to build systemtap out of git
>>> occasoinally. (Remember that the recent 2.6.28 breakage took a few
>>> hours to fix.)
>>>
>>> Another solution would be for rawhide-style distributions to
>>> aggressively package systemtap snapshots into their development
>>> streams [...]
>> Even if we do that, we have to clarify which package can be applied
>> to which kernel version.
>
> In what way? There would be one package in rawhide, which should work
> on every kernel version that we've ever worked with. It would be
> replaced frequently - perhaps every few days.
For example, commenting in each snapshot release note.
e.g. - tested on 2.6.28.
>> I'm still not sure when some bugs reported on this ml are fixed -
>> e.g. http://sources.redhat.com/ml/systemtap/2009-q1/msg00029.html
>
> There was no bugzilla report associated with it, but it was fixed the
> same day.
Thank you. I think we should notice that fix to reporters.
>> BTW, more those kind of bugfix are committed, more autoconfs are
>> introduced. We already has 15(!) autoconfs,
>
> Yes, but as you know, their cost has a benefit: they enable our
> operation with a whole spectrum of kernel versions.
I know that it is so useful for older kernels. However, once the
runtime is merged to upstream, we don't need to prepare those autoconfs
and to recompile systemtap itself.
>> and these autoconfs increase compilation time (this will be avoided
>> by caching the result per kernel...).[...]
>
> FWIW, on my workstation, they seem to add about a second.
Sure, autoconf compilation overhead may not be so big problem...
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-01-12 19:29 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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
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=496B9A25.1070405@redhat.com \
--to=mhiramat@redhat.com \
--cc=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=tytso@mit.edu \
/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).