On Sun, Nov 18, 2018 at 11:39 PM Jan Kiszka <jan.kis...@siemens.com> wrote:
> On 19.11.18 07:38, C Smith via Xenomai wrote: > > I am porting an old Linux kernelspace driver to Xenomai 2.6.5 using RTDM > > API. > > I see calls to spinlock_irq_save() and spin_unlock_irqrestore() in the > old > > kernel driver code, right in the middle of an interrupt handler. > > > > Are those spinlock calls 'wrapped' by Xenomai 2.6.5 such that they work, > > and execute in Primary mode? Is calling these a bad thing to do in the > > middle of an RTDM interrupt, will it try to switch to Secondary mode ? > > > > Neither the obsolete 2.6 (don't use it anymore!) nor current Xenomai 3 can > perform any magic here. If your driver's IRQ routine shall run in primary > mode, > you need to migrate it explicitly to the RTDM API. > > OK, that's what I suspected. Yes my interrupts must be Primary mode (hard RT), so should I use rtdm_lock_irqsave () and rtdm_lock_irqrestore () as a substitute? Also, the old kernel driver used writel(), is that magically wrapped so it would just become a Xenomai Primary mode call ? We will port to Xenomai 3 in the coming year. In the meantime there are tens of thousands of lines of code to so I must maintain our 2.6.5 code for now. Please don't abandon discussions of 2.6, it's the stable and debugged pinnacle of your excellent work, after all. thanks, -C Smith Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux >
