Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754645AbbHNJAg (ORCPT ); Fri, 14 Aug 2015 05:00:36 -0400 Received: from e23smtp09.au.ibm.com ([202.81.31.142]:55741 "EHLO e23smtp09.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754008AbbHNJAd (ORCPT ); Fri, 14 Aug 2015 05:00:33 -0400 X-Helo: d23dlp01.au.ibm.com X-MailFrom: shreyas@linux.vnet.ibm.com X-RcptTo: linux-kernel@vger.kernel.org Message-ID: <55CDADF1.5050308@linux.vnet.ibm.com> Date: Fri, 14 Aug 2015 14:29:29 +0530 From: Shreyas B Prabhu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: "Gautham R. Shenoy" , Paul Mackerras , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Michael Ellerman CC: mikey@neuling.org, Segher Boessenkool , Madhavan Srinivasan Subject: Re: [PATCH v3] powerpc: Add an inline function to update POWER8 HID0 References: <20150805065400.GA14701@in.ibm.com> <1438758511-918-1-git-send-email-ego@linux.vnet.ibm.com> In-Reply-To: <1438758511-918-1-git-send-email-ego@linux.vnet.ibm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15081409-0033-0000-0000-000001F73EF9 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 738 Lines: 19 On 08/05/2015 12:38 PM, Gautham R. Shenoy wrote: > Section 3.7 of Version 1.2 of the Power8 Processor User's Manual > prescribes that updates to HID0 be preceded by a SYNC instruction and > followed by an ISYNC instruction (Page 91). > > Create an inline function name update_power8_hid0() which follows this > recipe and invoke it from the static split core path. > > Signed-off-by: Gautham R. Shenoy Reviewed-by: Shreyas B. Prabhu -- 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/