Linux Documentation
 help / color / mirror / Atom feed
From: Leyfoon Tan <leyfoon.tan@starfivetech.com>
To: Conor Dooley <conor.dooley@microchip.com>,
	Song Shuai <suagrfillet@gmail.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
	"alexs@kernel.org" <alexs@kernel.org>,
	"siyanteng@loongson.cn" <siyanteng@loongson.cn>,
	"robh@kernel.org" <robh@kernel.org>,
	"palmer@rivosinc.com" <palmer@rivosinc.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: RE: [PATCH] sched/doc: supplement CPU capacity with RISC-V
Date: Tue, 28 Feb 2023 02:00:56 +0000	[thread overview]
Message-ID: <49412393956e428fbc7d27ddecee3493@EXMBX061.cuchost.com> (raw)
In-Reply-To: <Y/yoWt+Y7n8/A6m9@wendy>



> -----Original Message-----
> From: Conor Dooley <conor.dooley@microchip.com>
> Sent: Monday, February 27, 2023 8:56 PM
> To: Song Shuai <suagrfillet@gmail.com>
> Cc: corbet@lwn.net; alexs@kernel.org; siyanteng@loongson.cn;
> robh@kernel.org; palmer@rivosinc.com; Leyfoon Tan
> <leyfoon.tan@starfivetech.com>; linux-doc@vger.kernel.org; linux-
> kernel@vger.kernel.org; linux-riscv@lists.infradead.org
> Subject: Re: [PATCH] sched/doc: supplement CPU capacity with RISC-V
> 
> On Mon, Feb 27, 2023 at 12:40:45PM +0000, Song Shuai wrote:
> > Conor Dooley <conor.dooley@microchip.com> 于2023年2月27日周一
> 11:57写道:
> > >
> > > On Mon, Feb 27, 2023 at 06:59:41PM +0800, Song Shuai wrote:
> > > > This commit 7d2078310cbf ("dt-bindings: arm: move cpu-capacity to
> > > > a shared loation") updates some references about
> > > > capacity-dmips-mhz
> > >
> > > Not requesting a respin for this, but mentioning commit 991994509ee9
> > > ("dt-bindings: riscv: add a capacity-dmips-mhz cpu property") is
> > > probably more relevant as a justification for this change.
> > >
> > Thanks for your correction, I'll pay attention next time.
> >
> > I have a question about the patch you mentioned:
> > The patch uses cpu_scale per_cpu variable to store the CPU capacity
> > through arch_topology, But arch_scale_cpu_capacity() interface seems
> > not defined to deliver the cpu_scale to the scheduler In contrast,
> > arm64 defines it as the topology_get_cpu_scale() in its
> > arch/arm64/include/asm/topology.h.
> > Is this an oversight or a particular purpose?
> 
> Intentional oversight I suppose? It wasn't my intention to do anything other
> than document the property that people were already using in their
> devicetrees (and finding bugs with!).
> In retrospect, perhaps it is better if I un-review this patch until we know it is
> plumbed into the scheduler properly?
> 
> Ley Foon Tan is the one that found the RISC-V bugs with this property in their
> devicetree, so perhaps they've already done the work here?

I have few patches to wire up few arch_*_topology functions for RISC-V architecture. But haven't send out to ML.

Regards
Ley Foon

  reply	other threads:[~2023-02-28  2:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 10:59 [PATCH] sched/doc: supplement CPU capacity with RISC-V Song Shuai
2023-02-27 11:56 ` Conor Dooley
2023-02-27 12:40   ` Song Shuai
2023-02-27 12:55     ` Conor Dooley
2023-02-28  2:00       ` Leyfoon Tan [this message]
2023-02-28  7:11 ` Alex Shi
2023-02-28 21:59 ` Palmer Dabbelt
2023-02-28 22:13   ` Jonathan Corbet
2023-03-07 17:18     ` Jonathan Corbet

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=49412393956e428fbc7d27ddecee3493@EXMBX061.cuchost.com \
    --to=leyfoon.tan@starfivetech.com \
    --cc=alexs@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.com \
    --cc=robh@kernel.org \
    --cc=siyanteng@loongson.cn \
    --cc=suagrfillet@gmail.com \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox