Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751938AbbKPLWu (ORCPT ); Mon, 16 Nov 2015 06:22:50 -0500 Received: from mail.fireflyinternet.com ([87.106.93.118]:63923 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750865AbbKPLWt (ORCPT ); Mon, 16 Nov 2015 06:22:49 -0500 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Date: Mon, 16 Nov 2015 11:22:38 +0000 From: Chris Wilson To: Tvrtko Ursulin Cc: Jens Axboe , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Daniel Vetter , Eero Tamminen , "Rantala, Valtteri" , stable@kernel.vger.org Subject: Re: [PATCH 1/2] drm/i915: Break busywaiting for requests on pending signals Message-ID: <20151116112238.GR569@nuc-i3427.alporthouse.com> Mail-Followup-To: Chris Wilson , Tvrtko Ursulin , Jens Axboe , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Daniel Vetter , Eero Tamminen , "Rantala, Valtteri" , stable@kernel.vger.org References: <1447594364-4206-1-git-send-email-chris@chris-wilson.co.uk> <5649A7C2.90206@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5649A7C2.90206@linux.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1309 Lines: 33 On Mon, Nov 16, 2015 at 09:54:10AM +0000, Tvrtko Ursulin wrote: > > Hi, > > On 15/11/15 13:32, Chris Wilson wrote: > >The busywait in __i915_spin_request() does not respect pending signals > >and so may consume the entire timeslice for the task instead of > >returning to userspace to handle the signal. > > Obviously correct to break the spin, but if spending a jiffie to > react to signals was the only problem then it is not too severe. > > Add something to the commit message about how it was found/reported > and about the severity of impact, etc? Perhaps: At the worst case this could cause a delay in signal processing of 20ms, which would be a noticeable jitter in cursor tracking. If a higher resolution signal was being used, for example to provide fairness of a server timeslices between clients, we could expect to detect some unfairness between clients. This issue was noticed when inspecting a report of poor interactivity resulting from excessively high __i915_spin_request usage. -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/