public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Fernando Fernandez Mancera <ffmancera@riseup.net>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, x86@kernel.org
Subject: Re: [PATCH RESEND] x86/cpu/topology: remove limit of CPUs due to noapic on x86_64
Date: Mon, 25 Nov 2024 09:37:56 +0100	[thread overview]
Message-ID: <Z0Q3ZNoQsoiCAiiA@gmail.com> (raw)
In-Reply-To: <20241124174510.2561-1-ffmancera@riseup.net>


* Fernando Fernandez Mancera <ffmancera@riseup.net> wrote:

> On x86_64 the command line parameter "noapic" should not limit the
> number of possible CPUs, as it only limits the use of IRQ sharing or
> device IRQ remapping. Only on x86_32 the command line parameter
> "nolapic" limits the number of possible CPUs to one. This restores the
> behavior previous to the rework of possible CPU management.

So what's the motivation? Arguably the x86-64 boot option behavior was 
weird: a working local APIC is very much needed to have an SMP system.

If we want to disable IRQ sharing or device IRQ remapping, then that 
should have an appropriately named boot command line option. Does some 
system require that perhaps?

Thanks,

	Ingo

  reply	other threads:[~2024-11-25  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24 17:45 [PATCH RESEND] x86/cpu/topology: remove limit of CPUs due to noapic on x86_64 Fernando Fernandez Mancera
2024-11-25  8:37 ` Ingo Molnar [this message]
2024-11-25 15:13   ` Fernando F. Mancera
2024-12-01 13:49     ` Thomas Gleixner
2024-12-01 13:56 ` Thomas Gleixner

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=Z0Q3ZNoQsoiCAiiA@gmail.com \
    --to=mingo@kernel.org \
    --cc=ffmancera@riseup.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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