All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Pokam <gpokam@gmail.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel memory
Date: Thu, 28 Apr 2005 22:48:31 -0700	[thread overview]
Message-ID: <ba8358220504282248344d5e78@mail.gmail.com> (raw)
In-Reply-To: <20050429054351.GA12654@taniwha.stupidest.org>

On 4/28/05, Chris Wedgwood <cw@f00f.org> wrote:
> On Thu, Apr 28, 2005 at 10:33:16PM -0700, Gilles Pokam wrote:
> 
> > I was thinking of making the whole memory accessible to handle this.
> > But I can not rely on mapping /dev/mem or /proc/kcore into the user
> > space since this would require modifying the binary. Are there other
> > ways of doing this ? May be disabling paging ? if so, how to do this
> > ?
> 
> why can't you use a wrapper?

Can you be more explicit ?

Thanks.

Gilles

  reply	other threads:[~2005-04-29  5:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 23:52 Kernel memory Gilles Pokam
2005-04-29  3:03 ` Chris Wedgwood
2005-04-29  5:33   ` Gilles Pokam
2005-04-29  5:43     ` Chris Wedgwood
2005-04-29  5:48       ` Gilles Pokam [this message]
2005-04-29  6:12         ` Chris Wedgwood
2005-04-29  6:45           ` Gilles Pokam
2005-04-29  6:48             ` Chris Wedgwood
2005-04-29  7:12               ` Gilles Pokam
  -- strict thread matches above, loose matches on Subject: below --
2012-06-21 12:27 Kernel Memory Vijay Chauhan
2012-06-21 13:35 ` HowKernel StuffWorks
2012-06-21 13:40 ` kishore sheik ahamed
2012-06-22 18:23   ` Vijay Chauhan
2012-06-21 13:44 ` Arun KS
2012-06-21 14:02 ` AFT
2012-06-21 15:48 ` michi1 at michaelblizek.twilightparadox.com
2016-05-17  7:11 Kernel memory Ronit Halder
2016-05-17 15:05 ` Valdis.Kletnieks at vt.edu

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=ba8358220504282248344d5e78@mail.gmail.com \
    --to=gpokam@gmail.com \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.