linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@analog.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: bryan.wu@analog.com, Bernd Schmidt <bernds_cb1@t-online.de>,
	bernd.schmidt@analog.com, linux-arch@vger.kernel.org,
	Matthew Wilcox <matthew@wil.cx>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Paul Mundt <lethal@linux-sh.org>,
	uclinux-dist-devel@blackfin.uclinux.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Uclinux-dist-devel] Re: [PATCH] Blackfin arch: add some missing syscall
Date: Fri, 14 Sep 2007 15:32:28 +0800	[thread overview]
Message-ID: <1189755148.8165.15.camel@roc-desktop> (raw)
In-Reply-To: <8bd0f97a0709132344w136f2df5ncfe4496c6c895bd8@mail.gmail.com>

On Fri, 2007-09-14 at 02:44 -0400, Mike Frysinger wrote:
> On 9/14/07, Bryan Wu <bryan.wu@analog.com> wrote:
> > On Thu, 2007-09-13 at 13:03 +0200, Bernd Schmidt wrote:
> > > Bryan Wu wrote:
> > > >>> but mremap doesn't -- there's even an implementation in mm/nommu.c.
> > > >>> Could you check the rest of these over to see if they truly don't need
> > > >>> to be implemented for no-mmu?
> > > >> you're right we want mremap, my fault
> > > >>
> > > >
> > > > Yes, I do think so, both sys_mremap and sys_munmap are implemented in
> > > > mm/nommu.c. How do think of this, Bernd?
> > >
> > > There's a mremap in nommu.c, but it doesn't do a lot that is useful.
> > > With some further mm changes in our tree, it's little more than a fancy
> > > way of saying munmap, and uClibc does not use it, so there's no
> > > compelling need to have it in userspace.
> >
> > Make sense. So currently Blackfin uClinux use the mremap/munmap in
> > uClibc?
> 
> most functions like this dont have any real libc component ... uClibc
> will define userspace symbols that merely make a syscall iff the __NR_
> exists in the headers
> 
> if we have __NR_mremap in our unistd.h, we'll automagically get the
> mremap() symbol in uClibc which simply passes along the args to the
> kernel

Yes, I know this. But currently, __NR_mremap does not exit in Blackfin
unistd.h:
/* 163 __NR_mremap */.

So the implementation of this kind syscalls should be in uClibc, right?

And Bernd said that the kernel version mremap/munmap is not very useful
for Blackfin arch. I think mremap/munmap can be ignored in Blackfin.

Thanks
-Bryan

  reply	other threads:[~2007-09-14  7:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13  7:56 [PATCH] Blackfin arch: add some missing syscall Bryan Wu
2007-09-13  8:07 ` Paul Mundt
2007-09-13  8:09   ` Paul Mundt
2007-09-13  8:18 ` Matthew Wilcox
2007-09-13  8:37   ` Mike Frysinger
2007-09-13  8:57     ` Bryan Wu
2007-09-13 11:03       ` [Uclinux-dist-devel] " Bernd Schmidt
2007-09-14  5:45         ` Bryan Wu
2007-09-14  6:44           ` Mike Frysinger
2007-09-14  7:32             ` Bryan Wu [this message]
2007-09-15  1:28               ` Mike Frysinger
2007-09-13  8:47   ` Paul Mundt

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=1189755148.8165.15.camel@roc-desktop \
    --to=bryan.wu@analog.com \
    --cc=akpm@linux-foundation.org \
    --cc=bernd.schmidt@analog.com \
    --cc=bernds_cb1@t-online.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --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).