From: Christoph Hellwig <hch@infradead.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (9/9): no timer interrupts in idle.
Date: Wed, 21 Apr 2004 17:32:33 +0100 [thread overview]
Message-ID: <20040421173233.A8176@infradead.org> (raw)
In-Reply-To: <OF5F328943.611CF55B-ONC1256E7D.005A1D57-C1256E7D.005ABDDC@de.ibm.com>; from schwidefsky@de.ibm.com on Wed, Apr 21, 2004 at 06:31:08PM +0200
On Wed, Apr 21, 2004 at 06:31:08PM +0200, Martin Schwidefsky wrote:
> > This is a bit ugly. What about inlining the CONFIG_NO_IDLE_HZ case
> > of this function in it's only caller and define idle_cpu_mask to
> > an empty cpu mask for all other arches?
>
> This would mean that all other arches need to do the above three
> statements in rcu_start_batch. If this is acceptable we certainly
> can introduce a global idle_cpu_mask. Where? sched.c?
My hope was gcc would actually optimize it away if it was a CPP constant
instead of a variable.
next prev parent reply other threads:[~2004-04-21 16:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 16:31 [PATCH] s390 (9/9): no timer interrupts in idle Martin Schwidefsky
2004-04-21 16:32 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 8:24 Martin Schwidefsky
2004-04-29 12:06 ` Dipankar Sarma
2004-04-29 7:43 Martin Schwidefsky
2004-04-29 8:16 ` Dipankar Sarma
2004-04-23 8:48 Martin Schwidefsky
2004-04-22 14:56 Martin Schwidefsky
2004-04-28 19:07 ` Dipankar Sarma
2004-04-22 12:44 Martin Schwidefsky
2004-04-22 13:11 ` Arjan van de Ven
2004-04-23 3:32 ` George Anzinger
2004-04-22 12:14 Martin Schwidefsky
2004-04-22 12:25 ` Arjan van de Ven
2004-04-22 11:09 Martin Schwidefsky
2004-04-22 11:14 ` Arjan van de Ven
2004-04-22 10:53 Martin Schwidefsky
2004-04-22 10:56 ` Arjan van de Ven
2004-04-22 8:55 Martin Schwidefsky
2004-04-22 8:48 Martin Schwidefsky
2004-04-22 8:52 ` Arjan van de Ven
[not found] <1Nt5d-84u-3@gated-at.bofh.it>
[not found] ` <1NwPD-2RW-37@gated-at.bofh.it>
[not found] ` <1NwPE-2RW-39@gated-at.bofh.it>
[not found] ` <1Nx8Y-3ev-15@gated-at.bofh.it>
2004-04-21 22:38 ` Andi Kleen
2004-04-21 18:52 Martin Schwidefsky
2004-04-21 21:58 ` Dipankar Sarma
2004-04-21 16:37 Martin Schwidefsky
2004-04-21 20:43 ` Dipankar Sarma
2004-04-21 20:46 ` Christoph Hellwig
2004-04-21 21:01 ` Dipankar Sarma
2004-04-21 14:49 Martin Schwidefsky
2004-04-21 15:31 ` Christoph Hellwig
2004-04-22 8:02 ` Arjan van de Ven
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=20040421173233.A8176@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox