All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@ozlabs.org, Michael Ellerman <mpe@ellerman.id.au>
Cc: rdunlap@infradead.org, srikar@linux.vnet.ibm.com
Subject: Re: [PATCH 1/3] powerpc: Make NUMA depend on SMP
Date: Thu, 10 Dec 2020 22:30:16 +1100 (AEDT)	[thread overview]
Message-ID: <160756604761.1313423.18058608408740419327.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20201124120547.1940635-1-mpe@ellerman.id.au>

On Tue, 24 Nov 2020 23:05:45 +1100, Michael Ellerman wrote:
> Our Kconfig allows NUMA to be enabled without SMP, but none of
> our defconfigs use that combination. This means it can easily be
> broken inadvertently by code changes, which has happened recently.
> 
> Although it's theoretically possible to have a machine with a single
> CPU and multiple memory nodes, I can't think of any real systems where
> that's the case. Even so if such a system exists, it can just run an
> SMP kernel anyway.
> 
> [...]

Applied to powerpc/next.

[1/3] powerpc: Make NUMA depend on SMP
      https://git.kernel.org/powerpc/c/25395cd2f8cb24ce6a5ce073c898acfb091e06cf
[2/3] powerpc: Make NUMA default y for powernv
      https://git.kernel.org/powerpc/c/4c28b32b886f1489c5f510ed8e3f0c4e3dcb59f5
[3/3] powerpc: Update NUMA Kconfig description & help text
      https://git.kernel.org/powerpc/c/bae80c27fc2195b9e5723d7b05c592e0874f4ba9

cheers

      parent reply	other threads:[~2020-12-10 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 12:05 [PATCH 1/3] powerpc: Make NUMA depend on SMP Michael Ellerman
2020-11-24 12:05 ` [PATCH 2/3] powerpc: Make NUMA default y for powernv Michael Ellerman
2020-11-25  4:30   ` Srikar Dronamraju
2020-11-24 12:05 ` [PATCH 3/3] powerpc: Update NUMA Kconfig description & help text Michael Ellerman
2020-11-24 19:47   ` Randy Dunlap
2020-11-24 19:46 ` [PATCH 1/3] powerpc: Make NUMA depend on SMP Randy Dunlap
2020-11-25  4:30 ` Srikar Dronamraju
2020-12-10 11:30 ` Michael Ellerman [this message]

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=160756604761.1313423.18058608408740419327.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=rdunlap@infradead.org \
    --cc=srikar@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.