Received: by 10.223.176.5 with SMTP id f5csp4353119wra; Tue, 30 Jan 2018 06:08:42 -0800 (PST) X-Google-Smtp-Source: AH8x227PmVI/T9fEFviH8t9SjyuuLz13IcNDUKAhtRhWg3QdsqoLvGeK/Im0MgvivQ+Yl35aJMo+ X-Received: by 2002:a17:902:a4:: with SMTP id a33-v6mr25371544pla.257.1517321322277; Tue, 30 Jan 2018 06:08:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517321322; cv=none; d=google.com; s=arc-20160816; b=IiM7sSIDMiQ32+dZQFPSuk96tW+3KYxL2Mb13bcCQMHJyVnxji5tFPoRTVuWIy8cHV nFegZRFu6QCZuep3YvybLi9uMTxDNMnomekFNDEr4bxpWaXdmPmfm7ctVEdWnrRcupOp N7eSjYEVgRK/pqal7+vorQBC8aRpBgc750X6wpoEdc2d6qoI/3NlzdlfHWoO2z22ihvp L82Bnoh4ZmTUhFts+hOe1phu5PY5hURYpzuSnNiunUiRaugwP37/gaB7J3TKNXwQGx7Y HC6rB31Ioc6nxGCvDDIpZ5K9YywgYfKG6wIvmhCbQ5UxmKTvJ6zTiyytkfCERH1m+shx mnwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=ZXlNSzndMfJdVkpLIIA+2TYf+AEcjJqJx/82NC1gkFs=; b=Q4cVxBmRBC+MqzoCZ/q1AEnEKwESPZXU/EWa9BUHzWaBgwiQdTo7NottssICW1UJdF gRfA/HnutGfGhkB3guAQb8BzbGHODEsvQMrOr3M8mXz3CtF/ll2yx1j7E+vnVxWIQ0lS 5nTP27n+SENO2/L9vGL+GqCWO9vBhuuDAUcMakg5YW69IQh4hRppAQqQ2oYzsquHwSP0 QEdY5HNTyKoUMryW5kNuZ9VfmcE3TcjOWYc64hkn3sD4N6axve5GL1/8RIUqCfH3HF5X DUiiT2Oci3q2x/YeWA+blMQAEagi3h0wxRatq0u/KwtQUYm5VACLxreLdKAFKcdaBGhm 4YOw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f80si14379362pfa.111.2018.01.30.06.08.28; Tue, 30 Jan 2018 06:08:42 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752875AbeA3OCi (ORCPT + 99 others); Tue, 30 Jan 2018 09:02:38 -0500 Received: from mail1.windriver.com ([147.11.146.13]:42322 "EHLO mail1.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752066AbeA3OCh (ORCPT ); Tue, 30 Jan 2018 09:02:37 -0500 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.15.2/8.15.1) with ESMTPS id w0UE2DtP023356 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 30 Jan 2018 06:02:13 -0800 (PST) Received: from [172.25.59.215] (172.25.59.215) by ALA-HCA.corp.ad.wrs.com (147.11.189.40) with Microsoft SMTP Server id 14.3.361.1; Tue, 30 Jan 2018 06:02:13 -0800 Subject: Re: [PATCH v2] kdb: use ktime_get_mono_fast_ns() instead of ktime_get_ts() To: Arnd Bergmann , Baolin Wang CC: Daniel Thompson , Ingo Molnar , Mark Brown , , Linux Kernel Mailing List References: <3f15868475cb4b32353885ee03c983209279fa81.1517192387.git.baolin.wang@linaro.org> From: Jason Wessel Message-ID: <8c05803e-eda8-36a1-fd38-77cb570f4ba9@windriver.com> Date: Tue, 30 Jan 2018 08:02:10 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/30/2018 07:35 AM, Arnd Bergmann wrote: > On Mon, Jan 29, 2018 at 3:22 AM, Baolin Wang wrote: >> The kdb code will print the monotonic time by ktime_get_ts(), but >> the ktime_get_ts() will be protected by a sequence lock, that will >> introduce one deadlock risk if the lock was already held in the >> context from which we entered the debugger. >> >> Thus we can use the ktime_get_mono_fast_ns() to get the monotonic >> time, which is NMI safe access to clock monotonic. Moreover we can >> remove the 'struct timespec', which is not y2038 safe. >> >> Signed-off-by: Baolin Wang > > Reviewed-by: Arnd Bergmann > I'll add this in today, run some tests and it should be in the merge window. Thanks, Jason