From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH V3] syscalls/timer_settime01: Make sure the timer fires
Date: Fri, 24 Jul 2020 15:29:13 +0200 [thread overview]
Message-ID: <20200724132913.GH9768@yuki.lan> (raw)
In-Reply-To: <f9289166-5698-e2ec-ecc8-531fbcbd60c5@cn.fujitsu.com>
Hi!
> >> When tesing timer_settime01 on 3.10.0-1136.el7.x86_64, this case fails
> >> whether we use any type clock.
> >>
> >> timer_settime01.c:174: PASS: timer_settime(CLOCK_BOOTTIME) passed
> >> timer_settime01.c:164: FAIL: timer_gettime(CLOCK_BOOTTIME_ALARM) reported
> >> bad values (0: 678013000): SUCCESS (0)
> >> timer_settime01.c:174: PASS: timer_settime(CLOCK_BOOTTIME_ALARM) passed
> >> timer_settime01.c:164: FAIL: timer_gettime(CLOCK_REALTIME_ALARM) reported
> >> bad values (0: 358240000): SUCCESS (0)
> >> timer_settime01.c:174: PASS: timer_settime(CLOCK_REALTIME_ALARM) passed
> >> timer_settime01.c:174: PASS: timer_settime(CLOCK_TAI) passed
> >
> > Can you share the complete test log? I am not sure if only the _ALARM
> > cocks are failing or all. You are getting values in the order of
> > 300-700 ms, while the max value can't be greater than 50 ms. So seems
> > like a kernel issue to me. Over that, both _ALARM type clocks weren't
> > supported before 3.11 and looks like your kernel version is 3.10.
> Yes, only _ALARM fails. I only find a kernel patch (commit
> 11ffa9d6065f344 timerfd: Add alarm timers) introduced alarm clock types
> for timefd in kernel 3.11 and a kernel patch (commit 9a7adcf5c6dea63d
> timers: Posix interface for alarm-timers) in kernel 3.1. It seems my
> kernel version has supported this two alarm clock, but not sure why this
> case fails.
This is on RHEL kernel that has backported the _ALARM support right? So
this may as well be case of badly bacported patch...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-07-24 13:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 11:43 [LTP] [PATCH 1/2] syscalls/timer_settime01: Improve print messages Viresh Kumar
2020-06-29 11:43 ` [LTP] [PATCH 2/2] syscalls/timer_settime01: Make sure the timer fires Viresh Kumar
2020-06-29 12:05 ` Arnd Bergmann
2020-06-29 12:13 ` Cyril Hrubis
2020-06-30 2:27 ` Viresh Kumar
2020-06-30 2:36 ` [LTP] [PATCH V1.1 " Viresh Kumar
2020-07-02 13:34 ` [LTP] [PATCH 1/2] syscalls/timer_settime01: Improve print messages Cyril Hrubis
2020-07-03 2:22 ` Viresh Kumar
2020-07-03 2:39 ` [LTP] [PATCH V2] syscalls/timer_settime01: Make sure the timer fires Viresh Kumar
2020-07-07 15:02 ` Cyril Hrubis
2020-07-08 10:31 ` [LTP] [PATCH V3] " Viresh Kumar
2020-07-14 14:28 ` Cyril Hrubis
2020-07-15 2:36 ` Viresh Kumar
2020-07-15 8:53 ` Cyril Hrubis
2020-07-23 2:39 ` Yang Xu
2020-07-24 3:37 ` Viresh Kumar
2020-07-24 5:07 ` Yang Xu
2020-07-24 10:18 ` Viresh Kumar
2020-07-24 10:27 ` Yang Xu
2020-07-24 13:29 ` Cyril Hrubis [this message]
2020-07-24 15:01 ` Yang Xu
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=20200724132913.GH9768@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.