From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Paul E. McKenney" Date: Tue, 04 Oct 2016 07:06:23 +0000 Subject: Re: [PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver Message-Id: <20161004070623.GM14933@linux.vnet.ibm.com> List-Id: References: <22c1ee0f908fe3bf8b70f5e87d659ceb29af1434.1474693319.git.dalias@libc.org> <20160926210716.GA12855@brightrain.aerifal.cx> <4b02ba7d-4a31-297a-bbbd-be26da615e7b@linaro.org> <20161003221039.GR19318@brightrain.aerifal.cx> In-Reply-To: <20161003221039.GR19318-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Rich Felker Cc: Daniel Lezcano , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Rob Herring , Mark Rutland , Thomas Gleixner On Mon, Oct 03, 2016 at 06:10:39PM -0400, Rich Felker wrote: > On Mon, Sep 26, 2016 at 11:27:14PM +0200, Daniel Lezcano wrote: > > On 26/09/2016 23:07, Rich Felker wrote: > > > Ping. Is there anything that still needs to be changed for this driver > > > to be acceptable? > > > > It is on my radar. I'm reviewing it. > > > > Can you elaborate the workaround mentioned in the changelog. I have been > > digging into the lkml@ thread but it is not clear if the issue is > > related to the time framework, the driver itself or whatever else. Can > > you clarify that ? > > Do you have comments on any remaining issues other than this > workaround? If not I don't mind removing the workaround and trying to > solve the issue separately later. Let me know and either way I'll > submit a v8. One question of interest to me is whether this patchset prevents the RCU CPU stall warnings that you are seeing. Thanx, Paul From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Paul E. McKenney" Subject: Re: [PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver Date: Tue, 4 Oct 2016 00:06:23 -0700 Message-ID: <20161004070623.GM14933@linux.vnet.ibm.com> References: <22c1ee0f908fe3bf8b70f5e87d659ceb29af1434.1474693319.git.dalias@libc.org> <20160926210716.GA12855@brightrain.aerifal.cx> <4b02ba7d-4a31-297a-bbbd-be26da615e7b@linaro.org> <20161003221039.GR19318@brightrain.aerifal.cx> Reply-To: paulmck-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20161003221039.GR19318-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Rich Felker Cc: Daniel Lezcano , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Rob Herring , Mark Rutland , Thomas Gleixner List-Id: devicetree@vger.kernel.org On Mon, Oct 03, 2016 at 06:10:39PM -0400, Rich Felker wrote: > On Mon, Sep 26, 2016 at 11:27:14PM +0200, Daniel Lezcano wrote: > > On 26/09/2016 23:07, Rich Felker wrote: > > > Ping. Is there anything that still needs to be changed for this driver > > > to be acceptable? > > > > It is on my radar. I'm reviewing it. > > > > Can you elaborate the workaround mentioned in the changelog. I have been > > digging into the lkml@ thread but it is not clear if the issue is > > related to the time framework, the driver itself or whatever else. Can > > you clarify that ? > > Do you have comments on any remaining issues other than this > workaround? If not I don't mind removing the workaround and trying to > solve the issue separately later. Let me know and either way I'll > submit a v8. One question of interest to me is whether this patchset prevents the RCU CPU stall warnings that you are seeing. Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753699AbcJDK1a (ORCPT ); Tue, 4 Oct 2016 06:27:30 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:52073 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752870AbcJDK12 (ORCPT ); Tue, 4 Oct 2016 06:27:28 -0400 Date: Tue, 4 Oct 2016 00:06:23 -0700 From: "Paul E. McKenney" To: Rich Felker Cc: Daniel Lezcano , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org, Rob Herring , Mark Rutland , Thomas Gleixner Subject: Re: [PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver Reply-To: paulmck@linux.vnet.ibm.com References: <22c1ee0f908fe3bf8b70f5e87d659ceb29af1434.1474693319.git.dalias@libc.org> <20160926210716.GA12855@brightrain.aerifal.cx> <4b02ba7d-4a31-297a-bbbd-be26da615e7b@linaro.org> <20161003221039.GR19318@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161003221039.GR19318@brightrain.aerifal.cx> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16100410-0024-0000-0000-000014B56438 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00005850; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000186; SDB=6.00764147; UDB=6.00364889; IPR=6.00539892; BA=6.00004782; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00012865; XFM=3.00000011; UTC=2016-10-04 10:27:24 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16100410-0025-0000-0000-00004507374A Message-Id: <20161004070623.GM14933@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-10-04_02:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1610040181 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 03, 2016 at 06:10:39PM -0400, Rich Felker wrote: > On Mon, Sep 26, 2016 at 11:27:14PM +0200, Daniel Lezcano wrote: > > On 26/09/2016 23:07, Rich Felker wrote: > > > Ping. Is there anything that still needs to be changed for this driver > > > to be acceptable? > > > > It is on my radar. I'm reviewing it. > > > > Can you elaborate the workaround mentioned in the changelog. I have been > > digging into the lkml@ thread but it is not clear if the issue is > > related to the time framework, the driver itself or whatever else. Can > > you clarify that ? > > Do you have comments on any remaining issues other than this > workaround? If not I don't mind removing the workaround and trying to > solve the issue separately later. Let me know and either way I'll > submit a v8. One question of interest to me is whether this patchset prevents the RCU CPU stall warnings that you are seeing. Thanx, Paul