public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add __vunmap prototype
Date: Mon, 14 May 2007 00:16:32 -0700	[thread overview]
Message-ID: <20070514001632.60421680.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070514070732.B3796DDE44@ozlabs.org>

On Mon, 14 May 2007 17:07:03 +1000 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:

> __vunmap is not static but I couldn't find a prototype for it, so this
> adds it. I need to use it in some powerpc patch to come.
> 
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> 
>  include/linux/vmalloc.h |    1 +
>  1 file changed, 1 insertion(+)
> 
> Index: linux-cell/include/linux/vmalloc.h
> ===================================================================
> --- linux-cell.orig/include/linux/vmalloc.h	2007-05-14 16:03:42.000000000 +1000
> +++ linux-cell/include/linux/vmalloc.h	2007-05-14 16:03:47.000000000 +1000
> @@ -50,6 +50,7 @@ extern void vfree(void *addr);
>  extern void *vmap(struct page **pages, unsigned int count,
>  			unsigned long flags, pgprot_t prot);
>  extern void vunmap(void *addr);
> +extern void __vunmap(void *addr, int deallocate_pages);
>  
>  extern int remap_vmalloc_range(struct vm_area_struct *vma, void *addr,
>  							unsigned long pgoff);

um, the only possible reason for wanting to access __vunmap() is that you
want to do vunmap() from interrupt context, which is deadlockable.


  reply	other threads:[~2007-05-14  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  7:07 [PATCH] Add __vunmap prototype Benjamin Herrenschmidt
2007-05-14  7:16 ` Andrew Morton [this message]
2007-05-14  7:56   ` Benjamin Herrenschmidt
2007-05-14  8:02     ` Satyam Sharma

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=20070514001632.60421680.akpm@linux-foundation.org \
    --to=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