public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: wind-lkml@cocodriloo.com
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: wind-lkml@cocodriloo.com, Alex Tomas <bzzz@tmi.comex.ru>,
	riel@surriel.com, akpm@digeo.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4 vm, program load, page faulting, ...
Date: Mon, 17 Mar 2003 20:06:36 +0100	[thread overview]
Message-ID: <20030317190636.GD11526@wind.cocodriloo.com> (raw)
In-Reply-To: <200303171957.49233.m.c.p@wolk-project.de>

On Mon, Mar 17, 2003 at 07:57:49PM +0100, Marc-Christian Petersen wrote:
> On Monday 17 March 2003 18:38, wind-lkml@cocodriloo.com wrote:
> 
> Hi Wind,
> 
> > > I wonder if this could be done by walking and faulting
> > > all pages at fs/binfmt_elf.c::elf_map just after do_mmap...
> > > will try it just now :)
> >
> > OK, this is not tested, since I'm compiling it now... feel free
> > to correct :)
> 
> mm/mmap.c:
> 
> unsigned long do_mmap_pgoff(struct file * file, unsigned long addr, unsigned 
> long len,
>         unsigned long prot, unsigned long flags, unsigned long pgoff)
> {
> 
> your "do_mmap_pgoff" calls 7 arguments. Obviously it cannot compile 8-)
> 

My first patch, I'm just becoming intimate with printk ;)


  reply	other threads:[~2003-03-17 18:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-16  4:59 2.4 vm, program load, page faulting, Paul Albrecht
2003-03-17 15:02 ` Rik van Riel
2003-03-17 15:10   ` William Lee Irwin III
2003-03-17 16:01     ` Rik van Riel
2003-03-17 16:52       ` wind
2003-03-17 16:50         ` Alex Tomas
2003-03-17 17:12           ` wind-lkml
2003-03-17 17:38             ` wind-lkml
2003-03-17 18:57               ` Marc-Christian Petersen
2003-03-17 19:06                 ` wind-lkml [this message]
2003-03-17 19:34                   ` wind
2003-03-17 22:05           ` Andrew Morton
2003-03-17 23:08             ` wind
2003-03-17 23:28               ` Andrew Morton
2003-03-18  0:12                 ` wind
2003-03-17 16:37     ` Alex Tomas
2003-03-18  7:43   ` Paul Albrecht

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=20030317190636.GD11526@wind.cocodriloo.com \
    --to=wind-lkml@cocodriloo.com \
    --cc=akpm@digeo.com \
    --cc=bzzz@tmi.comex.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    --cc=riel@surriel.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