Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2120733ybl; Thu, 19 Dec 2019 08:23:21 -0800 (PST) X-Google-Smtp-Source: APXvYqzthxiLEhTvK7/rM/xr7upgnSj+s59hSXK12nt85l9XQiwtHF9e0yKF2oyv9Gbh8MXKXhhX X-Received: by 2002:a05:6830:1d59:: with SMTP id p25mr9936294oth.308.1576772600953; Thu, 19 Dec 2019 08:23:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576772600; cv=none; d=google.com; s=arc-20160816; b=fnaypL8VCibGfbLnscLq8roJ+PrSetdxZYTSgzQ7cYY7o1fBec+vAGjq5Uagl1RSAX K53QXeRJJ7uvczTgZXnNi0mU/G5UEytEyhzhdH+TMdc49LgumUaAp6MGhqBnLt9u7lWV eQaixjb48mja0thpM8BkRzdSxd/zW+Zf+OD+Q57YvPBc0+NI9yWR+WTDfFh8zq6i1zaZ wY/A4u7Ro9ANmdFdUIetSEi+7avnJ0dxppev7KNczmsNTWCtVd5F02En2mDE2vmkP3Ou 4/DsM5VrRbNie6BOAZHT2ctIqceFXPsCsXS4ONJnGHHXqgOChKAikV7IWLHItnm8IMVt KKmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=j7qYM1VZ9asUX1JXywhXLoBdTa6WyW86FKKRtK2gTmw=; b=kQ7SbgBO+EuHKxDuDbREsUUjTMbEGFoYv+kDeWjZ5W+8TS+n3y0MBtAsAjRU/rgDMS TF7860HGRsfVecDaYu/D09aoCZGa7NLiKUdiuroLXG96eAfSl4VlshXYkHY02ARH3PtR IIfpXlKHZboBhaW4VrYo2nD2urQuLhAA8rkOqOFt6FKXpxmzzRlqXdYWKjJ2+o1o9+mC n6sh1TaT10ChTl6cISQ4pTKDnYJglVZFkCzukl0vLhI+EPjTieTnZAygVjykQHlvwFpZ ZD//MR9OPGa3LxFYGaxnHWdttEBkRNQcbu6mMXsjMmuo6u7D4NcOU6OPao35slSy992z x+6Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w7si3375941otq.250.2019.12.19.08.23.01; Thu, 19 Dec 2019 08:23:20 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726936AbfLSQWS (ORCPT + 99 others); Thu, 19 Dec 2019 11:22:18 -0500 Received: from mail.kernel.org ([198.145.29.99]:32966 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726873AbfLSQWR (ORCPT ); Thu, 19 Dec 2019 11:22:17 -0500 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8BE0A206EC; Thu, 19 Dec 2019 16:22:16 +0000 (UTC) Date: Thu, 19 Dec 2019 11:22:14 -0500 From: Steven Rostedt To: Kirill Tkhai Cc: Peter Zijlstra , mingo@redhat.com, juri.lelli@redhat.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, bsegall@google.com, mgorman@suse.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] sched: Micro optimization in pick_next_task() and in check_preempt_curr() Message-ID: <20191219112214.37f1f0af@gandalf.local.home> In-Reply-To: References: <157675913272.349305.8936736338884044103.stgit@localhost.localdomain> <20191219131242.GK2827@hirez.programming.kicks-ass.net> <20191219140252.GS2871@hirez.programming.kicks-ass.net> <20191219094330.0e44c748@gandalf.local.home> <11d755e9-e4f8-dd9e-30b0-45aebe260b2f@virtuozzo.com> <20191219095941.2eebed84@gandalf.local.home> <44c95c18-7593-f3e7-f710-a7d424af7442@virtuozzo.com> <20191219104018.5f8e50d2@gandalf.local.home> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 19 Dec 2019 19:08:05 +0300 Kirill Tkhai wrote: > Should I resend this as two patches, with your changes in a separate? You don't have to, you can include multiple SOBs if a patch was written by two people. But perhaps it will better to do so, that way people will know who to blame when the linker breaks ;-) I'll send you a patch that you can apply just before your change. That may be the cleanest way. -- Steve