From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 85341C4338F for ; Thu, 12 Aug 2021 16:58:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5F6AA60FBF for ; Thu, 12 Aug 2021 16:58:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233781AbhHLQ6y (ORCPT ); Thu, 12 Aug 2021 12:58:54 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:59782 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233391AbhHLQ6x (ORCPT ); Thu, 12 Aug 2021 12:58:53 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1628787506; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=62G4dU5wieVTwuTwkdkYbYBGIKJZ6MMqOVtxRJPIJYw=; b=fIa35NqWRwZjI7/9YAu6i+bf2Akd2/8CnMNsdzDuF4A4n/DlPsj6+8WU40wzMtu7L4o1M+ ZOCe4X9y9KXqXm2KVav/ArozL/SN6poJrlN6cCKaYyFCQIFsy1p9d/HnSfE+JaQQbhG6wX 9PD/+AWukZUOcKkUgCMXW50Lgr1BAbVtNQXbhQPzfCER/o+hY8y+6s6XHJBmihBHCsFVii 4cJkwQC9HjHVJ4QfZklSa87OztsQ/sBbAwFIYhLHc0Z0TfHFG8pyp8ruQEx5Tu7QrixZrZ xLdEOR11A1KwRPpI6xpgt2Aom18Pv9QU96LW/2eGwZWLoRDAGmFDB1Nja0BNvg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1628787506; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=62G4dU5wieVTwuTwkdkYbYBGIKJZ6MMqOVtxRJPIJYw=; b=s7R+9lBNyhtuoJ6c+4Zic/NWGqEHSgxnVP4wPmmCxGkBnN99vpjEuKqkjDIC728nnyaWUm ePDAUR0VClz/yRCA== To: Mike Galbraith , linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org Cc: Peter Zijlstra , x86@kernel.org Subject: Re: [tip: timers/core] hrtimer: Consolidate reprogramming code In-Reply-To: References: <20210713135158.054424875@linutronix.de> <162861133759.395.7795246170325882103.tip-bot2@tip-bot2> <7dfb3b15af67400227e7fa9e1916c8add0374ba9.camel@gmx.de> <87a6lmiwi0.ffs@tglx> <877dgqivhy.ffs@tglx> <87v94ahemj.ffs@tglx> Date: Thu, 12 Aug 2021 18:58:26 +0200 Message-ID: <87pmuiha6l.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 12 2021 at 17:31, Mike Galbraith wrote: > On Thu, 2021-08-12 at 17:22 +0200, Thomas Gleixner wrote: >> > >> > Config attached just in case. >> >> I rather assume it's a hardware dependency. What kind of machine are you >> using? > > Desktop box is a garden variety MEDION i4790 box with an Nvidia GTX980. > Lappy is an HP Spectre 360 i5-6200U w. i915 graphics. Very mundane. Hmm, spectre induced timer meltdown? :) Anyway I found a box which exposes the problem. Investigating... Thanks, tglx