From: Feng Tang <feng.tang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@intel.com>
Cc: Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H . Peter Anvin" <hpa@zytor.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <rui.zhang@intel.com>,
<tim.c.chen@intel.com>,
Xiongfeng Wang <wangxiongfeng2@huawei.com>,
Yu Liao <liaoyu15@huawei.com>
Subject: Re: [PATCH] x86/tsc: Extend the watchdog check exemption to 4S/8S machine
Date: Wed, 12 Oct 2022 16:44:05 +0800 [thread overview]
Message-ID: <Y0Z+VR9MnASeOA3S@feng-clx> (raw)
In-Reply-To: <Y0VpG8POb4AL1g33@hirez.programming.kicks-ass.net>
On Tue, Oct 11, 2022 at 03:01:15PM +0200, Peter Zijlstra wrote:
> On Tue, Oct 11, 2022 at 03:51:21PM +0800, Feng Tang wrote:
> > Th simple patch below is to have a dedicate CPU nodemask and set it in
> > early SRAT CPU parsing, still it has problem when sub-numa is enabled
> > in BIOS where there are more NUMA nodes in SRAT table. (also I'm
> > not sure the change to amdtopology.c is right)
>
> No; none of this has anything to do with nodes. This is about sockets.
Exactly. All we try to do is to get a closer number to the socket
numbers (also stated in current code comments)
According to our discussion, we haven't found a way to get a very
accurate number of sockets, so I plan to (if no objection):
* Send a patch lifting the socket number check from 2 to 4, to fix
the issue reported by Yu Liao.
* Send another RFC patch[1], which makes the socket number more
accurate, as it solve the 2 problems mentioned by Dave:
- fakenuma (numa=fake=4 etc)
- system with CPU-DRAM nodes + HBM nodes + Persistent Memory nodes
but it still can't cover the subnuma enabled case
[1]. https://lore.kernel.org/lkml/Y0UgeUIJSFNR4mQB@feng-clx/
Thanks,
Feng
next prev parent reply other threads:[~2022-10-12 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 5:12 [PATCH] x86/tsc: Extend the watchdog check exemption to 4S/8S machine Feng Tang
2022-10-09 13:01 ` Peter Zijlstra
2022-10-10 1:23 ` Feng Tang
2022-10-10 14:23 ` Dave Hansen
2022-10-11 1:09 ` Feng Tang
2022-10-11 7:51 ` Feng Tang
2022-10-11 13:01 ` Peter Zijlstra
2022-10-12 8:44 ` Feng Tang [this message]
2022-10-11 7:52 ` Peter Zijlstra
2022-10-11 13:33 ` Zhang Rui
2022-10-11 14:01 ` Peter Zijlstra
2022-10-11 14:11 ` Feng Tang
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=Y0Z+VR9MnASeOA3S@feng-clx \
--to=feng.tang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=liaoyu15@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@intel.com \
--cc=wangxiongfeng2@huawei.com \
--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 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.