From: Denis OSTERLAND-HEIM <denis.osterland@diehl.com>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re: [PATCH] pps: add epoll support
Date: Tue, 25 Feb 2025 17:34:04 +0100 (CET) [thread overview]
Message-ID: <11965b8b6101487996df902d35ba2ea3@diehl.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
Hi,
> -----Original Message-----
> From: Rodolfo Giometti <giometti@enneenne.com>
> Sent: Tuesday, February 25, 2025 3:24 PM
> To: Denis OSTERLAND-HEIM <denis.osterland@diehl.com>
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] pps: add epoll support
>
[snip]
>
> > If I start multiple user space programs data races are visible.
> >
> > ```
> > # for i in 0 1 2 3 4 5 6; do PpsPollTest /dev/pps1 > log$i & done
> > # sleep 6
> > # tail log*
> > ==> log0 <==
> > timeout
> > assert: 196
> > time: 1520599554.276752928
> > assert: 197
> > time: 1520599555.300692704
>
> This is the same behavior we have when working with a serial port: if more than
> one process gets access to it, data is stolen.
Okay, then lets choose your suggestion.
>
> >>From my point of view it would be great to fix this bug without such an limitation.
>
> I disagree, it is not a limitation! It is like a normal char device work.
>
> What we have to test now is if your initial goal has been addressed! That is, in
> an application that has more to do than just dealing with one PPS device, we can
> use poll()/select() in order to avoid using threads.
I will do the final test.
I expect that it works with your patch.
Shall I prepare the patch?
Shall I add you as Co-author?
Or do you want to send your patch with me in reported-by and tested-by?
Fixes: eae9d2ba0cfc ("LinuxPPS: core support")?
CC stable?
Regards, Denis
>
> Ciao,
>
> Rodolfo
>
> --
> GNU/Linux Solutions e-mail: giometti@enneenne.com
> Linux Device Driver giometti@linux.it
> Embedded Systems phone: +39 349 2432127
> UNIX programming
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6038 bytes --]
next reply other threads:[~2025-02-25 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 16:34 Denis OSTERLAND-HEIM [this message]
2025-02-26 7:36 ` [PATCH] pps: add epoll support Rodolfo Giometti
-- strict thread matches above, loose matches on Subject: below --
2025-02-25 13:39 Denis OSTERLAND-HEIM
2025-02-24 11:38 Denis OSTERLAND-HEIM
2025-02-24 17:38 ` Rodolfo Giometti
2025-02-25 12:47 ` Denis OSTERLAND-HEIM
2025-02-21 10:49 [EXT] " Denis OSTERLAND-HEIM
2025-02-21 11:39 ` Rodolfo Giometti
2025-02-21 11:54 ` Denis OSTERLAND-HEIM
2025-02-19 12:21 Denis OSTERLAND-HEIM
2025-02-20 8:50 ` Rodolfo Giometti
2025-02-20 16:45 ` Denis OSTERLAND-HEIM
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=11965b8b6101487996df902d35ba2ea3@diehl.com \
--to=denis.osterland@diehl.com \
--cc=giometti@enneenne.com \
--cc=linux-kernel@vger.kernel.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