From: Dave Hansen <haveblue@us.ibm.com>
To: "Hanson, Jonathan M" <jonathan.m.hanson@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Figuring out physical memory regions from a kernel module
Date: Wed, 08 Dec 2004 13:38:28 -0800 [thread overview]
Message-ID: <1102541907.883.18.camel@localhost> (raw)
In-Reply-To: <C863B68032DED14E8EBA9F71EB8FE4C20596063B@azsmsx406>
On Wed, 2004-12-08 at 13:26, Hanson, Jonathan M wrote:
> [Jon M. Hanson] Even looking at the implementation of the crashdump
> code, I still encounter the same problem I've run into up until now: the
> crashdump code is a part of the kernel so it has access to all of the
> kernel's data structures and functions; as a kernel module, I'm
> hamstrung by what is exported by the kernel. I know that I can modify
> the kernel to export whatever I want but I don't want to have to do
> that. I want to be able to run my kernel module without having to patch
> the kernel itself.
There's some design effort not to expose kernel *internals* to modules.
Seems like your module requirements are different from the current
design direction of the kernel.
-- Dave
next prev parent reply other threads:[~2004-12-08 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 21:26 Figuring out physical memory regions from a kernel module Hanson, Jonathan M
2004-12-08 21:38 ` Dave Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 18:28 Hanson, Jonathan M
2004-12-08 18:40 ` Dave Hansen
2004-12-08 17:54 Hanson, Jonathan M
2004-12-08 17:44 Hanson, Jonathan M
2004-12-08 17:50 ` Arjan van de Ven
2004-12-08 17:57 ` Dave Hansen
2004-12-09 6:25 ` Vivek Goyal
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=1102541907.883.18.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=jonathan.m.hanson@intel.com \
--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.