From: Guan Xuetao <gxt@mprc.pku.edu.cn>
To: "Linas Vepstas (Code Aurora)" <linas@codeaurora.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
GLIBC Devel <libc-alpha@sourceware.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Jonas Bonn <jonas.bonn@gmail.com>,
libc-ports@sourceware.org, linux-hexagon@vger.kernel.org,
linux-arch@vger.kernel.org,
Mark Salter <msalter@redhat.com>,
Tobias Klauser <tklauser@distanz.ch>
Subject: Re: __ARCH_WANT_SYSCALL_DEPRECATED
Date: Thu, 25 Aug 2011 02:33:00 -0000 [thread overview]
Message-ID: <1314239622.29738.53.camel@epip-laptop> (raw)
In-Reply-To: <20110824152537.GA3993@codeaurora.org>
On Wed, 2011-08-24 at 10:25 -0500, Linas Vepstas (Code Aurora) wrote:
> On Wed, Aug 24, 2011 at 10:01:24AM +0800, Guan Xuetao wrote:
> > For getdents (or other deprecated syscalls), we select getdents64 to
> > replace getdent, though we have not verified it on unicore32 platform.
>
> Do you have a publically-available version? Have you considered
> submitting it to the FSF? Have you signed the copyright-transfer
> forms with the FSF?
Firstly, what I said for getdents64 in unicore is just in developing,
not ready yet.
And for glibc part, it need much time to prepare for submitting.
>
> My goal with the hexagon archiecture is to have the kernel asm/unistd.h
> include asm-generic/unistd.h, and have glibc compile (on hexagon) with
> no further #defines in asm/unistd.h. This "almost" works today; with
> Chris Metcalf's generic syscall patches for glibc, I am able to compile
> glibc (and pass the glibc test suite). However, I have to #define
> __ARCH_WANT_SYSCALL_DEPRECATED to do this. If I don't, then the
> getdents syscall fails to compile; I don't know how many others there are.
It's also my goal. And you have walked further than me.
I guess, Chris don't need getdent for tile, since he didn't export the
syscall in kernel.
IMO, it's better to add one syscall instead of
__ARCH_WANT_SYSCALL_DEPRECATED in your own unistd.h:
#define __NR_getdents 1065
#define __ARCH_WANT_SYS_GETDENTS
__SYSCALL(__NR_getdents, sys_getdents)
>
> As to the "API": I just want to use Arnd's "generic" kernel support;
> that will be the API. No changing, porting, hacking :-)
>
> -- Linas
>
Regards
Guan Xuetao
next prev parent reply other threads:[~2011-08-25 2:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 19:36 __ARCH_WANT_SYSCALL_DEPRECATED Linas Vepstas (Code Aurora)
2011-08-22 20:44 ` __ARCH_WANT_SYSCALL_DEPRECATED Arnd Bergmann
2011-08-24 2:01 ` __ARCH_WANT_SYSCALL_DEPRECATED Guan Xuetao
2011-08-24 15:26 ` __ARCH_WANT_SYSCALL_DEPRECATED Linas Vepstas (Code Aurora)
2011-08-25 2:33 ` Guan Xuetao [this message]
2011-08-26 2:57 ` __ARCH_WANT_SYSCALL_DEPRECATED Chris Metcalf
2011-08-29 11:33 ` __ARCH_WANT_SYSCALL_DEPRECATED Tobias Klauser
2011-08-29 15:22 ` __ARCH_WANT_SYSCALL_DEPRECATED Joseph S. Myers
2011-08-29 16:19 ` __ARCH_WANT_SYSCALL_DEPRECATED Tobias Klauser
2011-08-22 22:11 ` __ARCH_WANT_SYSCALL_DEPRECATED Joseph S. Myers
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=1314239622.29738.53.camel@epip-laptop \
--to=gxt@mprc.pku.edu.cn \
--cc=arnd@arndb.de \
--cc=cmetcalf@tilera.com \
--cc=jonas.bonn@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=linas@codeaurora.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=tklauser@distanz.ch \
/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).