loongarch.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Arnd Bergmann <arnd@arndb.de>, Marc Zyngier <maz@kernel.org>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
	loongson-kernel@lists.loongnix.cn
Subject: [PATCH v3 0/4] Give chance to build under !CONFIG_SMP for LoongArch
Date: Thu, 11 Apr 2024 09:05:06 +0800	[thread overview]
Message-ID: <20240411010510.22135-1-yangtiezhu@loongson.cn> (raw)

The changes of irqchip have been merged into the irq/core branch of tip.

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=42a7d887664b
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=a64003da0ef8

This version is only related with arch/loongarch and based on 6.9-rc3,
the first 3 patches with detailed commit message are preparations for
patch #4.

Tested with the following configs:
(1) CONFIG_NUMA=n, CONFIG_SMP=n
(2) CONFIG_NUMA=n, CONFIG_SMP=y
(3) CONFIG_NUMA=y, CONFIG_SMP=n (not allowed due to NUMA select SMP)
(4) CONFIG_NUMA=y, CONFIG_SMP=y

Tiezhu Yang (4):
  LoongArch: Move CONFIG_HAVE_SETUP_PER_CPU_AREA related code to smp.c
  LoongArch: Refactor get_acpi_id_for_cpu() related code
  LoongArch: Save and restore PERCPU_BASE_KS for ACPI S3 state
  LoongArch: Give chance to build under !CONFIG_SMP

 arch/loongarch/Kconfig                |  4 +-
 arch/loongarch/include/asm/acpi.h     |  8 +++-
 arch/loongarch/include/asm/smp.h      |  5 +++
 arch/loongarch/kernel/acpi.c          |  9 +++-
 arch/loongarch/kernel/irq.c           |  2 +
 arch/loongarch/kernel/machine_kexec.c |  2 +-
 arch/loongarch/kernel/numa.c          | 58 --------------------------
 arch/loongarch/kernel/smp.c           | 59 +++++++++++++++++++++++++++
 arch/loongarch/power/suspend.c        |  4 +-
 9 files changed, 87 insertions(+), 64 deletions(-)

-- 
2.42.0


             reply	other threads:[~2024-04-11  1:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  1:05 Tiezhu Yang [this message]
2024-04-11  1:05 ` [PATCH v3 1/4] LoongArch: Move CONFIG_HAVE_SETUP_PER_CPU_AREA related code to smp.c Tiezhu Yang
2024-04-12  4:12   ` Huacai Chen
2024-04-12  9:27     ` Tiezhu Yang
2024-04-13  7:20       ` Huacai Chen
2024-04-11  1:05 ` [PATCH v3 2/4] LoongArch: Refactor get_acpi_id_for_cpu() related code Tiezhu Yang
2024-04-12  4:17   ` Huacai Chen
2024-04-12  9:28     ` Tiezhu Yang
2024-04-11  1:05 ` [PATCH v3 3/4] LoongArch: Save and restore PERCPU_BASE_KS for ACPI S3 state Tiezhu Yang
2024-04-12  4:18   ` Huacai Chen
2024-04-12  9:30     ` Tiezhu Yang
2024-04-13  7:22       ` Huacai Chen
2024-04-11  1:05 ` [PATCH v3 4/4] LoongArch: Give chance to build under !CONFIG_SMP Tiezhu Yang
2024-04-11  4:26 ` [PATCH v3 0/4] Give chance to build under !CONFIG_SMP for LoongArch Huacai Chen
2024-04-11  6:06   ` Arnd Bergmann
2024-04-12  4:00     ` Huacai Chen
2024-04-18 17:44     ` Xi Ruoyao

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=20240411010510.22135-1-yangtiezhu@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=arnd@arndb.de \
    --cc=chenhuacai@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=loongson-kernel@lists.loongnix.cn \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    /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 NNTP newsgroup(s).