Date: Mon, 13 Apr 2015 11:06:40 -0400
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
        Frederic Weisbecker <fweisbec@gmail.com>, linux-kernel@vger.kernel.org,
        Rik van Riel <riel@redhat.com>
Subject: Re: kernel/timer: avoid spurious ksoftirqd wakeups (v2)
Message-ID: <20150413110640.40f137c4@redhat.com>
In-Reply-To: <alpine.DEB.2.11.1504111124020.3845@nanos>
References: <20150406231557.GA5094@amt.cnet>
	<alpine.DEB.2.11.1504072200210.3845@nanos>
	<20150407221244.GB6143@lerouge>
	<20150410180907.GA13199@amt.cnet>
	<20150410213037.0ead22a3@redhat.com>
	<alpine.DEB.2.11.1504111124020.3845@nanos>
Organization: Red Hat
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 863
Lines: 27

On Sat, 11 Apr 2015 11:25:49 +0200 (CEST)
Thomas Gleixner <tglx@linutronix.de> wrote:

> On Fri, 10 Apr 2015, Luiz Capitulino wrote:
> > On Fri, 10 Apr 2015 15:09:07 -0300
> > > It seems a valid solution for this interrupt is to program 
> > > sched_timer to the nearest future possible. 
> > 
> > What about calling the timer function right there, like
> > hrtimer_interrupt() does?
> 
> No, you cannot call the timer function from the enqueue path. The
> caller might hold a lock which is taken in the callback as well.....

Fair enough. We're going to think about a different solution.

> 
> Thanks,
> 
> 	tglx
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/