From: David Smith <dsmith@redhat.com>
To: Santosh Shukla <sshukla@mvista.com>
Cc: Josh Stone <jistone@redhat.com>, systemtap@sourceware.org
Subject: Re: [SYSTEMTAP/PATCH v2 0/6] RT aware systemtap patch set
Date: Mon, 22 Sep 2014 13:50:00 -0000 [thread overview]
Message-ID: <5420292C.9050106@redhat.com> (raw)
In-Reply-To: <CAAyOgsYxraDjBerEDicAERV7D4LT8ekY43kCnu6VeZ80mWZz7Q@mail.gmail.com>
On 09/20/2014 08:12 AM, Santosh Shukla wrote:
> Hi,
>
> On Fri, Sep 19, 2014 at 11:12 PM, Santosh Shukla <sshukla@mvista.com> wrote:
>> On Fri, Sep 19, 2014 at 8:16 PM, David Smith <dsmith@redhat.com> wrote:
>>> On 09/16/2014 07:49 AM, Santosh Shukla wrote:
>>>> Hi,
>>>>
>>>> This is a v2 version of -rt aware systemtap patchset, tested for 3.14.12-rt9 and for 3.10.40-rt38 kernel version.
>>>> For v1->v2 related details refer [1]. Patchset based on stap upstream link [2] master branch.
>>>
>>> I did a bit of testing on these patches.
>>>
>>> First I tested plain systemtap code on 3.10.0-153.el7.x86_64 to get a
>>> baseline. I then applied the 6 patches, and re-ran the entire testsuite
>>> on that kernel. No changes. Great.
>>>
>>> I then put 3.10.0-155.rt56.79.el7rt.x86_64 on that same system and ran
>>> the testsuite. Unfortunately the system crashes somewhere in check.exp.
>>> So, we've still got a ways to go.
>>>
>>
>> Right, I fixed those.. still seeing few deadlock. I'll update v3 patch
>> set passing installcheck testsuite soon. Thanks.
>
> Test result summary for make installcheck using el7 config on -rt and
> non-rt mode tested on vanilla 3.14.12 (non-rt) and on 3.14.12-rt9
> kernel below :
Let me see if I understand this:
-rt mode: This is your patched systemtap running on a rt kernel
non-rt mode: This is your patches systemtap running on a regular,
non-rt, kernel.
Is the above correct?
> 1) -rt mode:
>
>
> === systemtap Summary ===
>
> # of expected passes 5060
> # of unexpected failures 131
> # of unexpected successes 1
> # of expected failures 315
> # of known failures 68
> # of untested testcases 275
> # of unsupported tests 4
>
>
>
> 2) non-rt mode:
>
> === systemtap Summary ===
>
> # of expected passes 4988
> # of unexpected failures 181
> # of unexpected successes 1
> # of expected failures 315
> # of known failures 68
> # of untested testcases 285
> # of unsupported tests 4
What's odd here is that the number of unexpected failures is higher on
the non-rt kernel. I would have expected the other way around.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
next prev parent reply other threads:[~2014-09-22 13:50 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 6/6] stp: rt: replace __stp_tf_task_work_list_lock to stp raw 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 raw lock Santosh Shukla
2014-09-16 12:50 ` [SYSTEMTAP/PATCH v2 5/6] stp: rt: replace utrace_struct lock to stp style " Santosh Shukla
2014-09-16 12:50 ` [SYSTEMTAP/PATCH v2 2/6] stp: rt: replace __stp_tf_map_lock rd/wr lock with " Santosh Shukla
2014-09-16 12:50 ` [SYSTEMTAP/PATCH v2 1/6] stp: rt: locking helper api 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
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 [this message]
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=5420292C.9050106@redhat.com \
--to=dsmith@redhat.com \
--cc=jistone@redhat.com \
--cc=sshukla@mvista.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).