All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Gary Robertson <gary.robertson@linaro.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: GeHao Kang <kanghao0928@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	jason.low2@hp.com, RT <linux-rt-users@vger.kernel.org>
Subject: Re: PREEMPT_RT with Full Tickless
Date: Sun, 13 Dec 2015 05:19:50 +0100	[thread overview]
Message-ID: <1449980390.3271.9.camel@gmail.com> (raw)
In-Reply-To: <CAF7YWnzyxECC=iKhVHoJXQrb_QH8pqvcm0LC9Fq43NviuSM=hg@mail.gmail.com>

On Sat, 2015-12-12 at 14:11 -0600, Gary Robertson wrote:
> On Fri, Dec 11, 2015 at 11:50 AM, Sebastian Andrzej Siewior
> <bigeasy@linutronix.de> wrote:
> > * Mike Galbraith | 2015-12-11 15:36:17 [+0100]:
> > 
> > > On Fri, 2015-12-11 at 19:29 +0800, GeHao Kang wrote:
> > > > When I enable CONFIG_PREEMPT_RT_FULL and CONFIG_NO_HZ_FULL
> > > > in Linux Kernel v4.1.12-rt12, I find the tick on the nohz_full
> > > > cpu
> > > > never stops.
> > > 
> 
> 
> Also - since in RT the tick timer interrupt results in a schedulable
> thread running to handle the software interrupt work stimulated by
> the
> tick - upon exit from the interrupt handler there are always at least
> 2 runnable threads in the CPU running the tick if there was a
> runnable
> task interrupted by the tick event.

Yup, handling that was one of the hacks that was dropped.  If you look
at what all was dropped in one 'let's con NOHZ_FULL into working'
patch, you'd think twice about submitting it for review.

	-Mike


      reply	other threads:[~2015-12-13  4:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 11:29 PREEMPT_RT with Full Tickless GeHao Kang
2015-12-11 14:36 ` Mike Galbraith
2015-12-11 17:50   ` Sebastian Andrzej Siewior
2015-12-12 20:11     ` Gary Robertson
2015-12-13  4:19       ` Mike Galbraith [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1449980390.3271.9.camel@gmail.com \
    --to=umgwanakikbuti@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=gary.robertson@linaro.org \
    --cc=jason.low2@hp.com \
    --cc=kanghao0928@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.