Re: linux syscall madvise

2010-01-06 Thread Alex Hornung
Sure, but point is that this won't fix much. You can, if you want to,
submit a patch with the relevant code, it's straight forward.
Main aim still remains to get LTP running, so all missing syscalls,
most of them way more important than madvise, can be identified.

Thanks for your effort,
Alex Hornung

2010/1/5 Pierre Abbat p...@phma.optus.nu:
 On Tuesday 05 January 2010 12:56:43 Alex Hornung wrote:
 madvise is of no real relevance and is normally not a big deal either.
 Implementing an empty dummy function will work perfectly fine as it
 isn't required to do anything.

 True, but there is a madvise in DFly, so the Linux call can be implemented as
 the DFly call for the functions they both have, and dummy for the rest.

 Pierre

 --
 .i toljundi do .ibabo mi'afra tu'a do
 .ibabo damba do .ibabo do jinga
 .icu'u la ma'atman.



Re: linux syscall madvise

2010-01-05 Thread Alex Hornung
madvise is of no real relevance and is normally not a big deal either.
Implementing an empty dummy function will work perfectly fine as it
isn't required to do anything.

Cheers,
Alex Hornung

2010/1/4 Pierre Abbat p...@phma.optus.nu:
 I haven't managed to get ltp running, but I have run some Linux programs. I
 get this message in dmesg:

 linux: syscall madvise is obsoleted or not implemented

 This call is used to tell the kernel what the program plans to do with a
 region of memory. Values used in Linux but not BSD, according to the man
 pages, are:
 MADV_REMOVE: seems to mean the same as MADV_FREE
 MADV_DONTFORK: when fork() is next called, the child will not inherit the
 memory
 MADV_DOFORK: opposite of MADV_DONTFORK

 Pierre
 --
 li ze te'a ci vu'u ci bi'e te'a mu du
 li ci su'i ze te'a mu bi'e vu'u ci



Re: linux syscall madvise

2010-01-05 Thread Pierre Abbat
On Tuesday 05 January 2010 12:56:43 Alex Hornung wrote:
 madvise is of no real relevance and is normally not a big deal either.
 Implementing an empty dummy function will work perfectly fine as it
 isn't required to do anything.

True, but there is a madvise in DFly, so the Linux call can be implemented as 
the DFly call for the functions they both have, and dummy for the rest.

Pierre

-- 
.i toljundi do .ibabo mi'afra tu'a do
.ibabo damba do .ibabo do jinga
.icu'u la ma'atman.


linux syscall madvise

2010-01-04 Thread Pierre Abbat
I haven't managed to get ltp running, but I have run some Linux programs. I 
get this message in dmesg:

linux: syscall madvise is obsoleted or not implemented

This call is used to tell the kernel what the program plans to do with a 
region of memory. Values used in Linux but not BSD, according to the man 
pages, are:
MADV_REMOVE: seems to mean the same as MADV_FREE
MADV_DONTFORK: when fork() is next called, the child will not inherit the 
memory
MADV_DOFORK: opposite of MADV_DONTFORK

Pierre
-- 
li ze te'a ci vu'u ci bi'e te'a mu du
li ci su'i ze te'a mu bi'e vu'u ci