From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Steve Ellcey <sellcey@caviumnetworks.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v3 00/17] Consolidate Linux sysvipc implementation
Date: Fri, 09 Dec 2016 20:18:00 -0000 [thread overview]
Message-ID: <4420709d-82a0-8a94-5b35-cc498db52a37@linaro.org> (raw)
In-Reply-To: <1481308253.29811.77.camel@caviumnetworks.com>
On 09/12/2016 16:30, Steve Ellcey wrote:
> On Wed, 2016-12-07 at 17:13 -0200, Adhemerval Zanella wrote:
>> Ping x2.
>>
>>> On 08/11/2016 18:29, Adhemerval Zanella wrote:
>>>>
>>>> Changes from previous version:
>>>>
>>>> - Refactor ipc_priv.h header to have working definition for all
>>>> architectures. The header basically contains Linux specific
>>>> ABI definitions for the architecture to correctly use default
>>>> implementation, including old ipc_perm definition, calling
>>>> convention, and __IPC_64 value.
>>>>
>>>> - Set all architectures to use the default implementation. It
>>>> leaded to some code changes to accomodate all the
>>>> architectures
>>>> calling convention (with ipc_priv.h change) and some fixes
>>>> on new default implementation.
>>>>
>>>> - Change mips64 implementation way to use the default one.
>>>>
>>>> - Some tests changes (name typos).
>>>>
>>>> --
>
> Adhemerval,
>
> It looks like you may have to tweek your change to test-skeleton.c in
> this patch. The FAIL_EXIT macro was moved from test-skeleton.c
> to support/check.h so I assume your new FAIL_UNSUPPORTED macro should
> be moved there as well.
Yes, I did not rebase against new source changes and looks like I will
need to do so. And it is worth a v4, so I will send it a new set for
review.
>
> I have been doing aarch64 and x86 builds here with your patch and have
> not had any problems except with my new aarch64 ILP32 code. There I
> had to change the definition of __IPC_64 in the new header
> file sysdeps/unix/sysv/linux/aarch64/ipc_priv.h from:
>
> #define __IPC_64 0x0
>
> to:
>
> #ifdef __LP64__
> # define __IPC_64 0x0
> #else /* __ILP32 */
> # define __IPC_64 0x100
> #endif
>
> I don't know if that is something that you want to incorporate into
> your patch or if I should leave it as part of my overall aarch64 ILP32
> patch. Right now it is hard to include it in my patch since that
> header file isn't in the official sources yet (being a new file in your
> patch).
If this is the correct value for ILP32 I will add, but from Arnd reply
it might an issue with your kernel config.
>
> Hopefully someone will approve your patch soon and then I can just
> build my patch on ToT instead of having to also include your patch.
> I don't see any other problems with your patch myself but I am not that
> familiar with this part of glibc so I would like to see someone else
> review/approve this patch before you check it in but I would also like
> to see it checked in soon so that I can move ahead with my aarch64
> ILP32 patches before we get too close to the GLIBC 2.25 cutoff date.
My idea is to push this next week to avoid issues with cutoff date.
>
> Steve Ellcey
> sellcey@caviumnetworks.com
>
prev parent reply other threads:[~2016-12-09 20:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 20:30 Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 04/17] Consolidate Linux msgrcv implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 03/17] Consolidate Linux msgctl implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 01/17] Add __ASSUME_SYSVIPC_SYSCALL for Linux Adhemerval Zanella
2016-11-08 21:19 ` Andreas Schwab
2016-11-09 13:23 ` Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 12/17] Add SYSV semaphore test Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 11/17] Consolidate Linux semtimedop implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 13/17] Use shmat syscall for Linux implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 15/17] Use shmdt syscall for linux implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 02/17] Refactor Linux ipc_priv header Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 10/17] Use semop syscall for Linux implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 05/17] Use msgsnd " Adhemerval Zanella
2016-11-08 21:13 ` Andreas Schwab
2016-11-09 13:23 ` Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 14/17] Consolidate Linux shmctl implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 09/17] Use semget syscall for Linux implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 17/17] Add SYSV shared memory test Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 07/17] Add SYSV message queue test Adhemerval Zanella
2016-11-08 21:23 ` Andreas Schwab
2016-11-09 13:28 ` Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 16/17] Use shmget syscall for linux implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 08/17] Consolidate Linux semctl implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 06/17] Use msgget syscall for Linux implementation Adhemerval Zanella
2016-11-09 13:57 ` [PATCH v3 00/17] Consolidate Linux sysvipc implementation Yury Norov
2016-11-25 14:02 ` Adhemerval Zanella
2016-12-07 19:14 ` Adhemerval Zanella
2016-12-09 18:31 ` Steve Ellcey
2016-12-09 20:04 ` Arnd Bergmann
2017-01-05 20:57 ` Yury Norov
2016-12-09 20:18 ` Adhemerval Zanella [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=4420709d-82a0-8a94-5b35-cc498db52a37@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=sellcey@caviumnetworks.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).