loongarch.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@kernel.org>,
	Qunqin Zhao <zhaoqunqin@loongson.cn>
Cc: lee@kernel.org, linux-kernel@vger.kernel.org,
	loongarch@lists.linux.dev, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v2] mfd: loongson-se: Add multi-node support
Date: Tue, 28 Apr 2026 20:55:56 +0800	[thread overview]
Message-ID: <197d8afc8c6afe165e60c219b0a08ce6b6698ff9.camel@xry111.site> (raw)
In-Reply-To: <CAAhV-H7SYoN49ZoFi+4V=qyctdzJG0hD=WUBBozewkQzKYia5w@mail.gmail.com>

On Mon, 2026-04-27 at 18:02 +0800, Huacai Chen wrote:
> On Mon, Apr 27, 2026 at 5:52 PM Qunqin Zhao <zhaoqunqin@loongson.cn> wrote:
> > 
> > 
> > 在 2026/4/27 下午5:37, Huacai Chen 写道:
> > > On Mon, Apr 27, 2026 at 5:24 PM Qunqin Zhao <zhaoqunqin@loongson.cn> wrote:
> > > > 
> > > > 在 2026/4/27 下午5:02, Huacai Chen 写道:
> > > > > Hi, Qunqin,
> > > > > 
> > > > > On Mon, Apr 27, 2026 at 4:55 PM Qunqin Zhao
> > > > > <zhaoqunqin@loongson.cn> wrote:
> > > > > > On the Loongson platform, each node is equipped with a
> > > > > > security engine
> > > > > > device. However, due to a hardware flaw, only the device on
> > > > > > node 0 can
> > > > > > trigger interrupts. Therefore, interrupts from other nodes
> > > > > > are forwarded
> > > > > > by node 0. We need to check in the interrupt handler of node
> > > > > > 0 whether
> > > > > > this interrupt is intended for other nodes.
> > > > > Multi-node or multi-package? In my opinion SE has no
> > > > > relationship with
> > > > > NUMA node, so maybe package?
> > > > Here is the output of lscpu from my machine:
> > > > 
> > > > [loongson@localhost ~]$ lscpu
> > > > Architecture:          loongarch64
> > > >     CPU op-mode(s):      32-bit, 64-bit
> > > >     Address sizes:       48 bits physical, 48 bits virtual
> > > >     Byte Order:          Little Endian
> > > > CPU(s):                128
> > > >     On-line CPU(s) list: 0-127
> > > > Model name:            Loongson-3C6000/D
> > > >     CPU family:          Loongson-64bit
> > > >     Model:               0x11
> > > >     Thread(s) per core:  2
> > > >     Core(s) per socket:  32
> > > >     Socket(s):           2
> > > >     BogoMIPS:            4200.00
> > > >     Flags:               cpucfg lam ual fpu lsx lasx crc32
> > > > complex crypto
> > > > lvz lbt_x86 lbt_arm lbt_mips
> > > > Caches (sum of all):
> > > >     L1d:                 4 MiB (64 instances)
> > > >     L1i:                 4 MiB (64 instances)
> > > >     L2:                  16 MiB (64 instances)
> > > >     L3:                  128 MiB (4 instances)
> > > > NUMA:
> > > >     NUMA node(s):        4
> > > >     NUMA node0 CPU(s):   0-31
> > > >     NUMA node1 CPU(s):   32-63
> > > >     NUMA node2 CPU(s):   64-95
> > > >     NUMA node3 CPU(s):   96-127
> > > > 
> > > > There are four SE devices in my system, one for each NUMA node.
> > > For Loongson-3C6000 node is the same as package. You should
> > > consider
> > > Loongson-3C5000L, one package contains four nodes.
> > 
> > I am not familiar with the SE-related components on the 3C5000L, and
> > this driver is not compatible with the 5000 series.
> Whether it is compatible to Loongson-3C5000L is not important. The
> importance is package is not always equal to node, and we should
> consider whether SE is per-node or per-package.

For a "compatible" example, 3C6000/D has two nodes in a package.

-- 
Xi Ruoyao <xry111@xry111.site>

  reply	other threads:[~2026-04-28 12:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 16:51 [PATCH v2] mfd: loongson-se: Add multi-node support Qunqin Zhao
2026-04-27  9:02 ` Huacai Chen
2026-04-27  9:20   ` Qunqin Zhao
2026-04-27  9:37     ` Huacai Chen
2026-04-27  9:47       ` Qunqin Zhao
2026-04-27 10:02         ` Huacai Chen
2026-04-28 12:55           ` Xi Ruoyao [this message]
2026-05-18  3:17           ` Qunqin Zhao

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=197d8afc8c6afe165e60c219b0a08ce6b6698ff9.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=chenhuacai@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=zhaoqunqin@loongson.cn \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).