linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
	liqin.chen@sunplusct.com, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: What's in asm-generic.git
Date: Fri, 11 Dec 2009 13:54:01 +0100	[thread overview]
Message-ID: <10f740e80912110454u172fc2cfye30da6ca0e0f0af0@mail.gmail.com> (raw)
In-Reply-To: <200912102225.05280.arnd@arndb.de>

On Thu, Dec 10, 2009 at 22:25, Arnd Bergmann <arnd@arndb.de> wrote:
> On Thursday 10 December 2009, Mike Frysinger wrote:
>> > I have found now that sys_accept4 was missing. sys_set_thread_area however
>> > is only defined on x86 and mips. Since you don't currently implement this
>> > on score, maybe it would be more appropriate to handle it like the other
>> > architectures do, rather than adding it to asm-generic/unistd.h?
>>
>> isnt the point of asm-generic/unistd.h to collect all common syscalls
>> ?  if there's syscalls that ideally should be handled by everyone but
>> currently doesnt, then it's easy to define it in the header but have
>> the actual entry.S leave it as a hole ...
>
> Well, sys_thread_area is not a common syscall but rather an exception.
> I haven't looked at how glibc does implents TLS on different architectures,
> but I think this is commonly done purely in user space without the
> need for a syscall.

10+ architectures already have sys_[sg]et_thread_area of have reserved
entries for it.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2009-12-11 12:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 19:14 What's in asm-generic.git Arnd Bergmann
2009-12-07  5:54 ` liqin.chen
2009-12-07 15:14   ` Arnd Bergmann
2009-12-07 15:14     ` Arnd Bergmann
2009-12-10 21:10     ` Arnd Bergmann
2009-12-10 21:17       ` Mike Frysinger
2009-12-10 21:17         ` Mike Frysinger
2009-12-10 21:25         ` Arnd Bergmann
2009-12-11 12:54           ` Geert Uytterhoeven [this message]
2009-12-11 13:06             ` Arnd Bergmann
2009-12-11 13:58               ` Geert Uytterhoeven

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=10f740e80912110454u172fc2cfye30da6ca0e0f0af0@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liqin.chen@sunplusct.com \
    --cc=vapier.adi@gmail.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 NNTP newsgroup(s).