Re: PIC32 build fail

2021-01-30 Thread Brennan Ashton
If we can get build secret by infra set we can probably just make a pipeline that we can trigger to build and upload the CI toolchain to a blob store like S3. I can file a ticket. On Fri, Jan 29, 2021, 9:30 PM Xiang Xiao wrote: > How about we generate the toolchain binary and publish it on some

RE: timerfd

2021-01-30 Thread Xiang Xiao
timerfd is a very nice feature, but is it better to call wd_* api than timer_ api? > -Original Message- > From: Matias N. > Sent: Saturday, January 30, 2021 10:01 AM > To: dev@nuttx.apache.org > Subject: timerfd > > Hi, > > I would like to implement timerfd interface to overcome some o

Re: timerfd

2021-01-30 Thread Matias N.
But that isn't a userspace API, is it? It runs the handler in interrupt context. I also realize now that timerfd has a limitation: you will not know about the timer expiration while not yet doing poll, so it looses a bit on the real-time aspect. Best, Matias On Sat, Jan 30, 2021, at 09:41, Xian

Re: timerfd

2021-01-30 Thread Xiang Xiao
On Sat, Jan 30, 2021 at 7:00 AM Matias N. wrote: > But that isn't a userspace API, is it? It runs the handler in interrupt > context. > > The core logic for timerfd is part of the kernel(actually, timerfd/eventfd implements file_operation like a normal driver). libc timerfd api just a simple wrap

Re: timerfd

2021-01-30 Thread Matias N.
On Sat, Jan 30, 2021, at 12:26, Xiang Xiao wrote: > On Sat, Jan 30, 2021 at 7:00 AM Matias N. wrote: > > > But that isn't a userspace API, is it? It runs the handler in interrupt > > context. > > > > > The core logic for timerfd is part of the kernel(actually, timerfd/eventfd > implements file_op

Re: limitation in SIGEV_THREAD?

2021-01-30 Thread Matias N.
I'm thinking again about this. Why wouldn't it be possible to make functions using SIGEV_THREAD (such as timer_settime) create a pthread behind the scenes (only the first time a SIGEV_THREAD is setup)? The underlying watchdog would go to a handler that posts a semaphore/condition variable that the

Re: limitation in SIGEV_THREAD?

2021-01-30 Thread Gregory Nutt
I'm thinking again about this. Why wouldn't it be possible to make functions using SIGEV_THREAD (such as timer_settime) create a pthread behind the scenes (only the first time a SIGEV_THREAD is setup)? The underlying watchdog would go to a handler that posts a semaphore/condition variable that the

Re: limitation in SIGEV_THREAD?

2021-01-30 Thread Brennan Ashton
On Sat, Jan 30, 2021, 1:58 PM Gregory Nutt wrote: > > I'm thinking again about this. Why wouldn't it be possible to make > functions > > using SIGEV_THREAD (such as timer_settime) create a pthread behind > > the scenes (only the first time a SIGEV_THREAD is setup)? The underlying > > watchdog wou

Re: limitation in SIGEV_THREAD?

2021-01-30 Thread Matias N.
> This is actually fairly in line with how the Musl libc implements this (at > least from a quick look). There are a few important details in there, but > it looks quite clean. > > http://git.musl-libc.org/cgit/musl/tree/src/time/timer_create.c > > While Musl is usually not as fast as glibc, I

Re: limitation in SIGEV_THREAD?

2021-01-30 Thread Brennan Ashton
On Sat, Jan 30, 2021 at 6:11 PM Matias N. wrote: > > > > This is actually fairly in line with how the Musl libc implements this (at > > least from a quick look). There are a few important details in there, but > > it looks quite clean. > > > > http://git.musl-libc.org/cgit/musl/tree/src/time/time