From: Oleg Nesterov <oleg@redhat.com>
To: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, a.p.zijlstra@chello.nl,
ego@in.ibm.com, tglx@linutronix.de, mingo@elte.hu,
andi@firstfloor.org, venkatesh.pallipadi@intel.com,
vatsa@linux.vnet.ibm.com, arjan@infradead.org,
svaidy@linux.vnet.ibm.com
Subject: Re: [v2 PATCH 1/4] timers: framework to identify pinned timers.
Date: Thu, 5 Mar 2009 17:53:40 +0100 [thread overview]
Message-ID: <20090305165340.GA6984@redhat.com> (raw)
In-Reply-To: <20090304121456.GB9855@linux.vnet.ibm.com>
On 03/04, Arun R Bharadwaj wrote:
>
> +static inline unsigned long tbase_get_flag_bits(struct timer_list *timer)
> +{
> + return tbase_get_deferrable(timer->base) |
> + tbase_get_pinned(timer->base);
> +}
I'd say this looks a bit strange. Hopefully compiler can optimize this code
to return (unsigned long)base & (TBASE_DEFERRABLE_FLAG | TBASE_PINNED_FLAG).
> @@ -736,6 +759,7 @@ void add_timer_on(struct timer_list *tim
> struct tvec_base *base = per_cpu(tvec_bases, cpu);
> unsigned long flags;
>
> + timer_set_pinned(timer);
But we never clear TBASE_PINNED_FLAG?
If we use mod_timer() next time, the timer remains "pinned". I do not say
this is really wrong, but a bit strange imho.
Oleg.
next prev parent reply other threads:[~2009-03-05 16:57 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 12:12 [v2 PATCH 0/4] timers: framework for migration between CPU Arun R Bharadwaj
2009-03-04 12:14 ` [v2 PATCH 1/4] timers: framework to identify pinned timers Arun R Bharadwaj
2009-03-05 16:53 ` Oleg Nesterov
2009-03-05 16:53 ` Oleg Nesterov [this message]
2009-03-06 6:14 ` Arun R Bharadwaj
2009-03-06 15:03 ` Oleg Nesterov
2009-03-06 15:03 ` Oleg Nesterov
2009-03-06 6:14 ` Arun R Bharadwaj
2009-03-06 7:01 ` Arun R Bharadwaj
2009-03-06 7:01 ` Arun R Bharadwaj
2009-03-04 12:14 ` Arun R Bharadwaj
2009-03-04 12:16 ` [v2 PATCH 2/4] timers: identifying the existing pinned hrtimers Arun R Bharadwaj
2009-03-04 12:16 ` Arun R Bharadwaj
2009-03-04 12:18 ` [v2 PATCH 3/4] timers: sysfs hook to enable timer migration Arun R Bharadwaj
2009-03-04 12:18 ` Arun R Bharadwaj
2009-03-04 12:19 ` [v2 PATCH 4/4] timers: logic " Arun R Bharadwaj
2009-03-04 12:19 ` Arun R Bharadwaj
2009-03-04 16:33 ` Daniel Walker
2009-03-04 16:52 ` Arun R Bharadwaj
2009-03-04 16:52 ` Arun R Bharadwaj
2009-03-04 16:33 ` Daniel Walker
2009-03-05 15:34 ` Oleg Nesterov
2009-03-05 15:34 ` Oleg Nesterov
2009-03-05 16:23 ` Oleg Nesterov
2009-03-06 3:21 ` Gautham R Shenoy
2009-03-06 3:21 ` Gautham R Shenoy
2009-03-06 14:50 ` Oleg Nesterov
2009-03-06 14:50 ` Oleg Nesterov
2009-03-06 15:49 ` Gautham R Shenoy
2009-03-06 15:49 ` Gautham R Shenoy
2009-03-06 17:08 ` Oleg Nesterov
2009-03-06 17:26 ` Gautham R Shenoy
2009-03-06 17:26 ` Gautham R Shenoy
2009-03-06 17:08 ` Oleg Nesterov
2009-03-05 16:23 ` Oleg Nesterov
2009-03-04 17:33 ` [v2 PATCH 0/4] timers: framework for migration between CPU Ingo Molnar
2009-03-04 17:33 ` Ingo Molnar
2009-03-04 18:06 ` Vaidyanathan Srinivasan
2009-03-04 18:29 ` Ingo Molnar
2009-03-04 18:29 ` Ingo Molnar
2009-03-04 18:06 ` Vaidyanathan Srinivasan
2009-03-06 0:14 ` Arjan van de Ven
2009-03-06 4:23 ` Arun R Bharadwaj
2009-03-06 4:23 ` Arun R Bharadwaj
2009-03-06 0:14 ` 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=20090305165340.GA6984@redhat.com \
--to=oleg@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=arun@linux.vnet.ibm.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vatsa@linux.vnet.ibm.com \
--cc=venkatesh.pallipadi@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.