From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe001.messaging.microsoft.com [216.32.181.181]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.global.frontbridge.com", Issuer "MSIT Machine Auth CA 2" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 06C1D2C0099 for ; Sat, 24 Aug 2013 01:31:34 +1000 (EST) Message-ID: <1377271865.20722.44.camel@snotra.buserror.net> Subject: Re: [PATCH 1/2] powerpc/85xx: add hardware automatically enter altivec idle state From: Scott Wood To: Wang Dongsheng-B40534 Date: Fri, 23 Aug 2013 10:31:05 -0500 In-Reply-To: References: <1376637789-27330-1-git-send-email-dongsheng.wang@freescale.com> <83499AB5-DCE7-407D-AEC1-B2493D1D38BE@kernel.crashing.org> <1376671853.31636.252.camel@snotra.buserror.net> <1376959116.31636.392.camel@snotra.buserror.net> <1377184761.5029.96.camel@snotra.buserror.net> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Cc: Wood Scott-B07421 , "linuxppc-dev@lists.ozlabs.org" , Zhao Chenhui-B35336 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2013-08-22 at 21:52 -0500, Wang Dongsheng-B40534 wrote: > > > -----Original Message----- > > From: Wood Scott-B07421 > > Sent: Thursday, August 22, 2013 11:19 PM > > To: Wang Dongsheng-B40534 > > Cc: Wood Scott-B07421; Kumar Gala; Zhao Chenhui-B35336; linuxppc- > > dev@lists.ozlabs.org > > Subject: Re: [PATCH 1/2] powerpc/85xx: add hardware automatically enter > > altivec idle state > > > > On Wed, 2013-08-21 at 22:13 -0500, Wang Dongsheng-B40534 wrote: > > > > > > > -----Original Message----- > > > > From: Wood Scott-B07421 > > > > Sent: Tuesday, August 20, 2013 8:39 AM > > > > To: Wang Dongsheng-B40534 > > > > Cc: Wood Scott-B07421; Kumar Gala; linuxppc-dev@lists.ozlabs.org > > > > Subject: Re: [PATCH 1/2] powerpc/85xx: add hardware automatically > > > > enter altivec idle state > > > > > > > > It just seems wrong to have an ad-hoc mechanism for running > > > > core-specific code when we have cputable... If we really need this, > > > > maybe we should add a "cpu_setup_late" function pointer. > > > > > > > > With your patch, when does the power management register get set > > > > when hot plugging a cpu? > > > > > > > Um.. I don't deal with this situation. I will fix it. > > > __setup/restore_cpu_e6500 looks good. But only bootcpu call > > __setup_cpu_e6500, not on each cpu. > > > I think this is a bug. > > > > Other CPUs call __restore_cpu_e6500. > > > No, there is bootcore of secondary thread, and other cores of first thread call __restore_cpu_e6500. This is the upstream list -- there is no e6500 thread support yet. :-) But in the SDK I do see generic_secondary_common_init being called from generic_secondary_thread_init, which means __restore_cpu_e6500 will be called. -Scott