From: Steven Rostedt <rostedt@goodmis.org>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Daniel Wagner <wagi@monom.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] sched/rt: Do not pull from current CPU if only one cpu to pull
Date: Mon, 4 Dec 2017 03:09:16 -0500 [thread overview]
Message-ID: <20171204030916.0cf09b0f@vmware.local.home> (raw)
In-Reply-To: <20171204074517.GA26712@localhost.localdomain>
On Mon, 4 Dec 2017 08:45:17 +0100
Juri Lelli <juri.lelli@redhat.com> wrote:
> Right. I was wondering however if for the truly UP case we shouldn't be
> initiating/queueing callbacks (pull/push) at all?
If !CONFIG_SMP then it's not compiled in. The issue came up when Daniel
ran a CONFIG_SMP kernel on an arch that only supports UP.
>
> DEADLINE doesn't use (yet?) the PUSH_IPI, but we will need a similar
> patch to keep logics aligned.
Maybe.
-- Steve
next prev parent reply other threads:[~2017-12-04 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 18:04 [PATCH] sched/rt: Do not pull from current CPU if only one cpu to pull Steven Rostedt
2017-12-04 7:45 ` Juri Lelli
2017-12-04 8:09 ` Steven Rostedt [this message]
2017-12-04 9:07 ` Juri Lelli
2017-12-04 9:55 ` Steven Rostedt
2017-12-04 10:29 ` Daniel Wagner
2017-12-11 16:47 ` Ingo Molnar
2017-12-11 19:34 ` Steven Rostedt
2017-12-12 10:56 ` [tip:sched/urgent] " tip-bot for Steven Rostedt
2017-12-15 15:39 ` [tip:sched/urgent] sched/rt: Do not pull from current CPU if only one CPU " tip-bot for Steven Rostedt
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=20171204030916.0cf09b0f@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
/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.