From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755451Ab3JHJ6Q (ORCPT ); Tue, 8 Oct 2013 05:58:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:11700 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752676Ab3JHJ6N (ORCPT ); Tue, 8 Oct 2013 05:58:13 -0400 Message-ID: <5253D732.8060906@redhat.com> Date: Tue, 08 Oct 2013 11:58:10 +0200 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130923 Thunderbird/17.0.9 MIME-Version: 1.0 To: Marcelo Tosatti CC: kvm@vger.kernel.org, dzickus@redhat.com, gleb@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [patch 2/3] pvclock: detect watchdog reset at pvclock read References: <20131008010515.516032211@amt.cnet> <20131008010552.779616517@amt.cnet> In-Reply-To: <20131008010552.779616517@amt.cnet> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 08/10/2013 03:05, Marcelo Tosatti ha scritto: > +void pvclock_touch_watchdogs(void) > +{ > + touch_softlockup_watchdog_sync(); > + clocksource_touch_watchdog(); > + rcu_cpu_stall_reset(); > + reset_hung_task_detector(); > +} > + Should this function be in kernel/ instead? It's not really pvclock-specific. Paolo