On Fri, 2007-09-14 at 02:44 -0400, Mike Frysinger wrote: > On 9/14/07, Bryan Wu <[EMAIL PROTECTED]> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
