From: "Duran, Leo" <leo.duran@amd.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH v4 0/2] UefiCpuPkg: Add CPUID support for AMD.
Date: Tue, 1 Aug 2017 19:32:06 +0000 [thread overview]
Message-ID: <DM5PR12MB1243BFC1074147584E005686F9B30@DM5PR12MB1243.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1497653820-15192-1-git-send-email-leo.duran@amd.com>
> -----Original Message-----
> From: Duran, Leo
> Sent: Friday, June 16, 2017 5:57 PM
> To: edk2-devel@lists.01.org
> Cc: Duran, Leo <leo.duran@amd.com>
> Subject: [PATCH v4 0/2] UefiCpuPkg: Add CPUID support for AMD.
Please ignore this PATCH v4.
PATCH v3 of this series has been merged upstream:
commit 061ead7a2dcc ("UefiCpuPkg: Modify GetProcessorLocationByApicId() to support AMD.").
I will push a new patch today that incorporates cleanups from PATCH v4,
and provide enhanced functionality.
Leo.
>
> This patch-set requires and builds upon this submission:
> https://lists.01.org/pipermail/edk2-devel/2017-May/010867.html
>
> Changes since v3:
> - Check AMD signature before checking CPUID_Fn8000_001E.
>
> Changes since v2:
> - Account for actual thread count (e.g., SMT disabled).
>
> Changes since v1:
> - Revert to (MaxCoresPerPackage = 1) when CPUID is not explicit.
>
> Leo Duran (2):
> UefiCpuPkg: Add CPUID definitions for AMD.
> UefiCpuPkg: Modify GetProcessorLocationByApicId() to support AMD.
>
> UefiCpuPkg/Include/Register/Amd/Cpuid.h | 599
> ++++++++++++++++++++-
> UefiCpuPkg/Library/BaseXApicLib/BaseXApicLib.c | 140 +++--
> .../BaseXApicX2ApicLib/BaseXApicX2ApicLib.c | 140 +++--
> 3 files changed, 806 insertions(+), 73 deletions(-)
>
> --
> 2.7.4
prev parent reply other threads:[~2017-08-01 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 22:56 [PATCH v4 0/2] UefiCpuPkg: Add CPUID support for AMD Leo Duran
2017-06-16 22:56 ` [PATCH v4 1/2] UefiCpuPkg: Add CPUID definitions " Leo Duran
2017-06-16 22:57 ` [PATCH v4 2/2] UefiCpuPkg: Modify GetProcessorLocationByApicId() to support AMD Leo Duran
2017-08-01 19:32 ` Duran, Leo [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-list 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=DM5PR12MB1243BFC1074147584E005686F9B30@DM5PR12MB1243.namprd12.prod.outlook.com \
--to=devel@edk2.groups.io \
/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