linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saurabh Sengar <ssengar@linux.microsoft.com>
To: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
	decui@microsoft.com, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
	hpa@zytor.com, peterz@infradead.org, sboyd@kernel.org,
	linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org
Cc: ssengar@microsoft.com
Subject: [PATCH v2 0/4] Fixing SMP config for DeviceTree platforms
Date: Tue,  2 Apr 2024 07:40:26 -0700	[thread overview]
Message-ID: <1712068830-4513-1-git-send-email-ssengar@linux.microsoft.com> (raw)

Original motivation for these changes was to fix an SMT warning observed
in Hyper-V VTL platform. Check V1 for more details:
https://lore.kernel.org/lkml/1710265404-23146-1-git-send-email-ssengar@linux.microsoft.com/

But on further review it was observed that x86 DeviceTree config has
modified recently, and there is opportunity to improve the existing
smp parsing for DeviceTree.

https://lore.kernel.org/lkml/20230807135027.064321764@linutronix.de/

Changes are small but I have logically separated them into four patches.
I am willing to merge them if there are too many 

[V2]
- Modified the approch how to fix the SMT issue, this is patch 3
  in this series. V1 for it is mentioned in above link.
- Added 2 more patches which are related to new SMP config parsing.
  These are patches 2 and 4 in this series.
- Fixed an issue with hv_vtl platform how it should use the smp
  parsing for DeviceTree with a fixes tag.

Saurabh Sengar (4):
  x86/hyperv/vtl: Correct parse_smp_cfg assignment
  x86/of: Set the parse_smp_cfg for all the DeviceTree platforms by
    default
  x86/of: Map NUMA node to CPUs as per DeviceTree
  x86/of: Change x86_dtb_parse_smp_config to static

 arch/x86/hyperv/hv_vtl.c          |  1 -
 arch/x86/include/asm/prom.h       |  9 ++-------
 arch/x86/kernel/devicetree.c      | 24 ++++++++++++++----------
 arch/x86/platform/ce4100/ce4100.c |  1 -
 4 files changed, 16 insertions(+), 19 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-04-02 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 14:40 Saurabh Sengar [this message]
2024-04-02 14:40 ` [PATCH v2 1/4] x86/hyperv/vtl: Correct parse_smp_cfg assignment Saurabh Sengar
2024-04-04 23:58   ` Wei Liu
2024-04-02 14:40 ` [PATCH v2 2/4] x86/of: Set the parse_smp_cfg for all the DeviceTree platforms by default Saurabh Sengar
2024-04-02 14:40 ` [PATCH v2 3/4] x86/of: Map NUMA node to CPUs as per DeviceTree Saurabh Sengar
2024-04-02 14:40 ` [PATCH v2 4/4] x86/of: Change x86_dtb_parse_smp_config to static Saurabh Sengar

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=1712068830-4513-1-git-send-email-ssengar@linux.microsoft.com \
    --to=ssengar@linux.microsoft.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sboyd@kernel.org \
    --cc=ssengar@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=wei.liu@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).