From owner-freebsd-current@freebsd.org Tue Jan 23 01:49:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F23BEC0559 for ; Tue, 23 Jan 2018 01:49:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FF2879F8C; Tue, 23 Jan 2018 01:49:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id 16so10747303wry.12; Mon, 22 Jan 2018 17:49:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fevZup30op1VofeVQFWF/M4R1YZdbh1oCXThcvM8bxs=; b=fvNYGqJvotkz9wQe/dfGQ8akg6FJU+Z3VcDeqYgvHn87+tGB1bGZO8tXD0c3/QWRNi Vx+Qu4M/eFg5yYf5ouHT1cjWcVZT+7Jkdl1TlqO6pyRSXHWVzKMMHTJ3MBqt4VL7vp4g D6XjDY03V0ncO6UiiljJsbJuQMHkcTgfaLeAH44ke/Bwin41PcXs3zq7SMjO3iCrdM/F z4aNQcXEBe0uVcaaiJweSioO2L0OlYH5UPW8gdMy7UUrx1WrB87Za/hMCw5Yk820/f+G OF768kVc99+sE3L21HzAmUAy5UL9L+P5u+3UXNqVw3iAfqM8h7qlXc5OjgcsibwFQBw0 txGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fevZup30op1VofeVQFWF/M4R1YZdbh1oCXThcvM8bxs=; b=kFw3504RV+cDFeg8rf/aGDm8+BnHn6ykEuSYGJSChVh6WopdEfqZFY86cFBX7c7vdX azUWpl7XCJFP2HFHDH80m+VyZ6gvpGeLM+ZCZWMYJdcap2o421a9Vu3ZarshVleUZPmZ TtQ3Wk3c/X0B6qlduQZlI+HeA1f9yXPw1Oui7awIwubsexP3KvgMd3txTXBoVwki1fZn t2G8sxHyRM9FeQ4Yeio4LQDmNkypVuN9QJeQhxBHg7ExjiF+s/orIDhs4MYEYvThJcVn qGwxmgFXyP5S/bFeE8YEF1kRCH1sgd4jwgI/ccxe9mxmGJp2iqTRL6chfswPw+sDqet9 wOoA== X-Gm-Message-State: AKwxytfmrFtSD/anfY2JVbclHvJy1GwofODFqHqpbo1Ftga0SOUmxWgn NMADJQKFm9euWiuKFbmCPo/wsWoaEKOHHNW0avU= X-Google-Smtp-Source: AH8x227r9xLDF6VxbBwj55z6mMw1yz1zTMFHUR7bTlqVGaTl3iEYKPF2DFe1rdQuK3Jq9vN7VZRHrKUEq5/8QO/2tEo= X-Received: by 10.223.198.198 with SMTP id c6mr582485wrh.159.1516672139942; Mon, 22 Jan 2018 17:48:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.181.3 with HTTP; Mon, 22 Jan 2018 17:48:58 -0800 (PST) In-Reply-To: References: <64218617-98d2-0e6e-5872-e44106e61bf7@selasky.org> <1516569725.42536.99.camel@freebsd.org> <0aceb3ff-4938-1b29-d493-d83ce82cc853@selasky.org> From: Adrian Chadd Date: Mon, 22 Jan 2018 17:48:58 -0800 Message-ID: Subject: Re: Periodical interrupt storm when playing game with USB keyboard To: Johannes Lundberg Cc: Hans Petter Selasky , Ian Lepore , freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 01:49:02 -0000 Hi Yeah the timers eventually get coalesced unless someone's asking for a ridciulously accurate timer value. So is some driver asking for hyper-accurate callout timer that isn't being coalesced? hps, is there any useful debugging to try and find callouts that are requesting stupidly accurate timers? Maybe a dtrace probe on the callout schedule entry point? -adrian