lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAHAQgRC5-tSnUZXHxTeVDhYK1m0XCzXho097bV2Awj-6XJ-UFA@mail.gmail.com>
Date:   Tue, 19 Sep 2023 13:33:16 +0800
From:   Chen Wang <unicornxw@...il.com>
To:     robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        Conor Dooley <conor@...nel.org>,
        "xiaoguang.xing" <xiaoguang.xing@...hgo.com>, jszhang@...nel.org,
        Inochi Amaoto <inochiama@...look.com>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     Chen Wang <unicornxw@...il.com>
Subject: Question about writing binding files for numa

Hi, I am working on writing dts for a new SOC - SG2042, you can see
the changes on https://github.com/unicornx/linux-riscv/commit/ee862fc4ebeade32bff00ad014d6b0513c0942a7.
This hardware uses a NUMA architecture,  so a "distance-map" node is
added and several "numa-node-id" are added for cpu/memory. The problem
is I find there is no YAML binding for numa, I only find
"Documentation/devicetree/bindings/numa.txt". To pass dtb check I want
to convert the txt to yaml file.

My question is: how to handle the "numa-node-id" which is listed in
the numa.txt file. To my understanding, due to cpu/memory node need to
contain this property. I should find some binding files for cpu/memory
and add "numa-node-id" for cpu/memory.
For "cpu", I find a
"Documentation/devicetree/bindings/riscv/cpus.yaml", where I think I
can add a property of   "numa-node-id" to. Note the SG2042 is a RISC-V
chip.
But for "memory", where should I add  "numa-node-id" definition to?

Regards,

Chen Wang

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ