All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Allow CPU0 to be nohz full
Date: Thu, 4 Apr 2019 16:36:20 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1904041635190.1685@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190404120704.18479-1-npiggin@gmail.com>

On Thu, 4 Apr 2019, Nicholas Piggin wrote:

> I've been looking at ways to fix suspend breakage with CPU0 as a
> nohz CPU. I started looking at various things like allowing CPU0
> to take over do_timer again temporarily or allowing nohz full
> to be stopped at runtime (that is quite a significant change for
> little real benefit). The problem then was having the housekeeping
> CPU go offline.
> 
> So I decided to try just allowing the freeze to occur on non-zero
> CPU. This seems to be a lot simpler to get working, but I guess
> some archs won't be able to deal with this? Would it be okay to
> make it opt-in per arch?

It needs to be opt in. x86 will fall on its nose with that.

Now the real interesting question is WHY do we need that at all?

Thanks,

	tglx

  parent reply	other threads:[~2019-04-04 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 12:07 [PATCH 0/4] Allow CPU0 to be nohz full Nicholas Piggin
2019-04-04 12:07 ` [PATCH 1/4] sched/core: allow the remote scheduler tick to be started on CPU0 Nicholas Piggin
2019-04-04 12:07 ` [PATCH 2/4] kernel/cpu: Allow non-zero CPU to be primary for suspend / kexec freeze Nicholas Piggin
2019-04-04 12:07 ` [PATCH 3/4] kernel/sched/isolation: require a present CPU in housekeeping mask Nicholas Piggin
2019-04-04 12:07 ` [PATCH 4/4] nohz_full: Allow the boot CPU to be full nohz Nicholas Piggin
2019-04-04 14:36 ` Thomas Gleixner [this message]
2019-04-04 16:02   ` [PATCH 0/4] Allow CPU0 to be nohz full Nicholas Piggin
2019-04-05 17:54     ` Thomas Gleixner
2019-04-09  9:21       ` Nicholas Piggin
2019-04-11 15:42         ` Paul E. McKenney
2019-04-12  3:16           ` Nicholas Piggin
2019-04-12 11:30             ` Paul E. McKenney

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=alpine.DEB.2.21.1904041635190.1685@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.org \
    --cc=rafael.j.wysocki@intel.com \
    /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.