On Thu, Jul 21, 2022 at 12:53 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> Hello Gedare and Joel,
>
> On 15.07.22 10:43, Sebastian Huber wrote:
> > The uniprocessor schedulers had some special case logic for the
> > PRIORITY_PSEUDO_ISR priority.  Tasks with a priority of
> PRIORITY_PSEUDO_ISR
> > were allowed to preempt a not preemptible task.  If other higher
> priority task
> > are made ready while a PRIORITY_PSEUDO_ISR task preempts a not
> preemptible
> > task, then the other tasks run before the not preemptible task.  This
> made the
> > RTEMS_NO_PREEMPT mode ineffective.
> >
> > Remove the PRIORITY_PSEUDO_ISR special case logic.  This simplifies the
> > uniprocessor schedulers.  Move the uniprocessor-specific scheduler
> support to
> > the new header file <rtems/score/scheduleruniimpl.h>.
> >
> > Close #2365.
>

I'm guessing that  PRIORITY_PSEUDO_ISR wasn't used outside RTEMS itself
and likely only historically for the Timer Server Thread. The protection
for that
thread was reworked as part of the SMP efforts. If it is used outside
RTEMS,
that would be a user facing breakage and should be documented.

If you think all the use cases of PRIORITY_PSEUDO_ISR are accounted for,
I'm ok with removing it.

>
> what is your opinion with respect to this change? It is the second last
> item on my score TODO list. The last item is:
>
> https://lists.rtems.org/pipermail/devel/2022-July/072534.html


I'll try to look at that today.

>
>
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.hu...@embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax:   +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to