All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	linux-omap@vger.kernel.org,
	Linus Walleij <linus.walleij@stericsson.com>
Subject: RE: [PATCH] ARM: smp: Introduce ARCH_HAS_COMMON_CORES_CLOCK to speed-up boot
Date: Thu, 20 Jan 2011 21:06:35 +0530	[thread overview]
Message-ID: <43c027bd53818ab19bdc1c823aa21ea4@mail.gmail.com> (raw)
In-Reply-To: <4D385155.4050301@gmail.com>

> -----Original Message-----
> From: Rob Herring [mailto:robherring2@gmail.com]
> Sent: Thursday, January 20, 2011 8:44 PM
> To: Santosh Shilimkar
> Cc: linux-arm-kernel@lists.infradead.org; Russell King; linux-
> omap@vger.kernel.org; Linus Walleij
> Subject: Re: [PATCH] ARM: smp: Introduce ARCH_HAS_COMMON_CORES_CLOCK
> to speed-up boot
>
> On 01/20/2011 03:42 AM, Santosh Shilimkar wrote:
> > On some architectures, secondary cores shares clock with primiary
> > core and hence scale together. Hence secondary core lpj
> calibration
> > is not necessary and can be skipped to save considerable time.
> >
> > This can speed up the secondary cpu boot and hotplug cpu online
> > paths.
> >
> > Discussion thread:
> > 	http://www.spinics.net/lists/arm-kernel/msg111124.html
> >
>
> There's already one way to do this with pre-calculated lpj.
>
How about the hot-plug path? This is not for just boot.

> Also, this isn't multi-platform friendly. You could accomplish the
> same
> thing using the clock api to get the core frequency of each core and
> only calculate lpj if the frequency is different.
May be but what's wrong with the obvious approach which is
completely non-intrusive.
Why is not multi-platform friendly ?
Archs can choose not to select this option.

Regards,
Santosh

WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: smp: Introduce ARCH_HAS_COMMON_CORES_CLOCK to speed-up boot
Date: Thu, 20 Jan 2011 21:06:35 +0530	[thread overview]
Message-ID: <43c027bd53818ab19bdc1c823aa21ea4@mail.gmail.com> (raw)
In-Reply-To: <4D385155.4050301@gmail.com>

> -----Original Message-----
> From: Rob Herring [mailto:robherring2 at gmail.com]
> Sent: Thursday, January 20, 2011 8:44 PM
> To: Santosh Shilimkar
> Cc: linux-arm-kernel at lists.infradead.org; Russell King; linux-
> omap at vger.kernel.org; Linus Walleij
> Subject: Re: [PATCH] ARM: smp: Introduce ARCH_HAS_COMMON_CORES_CLOCK
> to speed-up boot
>
> On 01/20/2011 03:42 AM, Santosh Shilimkar wrote:
> > On some architectures, secondary cores shares clock with primiary
> > core and hence scale together. Hence secondary core lpj
> calibration
> > is not necessary and can be skipped to save considerable time.
> >
> > This can speed up the secondary cpu boot and hotplug cpu online
> > paths.
> >
> > Discussion thread:
> > 	http://www.spinics.net/lists/arm-kernel/msg111124.html
> >
>
> There's already one way to do this with pre-calculated lpj.
>
How about the hot-plug path? This is not for just boot.

> Also, this isn't multi-platform friendly. You could accomplish the
> same
> thing using the clock api to get the core frequency of each core and
> only calculate lpj if the frequency is different.
May be but what's wrong with the obvious approach which is
completely non-intrusive.
Why is not multi-platform friendly ?
Archs can choose not to select this option.

Regards,
Santosh

  reply	other threads:[~2011-01-20 15:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20  9:42 [PATCH] ARM: smp: Introduce ARCH_HAS_COMMON_CORES_CLOCK to speed-up boot Santosh Shilimkar
2011-01-20  9:42 ` Santosh Shilimkar
2011-01-20 15:14 ` Rob Herring
2011-01-20 15:14   ` Rob Herring
2011-01-20 15:36   ` Santosh Shilimkar [this message]
2011-01-20 15:36     ` Santosh Shilimkar
2011-01-20 16:34     ` Rob Herring
2011-01-20 16:34       ` Rob Herring
2011-01-21 13:43       ` Santosh Shilimkar
2011-01-21 13:43         ` Santosh Shilimkar
2011-01-21 14:23         ` Linus Walleij
2011-01-21 14:23           ` Linus Walleij
2011-01-21 15:00         ` Rob Herring
2011-01-21 15:00           ` Rob Herring
2011-01-21 17:15           ` Russell King - ARM Linux
2011-01-21 17:15             ` Russell King - ARM Linux
2011-01-22  7:44             ` [PATCH] ARM: smp: Introduce ARCH_HAS_COMMON_CORES_CLOCK tospeed-up boot Santosh Shilimkar
2011-01-22  7:44               ` Santosh Shilimkar
2011-01-22 21:20               ` Russell King - ARM Linux
2011-01-22 21:20                 ` Russell King - ARM Linux
2011-01-23  7:25                 ` [PATCH] ARM: smp: Introduce ARCH_HAS_COMMON_CORES_CLOCKtospeed-up boot Santosh Shilimkar
2011-01-23  7:25                   ` Santosh Shilimkar
2011-01-21 17:08         ` [PATCH] ARM: smp: Introduce ARCH_HAS_COMMON_CORES_CLOCK to speed-up boot Russell King - ARM Linux
2011-01-21 17:08           ` Russell King - ARM Linux
2011-01-20 16:21   ` Linus Walleij
2011-01-20 16:21     ` Linus Walleij

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=43c027bd53818ab19bdc1c823aa21ea4@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=robherring2@gmail.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.