From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Matheus Castanho <msc@linux.ibm.com>, libc-alpha@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH v2 1/2] powerpc: Runtime selection between sc and scv for syscalls
Date: Thu, 10 Dec 2020 15:07:22 -0300 [thread overview]
Message-ID: <3d30f314-9ef1-dcfa-3a22-37069e7d2d9b@linaro.org> (raw)
In-Reply-To: <0c37d169-bcd4-9fa3-d9bf-9b72ffccb895@linux.ibm.com>
On 10/12/2020 14:28, Matheus Castanho wrote:
> Hi Florian an Adhemerval,
>
> I was able to get rid of the thread pointer check, leaving it only on libc.a, and the DL
> is using the old interface (sc insn). Do you have further comments?
>
> On 12/3/20 2:15 PM, Matheus Castanho via Libc-alpha wrote:
>> This patch depends on the brk consolidation implemented by [0].
>>
>> [0] https://sourceware.org/pipermail/libc-alpha/2020-November/119770.html
>>
>
> [...]
>
> Adhemerval, do you plan to merge this patch (with the change suggested by Tulio)
> in this release? I see it already has a Reviewed-by.
>
> I'd like to try to merge this change before the freeze, but it depends on that patch
> now.
>
> Thanks,
> Matheus Castanho
>
I will do it, thanks for remind me.
next prev parent reply other threads:[~2020-12-10 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 17:15 [PATCH v2 0/2] powerpc: Add support for system call vectored Matheus Castanho
2020-12-03 17:15 ` [PATCH v2 1/2] powerpc: Runtime selection between sc and scv for syscalls Matheus Castanho
2020-12-10 17:28 ` Matheus Castanho
2020-12-10 18:07 ` Adhemerval Zanella [this message]
2020-12-30 21:29 ` Tulio Magno Quites Machado Filho
2020-12-03 17:15 ` [PATCH v2 2/2] powerpc: Use scv instruction on clone when available Matheus Castanho
2020-12-30 21:30 ` Tulio Magno Quites Machado Filho
2020-12-08 18:24 ` [PATCH v2 0/2] powerpc: Add support for system call vectored Lucas A. M. Magalhaes
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=3d30f314-9ef1-dcfa-3a22-37069e7d2d9b@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=msc@linux.ibm.com \
/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).