mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: David Rientjes <rientjes@google.com>, Ingo Molnar <mingo@kernel.org>
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 18:34:22 +0700	[thread overview]
Message-ID: <f6a804d1-955b-2498-0ec1-c664c4ed843e@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1803262351340.261728@chino.kir.corp.google.com>

Hi All,

On 3/27/18 1:52 PM, David Rientjes wrote:
> On Tue, 27 Mar 2018, Ingo Molnar 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.
>>
> 
> I was wondering the exact same thing today when this came across.  I found
> it's based on Suravee's other patch series posted today entitled "x86/CPU:
> Update AMD Last-Level-Cache Information".
> 
> https://marc.info/?l=linux-kernel&m=152204614503522
> 1522046116-22578-1-git-send-email-suravee.suthikulpanit@amd.com
> 

Sorry for failing to mention the dependency on the other series here
(https://lkml.org/lkml/2018/3/26/24).

Suravee

      reply	other threads:[~2018-03-27 11:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26  8:05 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 ` [PATCH 0/2] x86/CPU/AMD: Add support for Extended Topology Enumeration Ingo Molnar
2018-03-27  6:52   ` David Rientjes
2018-03-27 11:34     ` Suravee Suthikulpanit [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=f6a804d1-955b-2498-0ec1-c664c4ed843e@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=bp@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rientjes@google.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

all inboxes | Powered by JetHome®