public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] riscv: Use the same CPU operations for all CPUs
Date: Wed, 22 Nov 2023 11:39:39 +0000	[thread overview]
Message-ID: <20231122-helpless-shaded-64908019806e@spud> (raw)
In-Reply-To: <20231121234736.3489608-4-samuel.holland@sifive.com>


[-- Attachment #1.1: Type: text/plain, Size: 457 bytes --]

On Tue, Nov 21, 2023 at 03:47:26PM -0800, Samuel Holland wrote:
> RISC-V provides no binding (ACPI or DT) to describe per-cpu start/stop
> operations, so cpu_set_ops() will always detect the same operations for
> every CPU. Replace the cpu_ops array with a single pointer to save space
> and reduce boot time.
> 
> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>

Reviewed-by: Conor Dooley <conor.dooley@microchip.com>

Cheers,
Conor.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-11-22 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 23:47 [PATCH 0/3] riscv: CPU operations cleanup Samuel Holland
2023-11-21 23:47 ` [PATCH 1/3] riscv: Deduplicate code in setup_smp() Samuel Holland
2023-11-22 11:18   ` Conor Dooley
2023-11-21 23:47 ` [PATCH 2/3] riscv: Remove unused members from struct cpu_operations Samuel Holland
2023-11-22 11:28   ` Conor Dooley
2023-11-21 23:47 ` [PATCH 3/3] riscv: Use the same CPU operations for all CPUs Samuel Holland
2023-11-22 11:39   ` Conor Dooley [this message]
2024-01-05 21:50 ` [PATCH 0/3] riscv: CPU operations cleanup patchwork-bot+linux-riscv

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=20231122-helpless-shaded-64908019806e@spud \
    --to=conor@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=samuel.holland@sifive.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