From: Santosh Shukla <sshukla@mvista.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: David Smith <dsmith@redhat.com>, Josh Stone <jistone@redhat.com>,
systemtap@sourceware.org
Subject: Re: [SYSTEMTAP/PATCH v2 0/6] RT aware systemtap patch set
Date: Wed, 17 Sep 2014 08:34:00 -0000 [thread overview]
Message-ID: <CAAyOgsZux_9cBBZgLrYdM+rZSW6_2wjTyU90Tum_avN6xDFT4Q@mail.gmail.com> (raw)
In-Reply-To: <CAAyOgsaNmYGTC_3funSzEyqw-qKkWaCRy7dwqM8cGTG--M3wrQ@mail.gmail.com>
Frank suggested me to run "make installcheck" on -rt and not-rt mode
which I tried and got build failure saying "./execrc: line 4: runtest:
command not found". Anyone knows how to fix this.
I am building/testing vanilla kernel version 3.14.12-rt9 on x86
Ivybridge box [12 cores HT].
On Tue, Sep 16, 2014 at 11:18 PM, Santosh Shukla <sshukla@mvista.com> wrote:
> On Tue, Sep 16, 2014 at 8:10 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
>> Santosh Shukla <sshukla@mvista.com> writes:
>>
>>> [...] This is a v2 version of -rt aware systemtap patchset, tested
>>> for 3.14.12-rt9 and for 3.10.40-rt38 kernel version. [...]
>>
>> Thanks!
>>
>>> [...]
>>> Test script used for testing :
>>> /usr/local/stap/bin/stap -v testsuite/systemtap.examples/network/netdev.stp
>>> /usr/local/stap/bin/stap -v testsuite/systemtap.examples/network/tcpdumplike.stp
>>> [...]
>>> Like know feedback, comment on patch set. also Does it make sense to maintain
>>> systemtap -rt version in upstream.. do we care?
>>
>> Thanks to Josh for looking into this in more detail. I only have the
>> general observation that this patchset would be desirable in mainline
>> stap, but only if it is tested by at least the whole testsuite (rather
>> than just those two samples) on your -rt kernel, *and* if the patched
>> code also runs the whole testsuite on a non-rt kernel. (We don't
>> expect 100% PASS, but also no smoke attributable to the patches.)
>>
>
> Agree, Could you point me testsuite to trigger and test.. I looked
> perhaps not so much keenly.. so it would be good to know right
> pointers about testing details .. I can run test and present the
> report. let me know. Also Any performance specific testsuite too? I
> did asked for in v1 patchset.
> Thanks.
>> - FChE
next prev parent reply other threads:[~2014-09-17 8:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 12:50 Santosh Shukla
2014-09-16 12:50 ` [SYSTEMTAP/PATCH v2 1/6] stp: rt: locking helper api Santosh Shukla
2014-09-16 12:50 ` [SYSTEMTAP/PATCH v2 2/6] stp: rt: replace __stp_tf_map_lock rd/wr lock with stp style raw lock Santosh Shukla
2014-09-16 12:50 ` [SYSTEMTAP/PATCH v2 5/6] stp: rt: replace utrace_struct lock to " Santosh Shukla
2014-09-16 12:50 ` [SYSTEMTAP/PATCH v2 3/6] stp: rt: replace __stp_tf_vma_lock rd/wr lock with stp style of " Santosh Shukla
2014-09-16 12:50 ` [SYSTEMTAP/PATCH v2 6/6] stp: rt: replace __stp_tf_task_work_list_lock to stp raw Santosh Shukla
2014-09-16 12:57 ` [SYSTEMTAP/PATCH v2 4/6] stp: rt: replace utrace->lock with stp style raw lock Santosh Shukla
2014-09-16 14:41 ` [SYSTEMTAP/PATCH v2 0/6] RT aware systemtap patch set Frank Ch. Eigler
2014-09-16 17:48 ` Santosh Shukla
2014-09-17 8:34 ` Santosh Shukla [this message]
2014-09-17 9:56 ` Santosh Shukla
2014-09-19 12:53 ` Santosh Shukla
2014-09-19 14:46 ` David Smith
2014-09-19 17:42 ` Santosh Shukla
2014-09-20 13:12 ` Santosh Shukla
2014-09-22 13:50 ` David Smith
2014-09-22 16:11 ` Santosh Shukla
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=CAAyOgsZux_9cBBZgLrYdM+rZSW6_2wjTyU90Tum_avN6xDFT4Q@mail.gmail.com \
--to=sshukla@mvista.com \
--cc=dsmith@redhat.com \
--cc=fche@redhat.com \
--cc=jistone@redhat.com \
--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).