Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp346573ybl; Wed, 29 Jan 2020 01:28:02 -0800 (PST) X-Google-Smtp-Source: APXvYqwGWX8c6ttB7SLZLFbebaOoFpfrvc8AE1dEp2jbj5vM6rQSLxkqfF34CNqT1Gh7RwZ6ngXV X-Received: by 2002:aca:d4c1:: with SMTP id l184mr5876763oig.172.1580290082555; Wed, 29 Jan 2020 01:28:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580290082; cv=none; d=google.com; s=arc-20160816; b=MublPd8lLubU3ZVi4glYhzk3As7JvW7lj6khvHMyvOo6M1ZvxQKNyceKvbXvZtZskI M+XKdU2w007lKzw3sYpYMbOBMuIBGD4Bb0rQw54WxSKv3S37jrv3KVELBLJx6yrG9Se5 I+vT8V/6iVh95Y/IBCuQ3TbPQ5KQZRIvAqxCvXWPva+1E0j7FQYlIB9YWe/oUs1m5rLp 9AMmymKO0YDr1kJmWZX5Q1T/LMbzz5L+HigQ6qMLAp07HXIW9BEg7uM7OPQVGghJlf+I w/C4RXQJjOy0jcNwu2S7aKmOyvClw+xYw05Uv8+/SO4X/woGICdG8vDeE43RHGG+2aW9 d1EQ== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=h+2Fu6jqhBGXNeGjp5UZUl2Tf7O+Xd3L1UIcKWFzoqA=; b=YI80fqCAv6i+e6SNvLPPKk34G5KbtvWOl2lWVIAV68+ImhOVlcmgCAy5BquJ87NvF+ IrCsEtydgHSayh2Zo52XN4887vYOJ3f67CUsbu06E5wWID5tsaN5pqUHi3W51jTvzobB QRh8J7njs6qrwW3hD6XF1zfuDhjE+ZOAwRvmu+UjPQ9oJTrvhi+hedx0oF1jFVdGhWUl wnnT2Gvm0Yzne3+yEzCfxJO4sGTqQEZKp4pQjiA72ZxwFW4xZ14wN8qSQCplkqZFngnO 6wX0B+zPzP8IK0qY0O2qW0JIaOD8XqVzwoirLozjAvbeYV37wBdBh2NLXMmSJ7IbpQBg P5aQ== 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 t26si758248otq.264.2020.01.29.01.27.50; Wed, 29 Jan 2020 01:28:02 -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 S1726177AbgA2JZ6 (ORCPT + 99 others); Wed, 29 Jan 2020 04:25:58 -0500 Received: from foss.arm.com ([217.140.110.172]:38478 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726010AbgA2JZ6 (ORCPT ); Wed, 29 Jan 2020 04:25:58 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 087611FB; Wed, 29 Jan 2020 01:25:58 -0800 (PST) Received: from [10.0.2.15] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id BBB513F52E; Wed, 29 Jan 2020 01:25:56 -0800 (PST) Subject: Re: [PATCH v3 1/3] sched/fair: Add asymmetric CPU capacity wakeup scan To: Pavan Kondeti Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, peterz@infradead.org, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, morten.rasmussen@arm.com, qperret@google.com, adharmap@codeaurora.org References: <20200126200934.18712-1-valentin.schneider@arm.com> <20200126200934.18712-2-valentin.schneider@arm.com> <20200128062245.GA27398@codeaurora.org> <1ed322d6-0325-ecac-cc68-326a14b8c1dd@arm.com> <20200129035258.GB27398@codeaurora.org> From: Valentin Schneider Message-ID: <7dd8b850-855c-29e2-8580-357cf1c8ce30@arm.com> Date: Wed, 29 Jan 2020 09:25:50 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <20200129035258.GB27398@codeaurora.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29/01/2020 03:52, Pavan Kondeti wrote: >> No particular reason other than we didn't consider it, I think. I don't see >> any harm in folding it in, I'll do that for v4. I am curious however; are >> you folks making use of SCHED_IDLE? AFAIA Android isn't making use of it >> yet, though Viresh paved the way for that to happen. >> > > We are not using SCHED_IDLE in product setups. I am told Android may use it > for background tasks in future. I am not completely sure though. I asked it > because select_idle_cpu() is using it. > Fair enough! Thanks.