All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Frederic Weisbecker <frederic@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Tony Luck <tony.luck@intel.com>,
	"David S . Miller" <davem@davemloft.net>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Helge Deller <deller@gmx.de>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, Fenghua Yu <fenghua.yu@intel.com>,
	"James E . J . Bottomley" <jejb@parisc-linux.org>,
	heiko.carstens@de.ibm.com
Subject: Re: [PATCH 10/10] softirq: Remove __ARCH_SET_SOFTIRQ_PENDING
Date: Thu, 29 Mar 2018 20:08:36 +0200	[thread overview]
Message-ID: <20180329180836.GS4082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180329165343.39f4486f@mschwideX1>

On Thu, Mar 29, 2018 at 04:53:43PM +0200, Martin Schwidefsky wrote:
> The lowcore optimization for softirq_pending field is not really needed,
> just nice to have. But if there is a strong reason to make a common
> definition for it we can certainly do that.

A slightly related question; would it make sense to move all kernel
static per-cpu stuff into lowcore, or is that asking for too much
trickery?

  parent reply	other threads:[~2018-03-29 18:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  2:26 [PATCH 00/10] softirq: Consolidate and optimize softirq mask Frederic Weisbecker
2018-03-29  2:26 ` [PATCH 01/10] ia64: Convert local_softirq_pending() to per-cpu ops Frederic Weisbecker
2018-03-29  2:26 ` [PATCH 02/10] sparc: Convert local_softirq_pending() to use per-cpu op Frederic Weisbecker
2018-03-29  2:26 ` [PATCH 03/10] softirq: Turn default irq_cpustat_t to standard per-cpu Frederic Weisbecker
2018-03-29  2:26 ` [PATCH 04/10] softirq: Consolidate default local_softirq_pending() implementations Frederic Weisbecker
2018-03-29  2:27 ` [PATCH 05/10] ia64: Switch to generic local_softirq_pending() implementation Frederic Weisbecker
2018-03-29  2:27 ` [PATCH 06/10] parisc: " Frederic Weisbecker
2018-03-29  2:27 ` [PATCH 07/10] powerpc: " Frederic Weisbecker
2018-03-29  2:27 ` [PATCH 08/10] sparc: " Frederic Weisbecker
2018-03-29  2:27 ` [PATCH 09/10] x86: " Frederic Weisbecker
2018-03-29  2:27 ` [PATCH 10/10] softirq: Remove __ARCH_SET_SOFTIRQ_PENDING Frederic Weisbecker
2018-03-29  7:16   ` Peter Zijlstra
2018-03-29 13:47     ` Frederic Weisbecker
2018-03-29 14:01       ` Peter Zijlstra
2018-03-29 14:07         ` Frederic Weisbecker
2018-03-29 14:53           ` Martin Schwidefsky
2018-03-29 16:55             ` Frederic Weisbecker
2018-03-29 18:08             ` Peter Zijlstra [this message]
2018-04-03  5:52               ` Martin Schwidefsky
2018-04-03  8:42                 ` Peter Zijlstra

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=20180329180836.GS4082@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=benh@kernel.crashing.org \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=fenghua.yu@intel.com \
    --cc=frederic@kernel.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jejb@parisc-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@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.