All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Figo.zhang" <figo1802@gmail.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: how to mmap in  videobuf-dma-sg.c
Date: Sat, 24 Jul 2010 21:43:20 +0800	[thread overview]
Message-ID: <1279979000.2666.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20090521073518.1c0c0a5b@pedra.chehab.org>

On Thu, 2009-05-21 at 07:35 -0300, Mauro Carvalho Chehab wrote:
> Em Thu, 21 May 2009 12:46:04 +0800
> "Figo.zhang" <figo1802@gmail.com> escreveu:
> 
> > hi,all,
> >  I am puzzle that how to mmap ( V4L2_MEMORY_MMAP) in videobuf-dma-sg.c?
> > 
> > In this file, it alloc the momery using vmalloc_32() , and put this
> > momery into sglist table,and then use dma_map_sg() to create sg dma at
> > __videobuf_iolock() function. but in __videobuf_mmap_mapper(), i canot
> > understand how it do the mmap? 
> > why it not use the remap_vmalloc_range() to do the mmap?
> 
> The answer is simple: remap_vmalloc_range() is newer than videobuf code. This
> part of the code was written back to kernel 2.4, and nobody cared to update it
> to use those newer functions, and simplify its code.
> 
> If you want, feel free to propose some cleanups on it
thanks, in __videobuf_mmap_mapper(), it define a videobuf_vm_ops->fault,
it
will alloc a new page for mmaping when it  encounter page fault
(do_page_fault),
so how the mmap() can mmap the vmalloc memory which had allocted before
using __videobuf_iolock()/vmalloc_
32() ?

Thanks,
Figo.zhang

> 
> 
> 
> Cheers,
> Mauro



  parent reply	other threads:[~2010-07-24 13:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21  4:46 how to mmap in videobuf-dma-sg.c Figo.zhang
2009-05-21 10:35 ` Mauro Carvalho Chehab
2009-05-21 10:48   ` Figo.zhang
2009-06-10 15:06     ` Figo.zhang
2010-07-24 13:43   ` Figo.zhang [this message]
     [not found]   ` <AANLkTimExb4hh8K5lRCRiM0IMIgsOpCw69bFvqLlQCDc@mail.gmail.com>
2010-07-25 17:46     ` Mauro Carvalho Chehab
2010-07-26  8:16       ` Laurent Pinchart

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=1279979000.2666.0.camel@localhost.localdomain \
    --to=figo1802@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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.