public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
	mingo@redhat.com, hpa@zytor.com, bp@suse.de
Subject: Re: [PATCH 0/2] x86/CPU/AMD: Add support for Extended Topology Enumeration
Date: Tue, 27 Mar 2018 08:48:06 +0200	[thread overview]
Message-ID: <20180327064806.dy5updhu7grlct3q@gmail.com> (raw)
In-Reply-To: <1522051559-23415-1-git-send-email-suravee.suthikulpanit@amd.com>


* Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> wrote:

> Linux currently provides function detect_extended_topology()
> for parsing CPUID Fn0xB and derive CPU topology information.
> Therefore, also call this function in AMD code path.
> 
> Thanks,
> Suravee
> 
> Suravee Suthikulpanit (2):
>   x86/CPU: Modify detect_extended_topology() to return result
>   x86/CPU/AMD: Derive CPU topology from CPUID Fn0xB when available
> 
>  arch/x86/include/asm/processor.h |  2 +-
>  arch/x86/kernel/cpu/amd.c        | 16 ++++++++++++----
>  arch/x86/kernel/cpu/topology.c   |  8 ++++----
>  3 files changed, 17 insertions(+), 9 deletions(-)

Which tree is this again? The second patch does not apply to -linus or -tip.

Thanks,

	Ingo

  parent reply	other threads:[~2018-03-27  6:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26  8:05 [PATCH 0/2] x86/CPU/AMD: Add support for Extended Topology Enumeration Suravee Suthikulpanit
2018-03-26  8:05 ` [PATCH 1/2] x86/CPU: Modify detect_extended_topology() to return result Suravee Suthikulpanit
2018-03-26  8:05 ` [PATCH 2/2] x86/CPU/AMD: Derive CPU topology from CPUID Fn0xB Suravee Suthikulpanit
2018-03-27 12:04   ` Suravee Suthikulpanit
2018-03-27  6:48 ` Ingo Molnar [this message]
2018-03-27  6:52   ` [PATCH 0/2] x86/CPU/AMD: Add support for Extended Topology Enumeration David Rientjes
2018-03-27 11:34     ` Suravee Suthikulpanit

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=20180327064806.dy5updhu7grlct3q@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=suravee.suthikulpanit@amd.com \
    --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