Re: Forbid deletion of memory mappings

2007-09-04 Thread Clemens Kolbitsch
> If you are doing research, consider these methods: > 1. Change vma_merge() so it always fail to merge mappings > > or > > 2. Set up your "mappings duplicated in userspace" so > they too merge in the same way. > > Helge Hafting Hi! Thanks for your answer, however you (too) misunderstood: Merg

Re: Copy large memory regions from & to userspace

2007-08-31 Thread Clemens Kolbitsch
On Friday 31 August 2007 15:25:40 you wrote: > On 8/30/07, Clemens Kolbitsch <[EMAIL PROTECTED]> wrote: > > Hi! > > Just a short question: What is the correct method of copying large areas > > of memory from userspace into userspace when running in kernel-mode? > >

Copy large memory regions from & to userspace

2007-08-30 Thread Clemens Kolbitsch
Hi! Just a short question: What is the correct method of copying large areas of memory from userspace into userspace when running in kernel-mode? According to just about any type of documentation out there something like unsigned long *from = 0x0800; unsigned long *to = 0x0900; memcpy(to

Re: Forbid deletion of memory mappings

2007-08-30 Thread Clemens Kolbitsch
On Thursday 30 August 2007 23:50:21 [EMAIL PROTECTED] wrote: > On Thu, 30 Aug 2007 23:41:09 +0200, Clemens Kolbitsch said: > > On Thursday 30 August 2007 23:34:52 you wrote: > > > On Thu, 30 Aug 2007, Clemens Kolbitsch wrote: > > > > is there no way to tell the kerne

Re: Forbid deletion of memory mappings

2007-08-30 Thread Clemens Kolbitsch
On Thursday 30 August 2007 23:34:52 you wrote: > On Thu, 30 Aug 2007, Clemens Kolbitsch wrote: > > is there no way to tell the kernel, that a certain mapping must not be > > removed, no matter what (except of course an explicit call to sys_unmap, > > of course)? > > I do

Re: Forbid deletion of memory mappings

2007-08-30 Thread Clemens Kolbitsch
On Thursday 30 August 2007 19:07:05 you wrote: > On Thu, 30 Aug 2007, Clemens Kolbitsch wrote: > > It all works perfectly well (creating & deleting the additional > > mappings), however, when the kernel feels like it needs to allocate a > > mapping in user-space it sometim

Re: Forbid deletion of memory mappings

2007-08-30 Thread Clemens Kolbitsch
On Thursday 30 August 2007 19:07:05 Jiri Kosina wrote: > On Thu, 30 Aug 2007, Clemens Kolbitsch wrote: > > It all works perfectly well (creating & deleting the additional > > mappings), however, when the kernel feels like it needs to allocate a > > mapping in user-spac

Forbid deletion of memory mappings

2007-08-30 Thread Clemens Kolbitsch
Hi everyone! I have a strange problem where I don't even know if there is a solution to it at the moment: I'm working on a new way of doing memory-management and currently I allocate memory mappings (at non-fixed locations) in user-memory (i.e. < TASK_SIZE) in addition to the regular pages mapp

Re: user-mode stack size & location

2007-08-28 Thread Clemens Kolbitsch
> hi, > > if you look where arch_align_stack() gets called.. that's where you > want to look. arch_align_stack() gets invoked in code that selects > userspace stack pointers > > Greetings, >Arjan van de Ven thanks a lot!! - To unsubscribe from this list: send the line "unsubscribe linux-k

user-mode stack size & location

2007-08-28 Thread Clemens Kolbitsch
hi! i'm working on a new concept of i386 memory management and have to change quite a bit of the linux mm. could someone please point out, where the location & size of the USER-MODE stack is set for a new program (i.e. after calling sys_execve...) exactly? I know that all settings are simply co