From: Zhonghua Dai <zdai@solution-soft.com>
To: Der Herr Hofrat <der.herr@mail.hofr.at>, linux-kernel@vger.kernel.org
Subject: Re: mmap question
Date: Tue, 24 Sep 2002 17:37:53 +0800 [thread overview]
Message-ID: <200209241737.53490.zdai@solution-soft.com> (raw)
In-Reply-To: <200209240726.g8O7QNA06595@hofr.at>
On Tuesday 24 September 2002 15:26, Der Herr Hofrat wrote:
> Hi !
>
> trying to write up a simple mmap for a pseudo device that accesses a
> kmalloc'ed area.
>
> The driver is a character driver that only has mmap implemented - the
> kmalloc is done in init module and the pointer to the buffer is in global
> context. I expected to be able to write to the mmap'ed area from user-space
> but it never shows up in kernel space (the printk in driver_mmap always
> shows the init_msg passed in init_module).
>
> the basic framework I'm using is below - can anybody point me to an
> obvious error or to some docs that would explain how to share an kmalloc'ed
> area with user-space via mmap ?
>
> thx !
> hofrat
>
> ---driver---
> char *kmalloc_area;
> ...
> static int
> driver_mmap(struct file *file,
> struct vm_area_struct *vma)
> {
> vma->vm_flags |= VM_LOCKED|VM_SHARED;
>
> printk("message buffer: %s\",kmalloc_area);
> remap_page_range(vma->vm_start,
> virt_to_phys(kmalloc_area),
> LEN,
> PAGE_SHARED);
Before memory can be exported into userspace, the reserved bit must be set.
Call mem_map_reserve() prior to remap_page_range().
good luck.
> return 0;
> }
>
> static struct file_operations simple_fops={
> mmap: driver_mmap,
> };
>
> int
> init_module(void){
> ...
> kmalloc_area=kmalloc(LEN,GFP_USER);
> strncpy(kmalloc_area,init_msg,sizeof(init_msg));
> ...
> }
>
> ---user-app---
>
> int main(void)
> {
> int fd;
> char msg[]="some message - should appear in kernel space";
> unsigned int *addr;
>
> if((fd=open("/dev/simple-device", O_RDWR))<0)
> addr = mmap(0, LEN, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0);
> memset(addr,0,LEN);
> strncpy(addr,msg,sizeof(msg));
> return 0;
> }
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-11-12 7:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 7:26 mmap question Der Herr Hofrat
2002-09-24 8:54 ` Der Herr Hofrat
2002-09-24 9:37 ` Zhonghua Dai [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 22:44 Ruslan Nikolaev
2005-03-21 17:59 Eric Van Hensbergen
2005-03-21 21:33 ` Bryan Henderson
2005-03-21 22:23 ` Matthew Wilcox
2005-03-21 23:18 ` Bryan Henderson
[not found] ` <a4e6962a05032114575776f94b@mail.gmail.com>
2005-03-21 22:57 ` Eric Van Hensbergen
2005-03-21 23:24 ` Bryan Henderson
2005-03-21 23:27 ` Bryan Henderson
2005-03-22 21:05 ` Eric Van Hensbergen
2005-03-21 23:56 ` Martin Jambor
2002-06-04 13:22 Frederic Gobry
2002-07-01 13:14 ` Frederic Gobry
2002-07-11 16:19 ` Frederic Gobry
2002-07-11 19:15 ` Jörn Engel
2002-07-12 7:57 ` Frederic Gobry
2002-07-12 15:08 ` Jörn Engel
2002-07-15 7:41 ` Frederic Gobry
2002-07-12 15:21 ` David Woodhouse
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=200209241737.53490.zdai@solution-soft.com \
--to=zdai@solution-soft.com \
--cc=der.herr@mail.hofr.at \
--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.