public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Will __pa(vmalloc()) ever work?
Date: Sat, 28 May 2005 17:16:26 +0100	[thread overview]
Message-ID: <20050528171626.B4711@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050527192925.GA8250@infradead.org>; from hch@infradead.org on Fri, May 27, 2005 at 08:29:25PM +0100

On Fri, May 27, 2005 at 08:29:25PM +0100, Christoph Hellwig wrote:
> On Fri, May 27, 2005 at 02:26:36PM -0500, Timur Tabi wrote:
> > I have a driver that calls __pa() on an address obtained via vmalloc().  
> > This is not supposed to work, and yet oddly it appears to.  Is there a 
> > possibility, even a remote one, that __pa() will return the correct 
> > physical address for a buffer returned by the vmalloc() function?
> 
> It will return the correct physical address for the start of the buffer.

__pa() is only defined to works on the direct-mapped kernel region.
The fact that it works on some architectures should be viewed as a
bug.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  parent reply	other threads:[~2005-05-28 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 19:26 Will __pa(vmalloc()) ever work? Timur Tabi
2005-05-27 19:29 ` Christoph Hellwig
2005-05-27 19:54   ` Timur Tabi
2005-05-27 20:31     ` Arnd Bergmann
2005-05-28 16:16   ` Russell King [this message]
2005-05-30  9:38 ` Gerd Knorr
2005-05-31 15:51   ` Timur Tabi
2005-05-31 16:13     ` Gerd Knorr
2005-05-31 18:59       ` Timur Tabi
2005-05-31 20:01         ` Russell King
2005-05-31 20:44         ` Brian Gerst

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=20050528171626.B4711@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=hch@infradead.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