From: Lukasz Luba <lukasz.luba@arm.com> To: Steev Klimaszewski <steev@kali.org> Cc: Thara Gopinath <thara.gopinath@linaro.org>, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, sudeep.holla@arm.com, will@kernel.org, catalin.marinas@arm.com, linux@armlinux.org.uk, gregkh@linuxfoundation.org, rafael@kernel.org, viresh.kumar@linaro.org, amitk@kernel.org, daniel.lezcano@linaro.org, amit.kachhap@gmail.com, bjorn.andersson@linaro.org, agross@kernel.org Subject: Re: [PATCH v3 0/5] Refactor thermal pressure update to avoid code duplication Date: Tue, 9 Nov 2021 08:29:21 +0000 [thread overview] Message-ID: <d83a5c25-2eae-3626-f78a-e42915076556@arm.com> (raw) In-Reply-To: <97e93876-d654-0a89-dce1-6fe1189345e2@kali.org> Hi Steev, That's interesting what you've done with Rockchip RK3399. I would like to reproduce your experiment on my RockPI 4B v1.3. Could you tell me how you to add this boost frequency that you have mentioned in some previous emails? I want to have similar setup to yours and I'll check all the subsystems involved in the decision making process for triggering this boost freq. On 11/8/21 11:21 PM, Steev Klimaszewski wrote: > Hi Thara, >> Hi Steev, >> >> IIUC, PineBook Pro has Rockchip RK3399 which has 2 Cortex A-72 and 4 >> Cortex A-52 where as C630 has Qualcomm sdm845 which has 4 Cortex A-75 >> and 4 Cortex A-55. Task placements and subsequently cpu load will be >> different for both the platforms. With the same workload, I will >> expect Rockchip to system to be more loaded than sdm845. Having said >> that, what cpu-freq governor are you using on both the systems. >> > I'm using sched-util on both of the systems. > > I've tried a number of different ways of forcing builds only on the A-75 > cores, and I simply cannot get the load to be "enough" to kick in the > boost frequency. > > An example being > > git clone https://github.com/zellij-org/zellij.git > > cd zellij > > taskset --cpu-list 4-7 cargo build --release > > git clean -fdx > > taskset --cpu-list 6-7 cargo build --release Thanks for the pointers, I'll give it a try when I sort out this Rockchip boost setup. > > > On my C630, it never goes higher than 85C with the 4 cores being used, > and with 2, it never goes about 65C and I do not get any 2.96GHz. It's > currently sitting at "6" in the time_in_state for 2965800. > > > --steev > Thank you for your support. Regards, Lukasz
WARNING: multiple messages have this Message-ID (diff)
From: Lukasz Luba <lukasz.luba@arm.com> To: Steev Klimaszewski <steev@kali.org> Cc: Thara Gopinath <thara.gopinath@linaro.org>, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, sudeep.holla@arm.com, will@kernel.org, catalin.marinas@arm.com, linux@armlinux.org.uk, gregkh@linuxfoundation.org, rafael@kernel.org, viresh.kumar@linaro.org, amitk@kernel.org, daniel.lezcano@linaro.org, amit.kachhap@gmail.com, bjorn.andersson@linaro.org, agross@kernel.org Subject: Re: [PATCH v3 0/5] Refactor thermal pressure update to avoid code duplication Date: Tue, 9 Nov 2021 08:29:21 +0000 [thread overview] Message-ID: <d83a5c25-2eae-3626-f78a-e42915076556@arm.com> (raw) In-Reply-To: <97e93876-d654-0a89-dce1-6fe1189345e2@kali.org> Hi Steev, That's interesting what you've done with Rockchip RK3399. I would like to reproduce your experiment on my RockPI 4B v1.3. Could you tell me how you to add this boost frequency that you have mentioned in some previous emails? I want to have similar setup to yours and I'll check all the subsystems involved in the decision making process for triggering this boost freq. On 11/8/21 11:21 PM, Steev Klimaszewski wrote: > Hi Thara, >> Hi Steev, >> >> IIUC, PineBook Pro has Rockchip RK3399 which has 2 Cortex A-72 and 4 >> Cortex A-52 where as C630 has Qualcomm sdm845 which has 4 Cortex A-75 >> and 4 Cortex A-55. Task placements and subsequently cpu load will be >> different for both the platforms. With the same workload, I will >> expect Rockchip to system to be more loaded than sdm845. Having said >> that, what cpu-freq governor are you using on both the systems. >> > I'm using sched-util on both of the systems. > > I've tried a number of different ways of forcing builds only on the A-75 > cores, and I simply cannot get the load to be "enough" to kick in the > boost frequency. > > An example being > > git clone https://github.com/zellij-org/zellij.git > > cd zellij > > taskset --cpu-list 4-7 cargo build --release > > git clean -fdx > > taskset --cpu-list 6-7 cargo build --release Thanks for the pointers, I'll give it a try when I sort out this Rockchip boost setup. > > > On my C630, it never goes higher than 85C with the 4 cores being used, > and with 2, it never goes about 65C and I do not get any 2.96GHz. It's > currently sitting at "6" in the time_in_state for 2965800. > > > --steev > Thank you for your support. Regards, Lukasz _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-09 8:29 UTC|newest] Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-03 16:10 [PATCH v3 0/5] Refactor thermal pressure update to avoid code duplication Lukasz Luba 2021-11-03 16:10 ` Lukasz Luba 2021-11-03 16:10 ` [PATCH v3 1/5] arch_topology: Introduce thermal pressure update function Lukasz Luba 2021-11-03 16:10 ` Lukasz Luba 2021-11-03 16:10 ` [PATCH v3 2/5] thermal: cpufreq_cooling: Use new " Lukasz Luba 2021-11-03 16:10 ` Lukasz Luba 2021-11-03 16:10 ` [PATCH v3 3/5] cpufreq: qcom-cpufreq-hw: Update offline CPUs per-cpu thermal pressure Lukasz Luba 2021-11-03 16:10 ` Lukasz Luba 2021-11-03 16:10 ` [PATCH v3 4/5] cpufreq: qcom-cpufreq-hw: Use new thermal pressure update function Lukasz Luba 2021-11-03 16:10 ` Lukasz Luba 2021-11-05 19:12 ` Thara Gopinath 2021-11-05 19:12 ` Thara Gopinath 2021-11-08 14:12 ` Lukasz Luba 2021-11-08 14:12 ` Lukasz Luba 2021-11-08 21:23 ` Thara Gopinath 2021-11-08 21:23 ` Thara Gopinath 2021-11-09 8:46 ` Lukasz Luba 2021-11-09 8:46 ` Lukasz Luba 2021-11-03 16:10 ` [PATCH v3 5/5] arch_topology: Remove unused topology_set_thermal_pressure() and related Lukasz Luba 2021-11-03 16:10 ` Lukasz Luba 2021-11-05 15:39 ` [PATCH v3 0/5] Refactor thermal pressure update to avoid code duplication Steev Klimaszewski 2021-11-05 15:39 ` Steev Klimaszewski 2021-11-05 16:26 ` Lukasz Luba 2021-11-05 16:26 ` Lukasz Luba 2021-11-05 17:33 ` Steev Klimaszewski 2021-11-05 17:33 ` Steev Klimaszewski 2021-11-05 19:18 ` Thara Gopinath 2021-11-05 19:18 ` Thara Gopinath 2021-11-05 19:51 ` Steev Klimaszewski 2021-11-05 19:51 ` Steev Klimaszewski 2021-11-05 21:06 ` Thara Gopinath 2021-11-05 21:06 ` Thara Gopinath 2021-11-05 22:46 ` Steev Klimaszewski 2021-11-05 22:46 ` Steev Klimaszewski 2021-11-08 10:44 ` Lukasz Luba 2021-11-08 10:44 ` Lukasz Luba 2021-11-08 14:11 ` Thara Gopinath 2021-11-08 14:11 ` Thara Gopinath 2021-11-08 15:22 ` Steev Klimaszewski 2021-11-08 15:22 ` Steev Klimaszewski 2021-11-08 21:31 ` Thara Gopinath 2021-11-08 21:31 ` Thara Gopinath 2021-11-08 23:21 ` Steev Klimaszewski 2021-11-08 23:21 ` Steev Klimaszewski 2021-11-09 8:29 ` Lukasz Luba [this message] 2021-11-09 8:29 ` Lukasz Luba 2021-11-09 15:46 ` Steev Klimaszewski 2021-11-09 15:46 ` Steev Klimaszewski 2021-11-09 16:22 ` Lukasz Luba 2021-11-09 16:22 ` Lukasz Luba 2021-11-09 18:13 ` Lukasz Luba 2021-11-09 18:13 ` Lukasz Luba 2021-11-09 19:09 ` Steev Klimaszewski 2021-11-09 19:09 ` Steev Klimaszewski
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=d83a5c25-2eae-3626-f78a-e42915076556@arm.com \ --to=lukasz.luba@arm.com \ --cc=agross@kernel.org \ --cc=amit.kachhap@gmail.com \ --cc=amitk@kernel.org \ --cc=bjorn.andersson@linaro.org \ --cc=catalin.marinas@arm.com \ --cc=daniel.lezcano@linaro.org \ --cc=gregkh@linuxfoundation.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=rafael@kernel.org \ --cc=steev@kali.org \ --cc=sudeep.holla@arm.com \ --cc=thara.gopinath@linaro.org \ --cc=viresh.kumar@linaro.org \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.