lkml.org 
[lkml]   [2018]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC/PATCH RT] Revert "rt,ntp: Move call to schedule_delayed_work() to helper thread"
On Fri, 2 Mar 2018 12:26:03 +0100 (CET)
Thomas Gleixner <tglx@linutronix.de> wrote:

> On Fri, 2 Mar 2018, Sebastian Andrzej Siewior wrote:
>
> > I've been looking at this in v3.10-RT where it got in. The patch
> > description says
> >
> > |The ntp code for notify_cmos_timer() is called from a hard interrupt
> > |context.
> >
> > I see only one caller of ntp_notify_cmos_timer() and that is
> > do_adjtimex() after "raw_spin_unlock_irqrestore()".
> > I see a few callers of do_adjtimex() which is SYS_adjtimex() (+compat)
> > and posix_clock_realtime_adj() which in turn is called by
> > SYS_clock_adjtime().
> >
> > I can't find the hard interrupt context. May I revert this patch?
>
> That really looks bogus. ntp_notify_cmos_timer() has never been invoked
> from hard interrupt context or from a atomic region. No idea how that patch
> ended up in RT...
>

I'm looking into why I did that. Unless I ended up converting the wrong
function. The patch is from 2013, and I'm sure it was due to some bug
that was triggered with the Red Hat RT kernel. Unless the RH version had
a call somewhere to it.

I'll dig a little further because I'm curious to why I added that
patch, but in the mean time, by all means, revert it.

Thanks!

-- Steve

\
 
 \ /
  Last update: 2018-03-05 18:34    [W:0.051 / U:0.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site