From: Yong Zhang <yong.zhang0@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Dmitry Antipov <dmitry.antipov@linaro.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@redhat.com>,
Venki Pallipadi <venki@google.com>,
linaro-dev@lists.linaro.org, patches@linaro.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] sched: generalize CONFIG_IRQ_TIME_ACCOUNTING for X86 and ARM
Date: Thu, 9 Feb 2012 10:51:03 +0800 [thread overview]
Message-ID: <20120209025103.GC26152@zhy> (raw)
In-Reply-To: <20120208131833.GK889@n2100.arm.linux.org.uk>
On Wed, Feb 08, 2012 at 01:18:33PM +0000, Russell King - ARM Linux wrote:
> On Wed, Feb 08, 2012 at 04:48:34AM -0800, Dmitry Antipov wrote:
> > Generalize CONFIG_IRQ_TIME_ACCOUNTING between X86 and
> > ARM, move "noirqtime=" option to common debugging code.
> > For a bit of backward compatibility, "tsc=noirqtime"
> > is preserved, but issues a warning.
> >
> > Suggested-by: Venki Pallipadi <venki@google.com>
> > Signed-off-by: Dmitry Antipov <dmitry.antipov@linaro.org>
> > ---
> > arch/arm/kernel/sched_clock.c | 3 +++
> > arch/x86/Kconfig | 11 -----------
> > arch/x86/kernel/tsc.c | 7 ++++---
> > include/linux/sched.h | 2 ++
> > lib/Kconfig.debug | 12 ++++++++++++
> > lib/Makefile | 2 ++
> > lib/irqtime.c | 12 ++++++++++++
> > 7 files changed, 35 insertions(+), 14 deletions(-)
> > create mode 100644 lib/irqtime.c
> >
> > diff --git a/arch/arm/kernel/sched_clock.c b/arch/arm/kernel/sched_clock.c
> > index 5416c7c..56d2a9d 100644
> > --- a/arch/arm/kernel/sched_clock.c
> > +++ b/arch/arm/kernel/sched_clock.c
> > @@ -162,5 +162,8 @@ void __init sched_clock_postinit(void)
> > if (read_sched_clock == jiffy_sched_clock_read)
> > setup_sched_clock(jiffy_sched_clock_read, 32, HZ);
> >
> > + if (!no_sched_irq_time)
> > + enable_sched_clock_irqtime();
>
> Why are you placing this here? sched_clock is available from the point
> that it's registered, which should be before the first sched_clock()
> call.
>
> > +config IRQ_TIME_ACCOUNTING
> > + bool "Fine granularity task level IRQ time accounting"
> > + depends on (X86 || (ARM && HAVE_SCHED_CLOCK))
>
> Even though it's not bad here, please get out of the habbit of throwing
> unnecessary parens into the mix. It can make stuff more difficult to
> read and therefore confirm correctness. (I've spent many a time
> rewriting if() statements because of paren overuse.)
>
> This could have been written:
>
> depends on X86 || (ARM && HAVE_SCHED_CLOCK)
>
> However, ARM will always have HAVE_SCHED_CLOCK after the next merge window,
> so this can become a much simpler:
>
> depends on X86 || ARM
Maybe we can hand the depend-things to every ARCH, say let ARCH provides
HAVE_IRQ_TIME_ACCOUNTING. Thus we can make IRQ_TIME_ACCOUNTING
denpend on HAVE_IRQ_TIME_ACCOUNTING.
Thanks,
Yong
>
> Apart from these two points, the rest of the patch looks fine to me but
> the ultimate decision about its acceptability is up to other people.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Only stand for myself
next prev parent reply other threads:[~2012-02-09 2:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 12:48 [PATCH] sched: generalize CONFIG_IRQ_TIME_ACCOUNTING for X86 and ARM Dmitry Antipov
2012-02-08 13:18 ` Russell King - ARM Linux
2012-02-08 15:15 ` Dmitry Antipov
2012-02-08 15:24 ` Russell King - ARM Linux
2012-02-09 2:51 ` Yong Zhang [this message]
2012-02-09 2:48 ` Yong Zhang
-- strict thread matches above, loose matches on Subject: below --
2012-02-28 6:29 Dmitry Antipov
2012-02-20 6:04 Dmitry Antipov
2012-02-27 10:12 ` Peter Zijlstra
2012-02-28 6:19 ` Dmitry Antipov
2012-02-11 0:02 Dmitry Antipov
2012-02-17 11:22 ` Ingo Molnar
2012-02-09 17:25 Dmitry Antipov
2012-02-10 22:28 ` Venki Pallipadi
2012-02-08 23:58 Dmitry Antipov
2012-02-08 16:08 Dmitry Antipov
2012-02-08 22:50 ` Venki Pallipadi
2012-02-07 18:06 Dmitry Antipov
2012-02-07 22:56 ` Venki Pallipadi
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=20120209025103.GC26152@zhy \
--to=yong.zhang0@gmail.com \
--cc=dmitry.antipov@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=patches@linaro.org \
--cc=rusty@rustcorp.com.au \
--cc=venki@google.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).