From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] c/r tests: Add futex c/r tests
Date: Mon, 6 Jul 2009 18:11:11 -0500 [thread overview]
Message-ID: <20090706231111.GA2353@us.ibm.com> (raw)
In-Reply-To: <1246910097-30792-1-git-send-email-matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Quoting Matt Helsley (matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org):
> Add tests for plain, robust, and pi futexes. Each test sets up a
> typical contended futex scenario and then awaits checkpoint. We only test
> the contended case since the uncontended cases are entirely based on the
> state of userspace memory. After checkpoint each test verifies that the
> critical semantics of the futex still works.
Thanks, Matt, these now compile and run on s390.
> For plain futexes we ensure that the same number of tasks that
> were asleep on the futex are woken up.
But plain always returns 0 (success)?
> For robust futexes we set the robust list head of each process
> and wait for checkpoint. After checkpoint we verify that the kernel
> still knows about the robust list head then each child exits without
> releasing the futex. Since the child still holds the futex at exit the
> kernel wakes another waiting child.
run.sh doesn't check for the return value. (trivially fixed as bash
wait returns its return value)
I think you also have several places where you log a FAIL when you should
probably log BROK. But I've applied this to cr_tests plus a fix
for run.sh to check return values. Can you send me a fix to have plain.c
log failures (unless I'm misreading and its all fine)?
thanks,
-serge
prev parent reply other threads:[~2009-07-06 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 19:54 [PATCH] c/r tests: Add futex c/r tests Matt Helsley
[not found] ` <1246910097-30792-1-git-send-email-matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-06 23:11 ` Serge E. Hallyn [this message]
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=20090706231111.GA2353@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.