All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Zhao Chenhui <chenhui.zhao@freescale.com>
Cc: Matthew McClintock <msm@freescale.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/5] powerpc/85xx: implement hardware timebase sync
Date: Wed, 6 Jun 2012 13:26:16 -0500	[thread overview]
Message-ID: <4FCFA0C8.9090800@freescale.com> (raw)
In-Reply-To: <20120606093142.GA23505@localhost.localdomain>

On 06/06/2012 04:31 AM, Zhao Chenhui wrote:
> On Tue, Jun 05, 2012 at 11:07:41AM -0500, Scott Wood wrote:
>> On 06/05/2012 04:08 AM, Zhao Chenhui wrote:
>>> On Fri, Jun 01, 2012 at 10:40:00AM -0500, Scott Wood wrote:
>>>> I know you say this is for dual-core chips only, but it would be nice if
>>>> you'd write this in a way that doesn't assume that (even if the
>>>> corenet-specific timebase freezing comes later).
>>>
>>> At this point, I have not thought about how to implement the cornet-specific timebase freezing.
>>
>> I wasn't asking you to.  I was asking you to not have logic that breaks
>> with more than 2 CPUs.
> 
> These routines only called in the dual-core case. 

Come on, you know we have chips with more than two cores.  Why design
such a limitation into it, just because you're not personally interested
in supporting anything but e500v2?

Is it so hard to make it work for an arbitrary number of cores?

>>> If do not set them, it may make KEXEC fail on other platforms.
>>
>> What platforms?
> 
> Such as P4080, P3041, etc.

So we need to wait for corenet timebase sync before we stop causing
problems in virtualization, simulators, etc. if a kernel has kexec or
cpu hotplug enabled (whether used or not)?

Can you at least make sure we're actually in a kexec/hotplug scenario at
runtime?

Or just implement corenet timebase sync -- it's not that different.

-Scott

WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Zhao Chenhui <chenhui.zhao@freescale.com>
Cc: <linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
	<galak@kernel.crashing.org>, <leoli@freescale.com>,
	Matthew McClintock <msm@freescale.com>
Subject: Re: [PATCH v5 1/5] powerpc/85xx: implement hardware timebase sync
Date: Wed, 6 Jun 2012 13:26:16 -0500	[thread overview]
Message-ID: <4FCFA0C8.9090800@freescale.com> (raw)
In-Reply-To: <20120606093142.GA23505@localhost.localdomain>

On 06/06/2012 04:31 AM, Zhao Chenhui wrote:
> On Tue, Jun 05, 2012 at 11:07:41AM -0500, Scott Wood wrote:
>> On 06/05/2012 04:08 AM, Zhao Chenhui wrote:
>>> On Fri, Jun 01, 2012 at 10:40:00AM -0500, Scott Wood wrote:
>>>> I know you say this is for dual-core chips only, but it would be nice if
>>>> you'd write this in a way that doesn't assume that (even if the
>>>> corenet-specific timebase freezing comes later).
>>>
>>> At this point, I have not thought about how to implement the cornet-specific timebase freezing.
>>
>> I wasn't asking you to.  I was asking you to not have logic that breaks
>> with more than 2 CPUs.
> 
> These routines only called in the dual-core case. 

Come on, you know we have chips with more than two cores.  Why design
such a limitation into it, just because you're not personally interested
in supporting anything but e500v2?

Is it so hard to make it work for an arbitrary number of cores?

>>> If do not set them, it may make KEXEC fail on other platforms.
>>
>> What platforms?
> 
> Such as P4080, P3041, etc.

So we need to wait for corenet timebase sync before we stop causing
problems in virtualization, simulators, etc. if a kernel has kexec or
cpu hotplug enabled (whether used or not)?

Can you at least make sure we're actually in a kexec/hotplug scenario at
runtime?

Or just implement corenet timebase sync -- it's not that different.

-Scott


  reply	other threads:[~2012-06-06 18:27 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 11:53 [PATCH v5 1/5] powerpc/85xx: implement hardware timebase sync Zhao Chenhui
2012-05-11 11:53 ` Zhao Chenhui
2012-05-11 11:53 ` [PATCH v5 2/5] powerpc/85xx: add HOTPLUG_CPU support Zhao Chenhui
2012-05-11 11:53   ` Zhao Chenhui
2012-06-01 21:27   ` Scott Wood
2012-06-01 21:27     ` Scott Wood
2012-06-04 11:04     ` Zhao Chenhui
2012-06-04 11:04       ` Zhao Chenhui
2012-06-04 16:32       ` Scott Wood
2012-06-04 16:32         ` Scott Wood
2012-06-05 11:18         ` Zhao Chenhui
2012-06-05 11:18           ` Zhao Chenhui
2012-06-05 16:15           ` Scott Wood
2012-06-05 16:15             ` Scott Wood
2012-06-06  9:59             ` Zhao Chenhui
2012-06-06  9:59               ` Zhao Chenhui
2012-06-06 18:19               ` Scott Wood
2012-06-06 18:19                 ` Scott Wood
2012-05-11 11:53 ` [PATCH v5 3/5] powerpc/85xx: add sleep and deep sleep support Zhao Chenhui
2012-05-11 11:53   ` Zhao Chenhui
2012-06-01 21:54   ` Scott Wood
2012-06-01 21:54     ` Scott Wood
2012-06-04 11:12     ` Zhao Chenhui
2012-06-04 11:12       ` Zhao Chenhui
2012-06-04 22:58       ` Scott Wood
2012-06-04 22:58         ` Scott Wood
2012-06-05 11:35         ` Zhao Chenhui
2012-06-05 11:35           ` Zhao Chenhui
2012-06-05 16:13           ` Scott Wood
2012-06-05 16:13             ` Scott Wood
2012-05-11 11:53 ` [PATCH v5 4/5] fsl_pmc: Add API to enable device as wakeup event source Zhao Chenhui
2012-05-11 11:53   ` Zhao Chenhui
2012-06-01 22:08   ` Scott Wood
2012-06-01 22:08     ` Scott Wood
2012-06-04 11:36     ` Zhao Chenhui
2012-06-04 11:36       ` Zhao Chenhui
2012-06-04 23:02       ` Scott Wood
2012-06-04 23:02         ` Scott Wood
2012-06-05  4:08         ` Li Yang-R58472
2012-06-05  4:08           ` Li Yang-R58472
2012-06-05 16:11           ` Scott Wood
2012-06-05 16:11             ` Scott Wood
2012-06-05 16:49             ` Li Yang-R58472
2012-06-05 16:49               ` Li Yang-R58472
2012-06-05 18:05               ` Scott Wood
2012-06-05 18:05                 ` Scott Wood
2012-06-06  4:06                 ` Li Yang
2012-06-06  4:06                   ` Li Yang
2012-06-06 18:29                   ` Scott Wood
2012-06-06 18:29                     ` Scott Wood
2012-06-07  4:10                     ` Li Yang
2012-06-07  4:10                       ` Li Yang
2012-05-11 11:53 ` [PATCH v5 5/5] powerpc/85xx: add support to JOG feature using cpufreq interface Zhao Chenhui
2012-05-11 11:53   ` Zhao Chenhui
2012-06-01 23:30   ` Scott Wood
2012-06-01 23:30     ` Scott Wood
2012-06-05 10:59     ` Zhao Chenhui
2012-06-05 10:59       ` Zhao Chenhui
2012-06-05 15:58       ` Scott Wood
2012-06-05 15:58         ` Scott Wood
2012-06-06 10:19         ` Zhao Chenhui
2012-06-06 10:19           ` Zhao Chenhui
2012-05-29  7:30 ` [PATCH v5 1/5] powerpc/85xx: implement hardware timebase sync Li Yang
2012-05-29  7:30   ` Li Yang
2012-05-29 12:20 ` [linuxppc-release] " Zhao Chenhui-B35336
2012-06-01 15:40 ` Scott Wood
2012-06-01 15:40   ` Scott Wood
2012-06-05  9:08   ` Zhao Chenhui
2012-06-05  9:08     ` Zhao Chenhui
2012-06-05 16:07     ` Scott Wood
2012-06-05 16:07       ` Scott Wood
2012-06-06  9:31       ` Zhao Chenhui
2012-06-06  9:31         ` Zhao Chenhui
2012-06-06 18:26         ` Scott Wood [this message]
2012-06-06 18:26           ` Scott Wood
2012-06-07  4:07           ` Zhao Chenhui
2012-06-07  4:07             ` Zhao Chenhui

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=4FCFA0C8.9090800@freescale.com \
    --to=scottwood@freescale.com \
    --cc=chenhui.zhao@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msm@freescale.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.