All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: liqin.chen@sunplusct.com
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: [GIT PULL, v4] S+core architecture (arch/score) support
Date: Mon, 31 Aug 2009 09:56:33 +0000	[thread overview]
Message-ID: <200908310956.33802.arnd@arndb.de> (raw)
In-Reply-To: <OF0579E5F2.3B710FBD-ON48257623.002611FB-48257623.002B92AD@sunplusct.com>

On Monday 31 August 2009 07:48:33 liqin.chen@sunplusct.com wrote:
> Arnd Bergmann <arnd@arndb.de> 写于 2009-08-27 22:00:37:
> 
> > 
> > I understand your problem here, and I think it would be good
> > to have second opinion from someone else here. The four
> > #defines you mention are roughly in reverse order of importance.
> > 
> > I think you really need to remove __ARCH_WANT_SYSCALL_DEPRECATED
> > and get that working. Please tell us if some system call is
> > giving you problems and we can find a solution together.
> > 
> > Removing __ARCH_WANT_SYSCALL_OFF_T should not be too hard, because
> > glibc uses the loff_t versions by default anyway. I have not tried
> > it though, so it may be more complicated than I thought.
> > 
> 
> in __ARCH_WANT_SYSCALL_DEPRECATED,
> asm-generic/unistd.h haven't define __NR_ipc and __NR__llseek
> which used in glibc.

__NR_ipc definitely should not be defined, it is a multiplexer
for other system calls that have their own number, e.g. msgctl
and semop. Look at e.g. how parisc does it in glibc.

I'm not sure what the problem with __NR_llseek could be, AFAICT
it is defined in asm-generic/unistd.h because you take the
default __BITSPERLONG=32 definition. You should however not
see __NR_lseek, which is used only on 64 bit systems these days.

> Now we have maintained 3 sets of syscall API code use for glibc.
> 1: Old syscall interface, which linux/score system work well.

Yes, and I guess this will continue to work, but it will never
work with upstream kernels.

> 2: New syscall interface, define all 4 macro __ARCH_WANT_SYSCALL_XXX,
>         linux/score system work now, but we still debug the glibc code.
> 3: New syscall interface, without define __ARCH_WANT_SYSCALL_DEPRECATED
>         and __ARCH_WANT_SYSCALL_OFF_T, linux/score system couldn't work.
>         because glibc have many place need to fix.

Do you have a patch against the glibc git tree for score so I can look
at what needs to be done? None of the changes should be specific to
score after all, ideally it should all work without any glibc changes,
though I realize that we are not there yet.

	Arnd <><

  reply	other threads:[~2009-08-31  9:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26  5:58 [GIT PULL, v4] S+core architecture (arch/score) support Chen Liqin (Gmail)
2009-08-26 17:31 ` Arnd Bergmann
2009-08-27  3:28   ` Chen Liqin
2009-08-27 14:00     ` Arnd Bergmann
2009-08-31  7:48       ` liqin.chen
2009-08-31  7:48         ` liqin.chen
2009-08-31  9:56         ` Arnd Bergmann [this message]
2009-09-01  6:45           ` liqin.chen
2009-09-01  6:45             ` liqin.chen
  -- strict thread matches above, loose matches on Subject: below --
2009-09-14  1:27 liqin.chen
2009-09-17 16:31 ` Linus Torvalds
2009-09-18  4:10   ` liqin.chen
2009-09-18  4:10     ` liqin.chen
2009-09-18  4:36     ` Linus Torvalds

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=200908310956.33802.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liqin.chen@sunplusct.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.