linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Paulson <epaulson@students.wisc.edu>
To: linux-kernel@vger.kernel.org
Subject: Exporting access_process_vm
Date: Sun, 03 Dec 2000 21:39:52 -0600	[thread overview]
Message-ID: <200012040339.VAA43998@mail5.doit.wisc.edu> (raw)

Hi,
	Back in September, David Howells sent in a one-line patch that just
exported
access_process_vm. It doesn't seem to have been applied, and there was no
discussion of it. 

Was it simply overlooked, or was there a good reason not to apply it and no
one
ever replied to the list about it? 

I'm dragging some checkpointing code into the Wonderful World of Linux 2.4,
and it'd
be great if I could chuck all the scary
walk-the-page-tables-and-hope-it-works
code that's currently in there with more modern stuff. 

Thanks!

-Erik

This was the original message: (I can re-create the "patch" against the
current
release, but it seemed straight-forward enough :)

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Could you please apply this little patch to export access_process_vm()?

Cheers,
David Howells
=============

diff -uNr linux-2.4.0-test8-orig/kernel/ksyms.c
linux-2.4.0-test8/kernel/ksyms.c
--- linux-2.4.0-test8-orig/kernel/ksyms.c Fri Sep 15 00:04:36 2000
+++ linux-2.4.0-test8/kernel/ksyms.c Mon Sep 11 23:39:38 2000
@@ -123,6 +123,7 @@
EXPORT_SYMBOL(find_vma);
EXPORT_SYMBOL(get_unmapped_area);
EXPORT_SYMBOL(init_mm);
+EXPORT_SYMBOL(access_process_vm);
#ifdef CONFIG_HIGHMEM
EXPORT_SYMBOL(kmap_high);
EXPORT_SYMBOL(kunmap_high);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2000-12-04  4:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200012040339.VAA43998@mail5.doit.wisc.edu \
    --to=epaulson@students.wisc.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).