linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sherry Yang <sherry.yang@oracle.com>
To: "mingo@redhat.com" <mingo@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"bp@alien8.de" <bp@alien8.de>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sherry Yang <sherry.yang@oracle.com>
Subject: Re: [PATCH 5.4 0/2] Backports "x86, sched: Treat Intel SNC topology as default, COD as exception"
Date: Wed, 16 Jun 2021 22:59:46 +0000	[thread overview]
Message-ID: <A969D4BF-D21B-4AB0-97AE-5C881C6F187D@oracle.com> (raw)
In-Reply-To: <20210608003715.66882-1-sherry.yang@oracle.com>


> On Jun 7, 2021, at 5:37 PM, Sherry Yang <sherry.yang@oracle.com> wrote:
> 
> Could you also backport these two commits
> adefe55e7258 ("x86/kernel: Convert to new CPU match macros")
> 2c88d45edbb8 ("x86, sched: Treat Intel SNC topology as default,
> COD as exception") to 5.4.y?
> 
> Commit adefe55e7258 ("x86/kernel: Convert to new CPU match macros")
> is a prerequisite of the second commit. There are conflicts while
> cherry-picking commit adefe55e7258 ("x86/kernel: Convert to new
> CPU match macros"), which are caused by a later commit
> c84cb3735fd5 ("x86/apic: Move TSC deadline timer debug printk").
> Keep the later code base.
> 
> Alison Schofield (1):
>  x86, sched: Treat Intel SNC topology as default, COD as exception
> 
> Thomas Gleixner (1):
>  x86/kernel: Convert to new CPU match macros
> 
> arch/x86/kernel/apic/apic.c | 32 ++++++-------
> arch/x86/kernel/smpboot.c   | 90 +++++++++++++++++++------------------
> arch/x86/kernel/tsc_msr.c   | 14 +++---
> arch/x86/power/cpu.c        | 16 +------
> 4 files changed, 68 insertions(+), 84 deletions(-)
> 
> -- 
> 2.27.0
> 

Hi,
 
We have seen that the warning “sched: CPU #20's llc-sibling CPU #0 is not on 
the same node! [node: 1 != 0]. Ignoring dependency. ” applies to 5.4 but we don’t 
observe the fix in 5.4. I'm sending this email to apply the fix from upstream 
2c88d45edbb8 ("x86, sched: Treat Intel SNC topology as default, COD as 
exception") to 5.4 and also resolve the dependency conflict caused by 
prerequisite commit adefe55e7258 ("x86/kernel: Convert to new CPU match 
macros”) by keeping the later code base, please refer to the
previous two patches for the detail.
 
Thanks,
Sherry


       reply	other threads:[~2021-06-16 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210608003715.66882-1-sherry.yang@oracle.com>
2021-06-16 22:59 ` Sherry Yang [this message]
2021-06-17 10:32   ` [PATCH 5.4 0/2] Backports "x86, sched: Treat Intel SNC topology as default, COD as exception" Greg KH

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=A969D4BF-D21B-4AB0-97AE-5C881C6F187D@oracle.com \
    --to=sherry.yang@oracle.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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).