From: Rajalakshmi Srinivasaraghavan <rajis@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 1/2] powerpc: Add space for HWCAP3/HWCAP4 in the TCB for future Power.
Date: Thu, 14 Dec 2023 17:05:07 -0600 [thread overview]
Message-ID: <6d3380a5-8f92-42d4-8d8c-0736a0a1d84f@linux.vnet.ibm.com> (raw)
In-Reply-To: <c0f58c75-fab7-4809-9368-0069564e8b8f@linux.ibm.com>
On 12/13/23 5:45 PM, Peter Bergner wrote:
> On 12/5/23 6:38 AM, Manjunath Matti wrote:
>> This patch reserves space for HWCAP3/HWCAP4 in the TCB of powerpc.
>> These hardware capabilities bits will be used by future Power
>> architectures.
>>
>> Versioned symbol '__parse_hwcap_3_4_and_convert_at_platform' advertises
>> the availability of the new HWCAP3/HWCAP4 data in the TCB.
>>
>> This is an ABI change for GLIBC 2.39.
>>
>> Suggested-by: Peter Bergner <bergner@linux.ibm.com>
>> ---
>> sysdeps/powerpc/Versions | 5 +++++
>> sysdeps/powerpc/hwcapinfo.c | 5 +++++
>> sysdeps/powerpc/nptl/tcb-offsets.sym | 1 +
>> sysdeps/powerpc/nptl/tls.h | 13 ++++++++++++-
>> .../unix/sysv/linux/powerpc/powerpc32/ld.abilist | 1 +
>> .../unix/sysv/linux/powerpc/powerpc64/be/ld.abilist | 1 +
>> .../unix/sysv/linux/powerpc/powerpc64/le/ld.abilist | 1 +
>> 7 files changed, 26 insertions(+), 1 deletion(-)
> LGTM.
>
> Reviewed-by: Peter Bergner <bergner@linux.ibm.com>
>
> Peter
Thanks Peter for the review. I will merge the first patch.
Since the second patch depends on the kernel patch, we can review and
merge that later.
prev parent reply other threads:[~2023-12-14 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 12:38 [PATCH v2 1/2] powerpc: Add space for HWCAP3/HWCAP4 in the TCB for future Power Manjunath Matti
2023-12-05 12:38 ` [PATCH v2 2/2] powerpc: Add HWCAP3/HWCAP4 data to TCB for Power Architecture Manjunath Matti
2023-12-13 23:47 ` Peter Bergner
2024-03-19 23:50 ` Peter Bergner
2023-12-13 23:45 ` [PATCH v2 1/2] powerpc: Add space for HWCAP3/HWCAP4 in the TCB for future Power Peter Bergner
2023-12-14 23:05 ` Rajalakshmi Srinivasaraghavan [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6d3380a5-8f92-42d4-8d8c-0736a0a1d84f@linux.vnet.ibm.com \
--to=rajis@linux.vnet.ibm.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).