From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, bp@suse.de,
peterz@infradead.org, Yazen.Ghannam@amd.com,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: [PATCH v4 0/2] x86/amd: Refactor and fixup family17h cpu_core_id
Date: Mon, 24 Jul 2017 04:22:43 -0500 [thread overview]
Message-ID: <1500888165-2345-1-git-send-email-suravee.suthikulpanit@amd.com> (raw)
Changes from V3 (https://lkml.org/lkml/2017/7/24/2)
* Use a cleaner version of refactor patch 1/2 from Boris instead.
Changes from V2 (https://lkml.org/lkml/2017/7/21/730)
* In patch 1/2
* Fix kbuild error for the __get_topoext() due to #ifdef CONFIG_SMP.
* Do not move node_id declaration in the refactored function.
Changes from V1 (https://lkml.org/lkml/2017/7/20/180)
* Refactor topology extension logic into __get_topoext() (per Boris)
Borislav Petkov (1):
x86/amd: Refactor topology extension related code
Suravee Suthikulpanit (1):
x86/amd: Fixup cpu_core_id for family17h downcore configuration
arch/x86/kernel/cpu/amd.c | 110 ++++++++++++++++++++++++++++++++--------------
1 file changed, 77 insertions(+), 33 deletions(-)
--
2.7.4
next reply other threads:[~2017-07-24 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 9:22 Suravee Suthikulpanit [this message]
2017-07-24 9:22 ` [PATCH v4 1/2] x86/amd: Refactor topology extension related code Suravee Suthikulpanit
2017-07-24 9:22 ` [PATCH v4 2/2] x86/amd: Fixup cpu_core_id for family17h downcore configuration Suravee Suthikulpanit
2017-07-24 11:14 ` Borislav Petkov
2017-07-24 14:14 ` Suravee Suthikulpanit
2017-07-24 14:44 ` Borislav Petkov
2017-07-25 5:51 ` Suravee Suthikulpanit
2017-07-25 5:56 ` Borislav Petkov
2017-07-25 6:02 ` Suravee Suthikulpanit
2017-07-25 8:07 ` Borislav Petkov
2017-07-28 9:39 ` Andreas Herrmann
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=1500888165-2345-1-git-send-email-suravee.suthikulpanit@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Yazen.Ghannam@amd.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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®