Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp2859663ybv; Mon, 24 Feb 2020 13:06:54 -0800 (PST) X-Google-Smtp-Source: APXvYqyuruKZgSXRYS4LmUJlOv95+ggFodLSfgv1WuEbTVuItbdaqJ8sZ9zjJgve9WU07AvzWQIW X-Received: by 2002:a9d:7d87:: with SMTP id j7mr40163028otn.159.1582578413938; Mon, 24 Feb 2020 13:06:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582578413; cv=none; d=google.com; s=arc-20160816; b=yzX+bwnCFLzz02Uo264NNExT/D3ufRiVU/jA8jz/7l/xfgWVhpwqK6vjlsovfwog57 LXxb0FJ8NoVu6qpdW8Ppq2cc7O1zIg2x1BhA9cEGkgpZA4O3La+GREemnJarfya09yXh HMhHKEy2JIav3elAr/Jjk4Y2q75dK1SWoeW8yNViD0S+eJwd7QS9BEGIdDhFRIVbYLRy AaOPn+d2IJKj9eS55BnbPKa+IJG+32J9gw3shRw/HbFO8NX4HJQ+ARJnadzg8lfN6B7k nDyTeyvIXVs6F86jmRewVqInzimo1i86V0ZKZgzzITj2D95/35Aj9I0fUWEPY7iM9UHa jVpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=5DSVOjO5MMhcJ4Yyl/SzEqdijrruBzjPxBcZjpo5gPE=; b=TP9ISNBw0XQAyquzwfY1jf8OerupyvKlg7kSBBPJsVc2qiN/n2ogFkO7OFZEm4RX0R v+X+dwHT0X2piqO+c3++xXnjT7/UZeWKhdgc2lY27BEHFoXqY4TAUUmJXqd/EF1lCWPm THk9PqnrOSkjDEE0AAx+cKAZSiE/olQxgZfycMuz++JgeYfzTiSd2GQL2XqmO/8hxnjN PR8oL0jOX2Kp8wYZlYp8aVvaJInqzKlPhebq0h+iXXQjhRA6UaAOPJFfo9n2SgzE+I6d CnUG3UqkaEBdeKc6+9VQiEarLMQDoMfs0SuSLa9lS6raMtoyBRKW5XpmK0sdK/6lDqqd Wr4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@riseup.net header.s=squak header.b=PVYEzY4k; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=riseup.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b2si5481549oic.205.2020.02.24.13.06.40; Mon, 24 Feb 2020 13:06:53 -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; dkim=pass header.i=@riseup.net header.s=squak header.b=PVYEzY4k; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=riseup.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727662AbgBXVGa (ORCPT + 99 others); Mon, 24 Feb 2020 16:06:30 -0500 Received: from mx1.riseup.net ([198.252.153.129]:47392 "EHLO mx1.riseup.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726996AbgBXVGa (ORCPT ); Mon, 24 Feb 2020 16:06:30 -0500 Received: from capuchin.riseup.net (capuchin-pn.riseup.net [10.0.1.176]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 48RF3n0DWBzFdby; Mon, 24 Feb 2020 13:06:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1582578389; bh=W7L9/p4orgEMw+230MsM0ON95JQJoNVyJegMs/MVNZE=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=PVYEzY4k7DBlnhSH8pL6ooSsQidK+NwSOEGdW0wALemKR5p7gNcR2apUS0bBRJo0f fApcuhrAIWy9PJOb9SQnFfWJ+ghnOE3ok+pXefxCjBE1+cFX75q4wX0ZtfArKJtzyS zubolc91Lv0ILUHzwHJo5wneSPONHHrKLOeDrwl8= X-Riseup-User-ID: 0858FF1C1280C931723AC04564AE1ACC9FF94A9985270954AC48D09166F8B32F Received: from [127.0.0.1] (localhost [127.0.0.1]) by capuchin.riseup.net (Postfix) with ESMTPSA id 48RF3m2ng0z8tqF; Mon, 24 Feb 2020 13:06:28 -0800 (PST) From: Francisco Jerez To: "Rafael J. Wysocki" Cc: "Rafael J. Wysocki" , "Rafael J. Wysocki" , Linux PM , LKML , Amit Kucheria , "Pandruvada\, Srinivas" , Rodrigo Vivi , Peter Zijlstra Subject: Re: [PATCH 00/28] PM: QoS: Get rid of unuseful code and rework CPU latency QoS interface In-Reply-To: References: <1654227.8mz0SueHsU@kreacher> <87wo8rjsa4.fsf@riseup.net> <877e0qj4bm.fsf@riseup.net> <87ftf3fv69.fsf@riseup.net> Date: Mon, 24 Feb 2020 13:06:24 -0800 Message-ID: <87lforelv3.fsf@riseup.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --==-=-= Content-Type: multipart/mixed; boundary="=-=-=" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Disposition: inline "Rafael J. Wysocki" writes: > On Fri, Feb 21, 2020 at 11:10 PM Francisco Jerez wrote: >> >> "Rafael J. Wysocki" writes: >> >> > On Thu, Feb 13, 2020 at 9:09 AM Francisco Jerez wrote: >> >> >> >> "Rafael J. Wysocki" writes: >> >> >> >> > On Thu, Feb 13, 2020 at 1:16 AM Rafael J. Wysocki wrote: >> >> >> >> >> >> On Thu, Feb 13, 2020 at 12:31 AM Francisco Jerez wrote: >> >> >> > >> > >> > [cut] >> > >> >> > >> >> > And BTW, posting patches as RFC is fine even if they have not been >> >> > tested. At least you let people know that you work on something this >> >> > way, so if they work on changes in the same area, they may take that >> >> > into consideration. >> >> > >> >> >> >> Sure, that was going to be the first RFC. >> >> >> >> > Also if there are objections to your proposal, you may save quite a >> >> > bit of time by sending it early. >> >> > >> >> > It is unfortunate that this series has clashed with the changes that >> >> > you were about to propose, but in this particular case in my view it >> >> > is better to clean up things and start over. >> >> > >> >> >> >> Luckily it doesn't clash with the second RFC I was meaning to send, >> >> maybe we should just skip the first? >> > >> > Yes, please. >> > >> >> Or maybe it's valuable as a curiosity anyway? >> > >> > No, let's just focus on the latest one. >> > >> > Thanks! >> >> We don't seem to have reached much of an agreement on the general >> direction of RFC2, so I can't really get started with it. Here is RFC1 >> for the record: >> >> https://github.com/curro/linux/commits/intel_pstate-lp-hwp-v10.8-alt > > Appreciate the link, but that hasn't been posted to linux-pm yet, so > there's not much to discuss. > > And when you post it, please rebase it on top of linux-next. > >> Specifically the following patch conflicts with this series: >> >> https://github.com/curro/linux/commit/9a16f35531bbb76d38493da892ece088e31dc2e0 >> >> Series improves performance-per-watt of GfxBench gl_4 (AKA Car Chase) by >> over 15% on my system with the branch above, actual FPS "only" improves >> about 5.9% on ICL laptop due to it being very lightly TDP-bound with its >> rather huge TDP. The performance of almost every graphics benchmark >> I've tried improves significantly with it (a number of SynMark >> test-cases are improved by around 40% in perf-per-watt, Egypt >> perf-per-watt improves by about 25%). >> >> Hopefully we can come up with some alternative plan of action. > > It is very easy to replace the patch above with an alternative one on > top of linux-next that will add CPU_RESPONSE_FREQUENCY QoS along the > lines of the CPU latency QoS implementation in there without the need > restore to global QoS classes. > > IOW, you don't really need the code that goes away in linux-next to > implement what you need. > > Thanks! Sure, I'll do that. --=-=-=-- --==-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEAREIAB0WIQST8OekYz69PM20/4aDmTidfVK/WwUCXlQ60QAKCRCDmTidfVK/ W3Y8AP9NgEjOmGkf1vstyGw90gmmNDSfMczKCw7o0DvxAVYerAD/WfE5Swgms89I SxJEaZIsofupzojqQVCcuPEgjFDpqbA= =Kq/o -----END PGP SIGNATURE----- --==-=-=--