From: Rik van Riel <riel@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, ajackson@redhat.com,
airlied@redhat.com, benh@kernel.crashing.org
Subject: [patch 2/5] use generic_access_phys for /dev/mem mappings
Date: Thu, 15 May 2008 13:53:59 -0400 [thread overview]
Message-ID: <20080515175431.059826165@redhat.com> (raw)
In-Reply-To: 20080515175357.636334082@redhat.com
[-- Attachment #1: 02-devmem-access.patch --]
[-- Type: text/plain, Size: 794 bytes --]
Use generic_access_phys as the access_process_vm access
function for /dev/mem mappings. This makes it possible to
debug the X server.
Signed-off-by: Rik van Riel <riel@redhat.com>
Index: ptrace-2.6.26-rc2-mm1/drivers/char/mem.c
===================================================================
--- ptrace-2.6.26-rc2-mm1.orig/drivers/char/mem.c 2008-05-15 13:28:13.000000000 -0400
+++ ptrace-2.6.26-rc2-mm1/drivers/char/mem.c 2008-05-15 13:28:41.000000000 -0400
@@ -326,7 +326,8 @@ static void mmap_mem_close(struct vm_are
static struct vm_operations_struct mmap_mem_ops = {
.open = mmap_mem_open,
- .close = mmap_mem_close
+ .close = mmap_mem_close,
+ .access = generic_access_phys
};
static int mmap_mem(struct file * file, struct vm_area_struct * vma)
--
All Rights Reversed
next prev parent reply other threads:[~2008-05-15 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 17:53 [patch 0/5] access_process_vm device memory access Rik van Riel
2008-05-15 17:53 ` [patch 1/5] access_process_vm device memory infrastructure Rik van Riel
2008-05-16 8:20 ` Peter Zijlstra
2008-05-16 20:27 ` [PATCH 6/5] Add documentation for the vm_ops->access function Rik van Riel
2008-05-15 17:53 ` Rik van Riel [this message]
2008-05-15 17:54 ` [patch 3/5] use generic_access_phys for pci mmap on x86 Rik van Riel
2008-05-15 17:54 ` [patch 4/5] powerpc ioremap_prot Rik van Riel
2008-05-15 17:54 ` [patch 5/5] spufs use the new vm_ops->access Rik van Riel
2008-05-23 5:58 ` [patch 0/5] access_process_vm device memory access Andrew Morton
2008-05-23 6:01 ` Andrew Morton
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=20080515175431.059826165@redhat.com \
--to=riel@redhat.com \
--cc=airlied@redhat.com \
--cc=ajackson@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox