From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: xenomai@lists.linux.dev, jan.kiszka@siemens.com
Subject: Re: [PATCH 13/13] y2038: testsuite/smokey/y2038: Adding tests for timerfd_gettime
Date: Mon, 08 May 2023 13:45:13 +0200 [thread overview]
Message-ID: <862cebd40855873341eb4ec40e81f2bc83284e36.camel@siemens.com> (raw)
In-Reply-To: <20230508125007.52fc2dae@wsk>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
On Mon, 2023-05-08 at 12:50 +0200, Lukasz Majewski wrote:
> Hi Florian,
>
> > Extending the smokey testsuite to do some tests for the recently added
> > timerfd_gettime syscall.
> >
>
> For better Y2038 compliance coverage one can use OE/Yocto ptest from
> glibc:
>
> https://git.yoctoproject.org/poky/plain/meta/recipes-core/glibc/glibc/run-ptest
> https://lore.kernel.org/all/YXm9s2mVGNI+NtzR@piout.net/T/##
Hi Lukasz,
I know your glibc testing stuff but it's not re-usable for Xenomai as
is right now. One reason is that the necessary glibc wrappers have not
been merged into Xenomai yet. That is one of the things still waiting
in my y2038 queue (see cover letter). I hope to get that merged within
next weeks.
We can reconsider when the remaining stuff has been integrated.
The purpose of the y2038 smokey tests is to test the lowest level of
kernel service entry points and proper routing within Xenomai. That's
likely not what the glibc test would provide. Integration of such tests
would likely happen within xenomai-images project and not within
Xenomai itself. (IMHO ;-))
Thanks for the heads up, again.
Best regards,
Florian
>
> > Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
> > ---
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 525 bytes --]
next prev parent reply other threads:[~2023-05-08 11:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 8:13 [PATCH 00/13] y2038: Part two - timer and timerfd support Florian Bezdeka
2023-05-08 8:13 ` [PATCH 01/13] y2038: cobalt: Introduce some itimerspec64 related helpers Florian Bezdeka
2023-05-12 15:59 ` Jan Kiszka
2023-05-15 9:31 ` Florian Bezdeka
2023-05-15 9:36 ` Jan Kiszka
2023-05-08 8:13 ` [PATCH 02/13] y2038: cobalt/posix/timer: Adding timer_settime64 Florian Bezdeka
2023-05-12 16:02 ` Jan Kiszka
2023-05-15 9:33 ` Florian Bezdeka
2023-05-08 8:13 ` [PATCH 03/13] y2038: lib/cobalt: Dispatch timer_settime Florian Bezdeka
2023-05-08 8:13 ` [PATCH 04/13] y2038: testsuite/smokey/y2038: Adding tests for timer_settime Florian Bezdeka
2023-05-08 8:13 ` [PATCH 05/13] y2038: cobalt/posix/timer: Adding timer_gettime64 Florian Bezdeka
2023-05-08 8:13 ` [PATCH 06/13] y2038: lib/cobalt: Dispatch timer_gettime Florian Bezdeka
2023-05-08 8:13 ` [PATCH 07/13] y2038: testsuite/smokey/y2038: Adding tests for timer_gettime Florian Bezdeka
2023-05-08 8:13 ` [PATCH 08/13] y2038: cobalt/posix/timerfd: Adding timerfd_settime64 Florian Bezdeka
2023-05-08 8:13 ` [PATCH 09/13] y2038: lib/cobalt: Dispatch timerfd_settime Florian Bezdeka
2023-05-08 8:13 ` [PATCH 10/13] y2038: testsuite/smokey/y2038: Adding tests for timerfd_settime Florian Bezdeka
2023-05-08 8:13 ` [PATCH 11/13] y2038: cobalt/posix/timerfd: Adding timerfd_gettime64 Florian Bezdeka
2023-05-08 8:13 ` [PATCH 12/13] y2038: lib/cobalt: Dispatch timerfd_gettime Florian Bezdeka
2023-05-08 8:13 ` [PATCH 13/13] y2038: testsuite/smokey/y2038: Adding tests for timerfd_gettime Florian Bezdeka
2023-05-08 10:50 ` Lukasz Majewski
2023-05-08 11:45 ` Florian Bezdeka [this message]
2023-05-12 16:09 ` [PATCH 00/13] y2038: Part two - timer and timerfd support Jan Kiszka
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=862cebd40855873341eb4ec40e81f2bc83284e36.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=lukma@denx.de \
--cc=xenomai@lists.linux.dev \
/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 NNTP newsgroup(s).