From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f196.google.com ([209.85.220.196]:38797 "EHLO mail-qk0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753172AbdJHSie (ORCPT ); Sun, 8 Oct 2017 14:38:34 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Andy Shevchenko Date: Sun, 8 Oct 2017 21:38:33 +0300 Message-ID: Subject: Re: [RFC v5 1/8] platform/x86: intel_pmc_ipc: Use spin_lock to protect GCR updates To: Kuppuswamy Sathyanarayanan Cc: Alessandro Zummo , "x86@kernel.org" , Wim Van Sebroeck , Ingo Molnar , Alexandre Belloni , Zha Qipeng , "H. Peter Anvin" , "dvhart@infradead.org" , Thomas Gleixner , Lee Jones , Andy Shevchenko , Souvik Kumar Chakravarty , linux-rtc@vger.kernel.org, linux-watchdog@vger.kernel.org, "linux-kernel@vger.kernel.org" , Platform Driver , Sathyanarayanan Kuppuswamy Natarajan , Kuppuswamy Sathyanarayanan Content-Type: text/plain; charset="UTF-8" Sender: linux-rtc-owner@vger.kernel.org List-ID: On Sun, Oct 8, 2017 at 1:19 AM, wrote: > From: Kuppuswamy Sathyanarayanan > > Currently, update_no_reboot_bit() function implemented in this driver > uses mutex_lock() to protect its register updates. But this function is > called with in atomic context in iTCO_wdt_start() and iTCO_wdt_stop() > functions in iTCO_wdt.c driver, which in turn causes "sleeping into > atomic context" issue. This patch fixes this issue by replacing the > mutex_lock() with spin_lock() to protect the GCR read/write/update APIs. > > Fixes: 9d855d4 ("platform/x86: intel_pmc_ipc: Fix iTCO_wdt GCS memory mapping failure") > Signed-off-by: Kuppuswamy Sathyanarayanan > * Rebased this patch on top of Andy's review branch. Oh, what I asked you is to use vanilla kernel as a base. Please, be sure (you assured me, though it's not true) that it's applied against vanilla (or our fixes branch) and send just this one patch separately. No need to resend v5 right now. -- With Best Regards, Andy Shevchenko