public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Amir Hermelin" <amir@montilio.com>
To: "'William Lee Irwin III'" <wli@holomorphy.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Creating a page struct for HIGHMEM pages
Date: Sun, 7 Dec 2003 20:05:39 +0200	[thread overview]
Message-ID: <00c401c3bcec$bbd52e40$1d01a8c0@CARTMAN> (raw)
In-Reply-To: <20031207175915.GZ8039@holomorphy.com>

Yes, I've tried ioremap (and placed the address in the ->virtual field), but
had problems with pre-written code that used kmap.  So, basically, what
you're saying is that I must change my code that uses kmap, or
alternatively, allocated page* below the highmem_start_page address.  Is
this correct?


-----Original Message-----
From: William Lee Irwin III [mailto:wli@holomorphy.com] 
Sent: Sunday, December 07, 2003 7:59 PM
To: Amir Hermelin
Cc: linux-kernel@vger.kernel.org
Subject: Re: Creating a page struct for HIGHMEM pages


On Sun, Dec 07, 2003 at 07:56:17PM +0200, Amir Hermelin wrote:
> I may be missing something a little more basic: I have a contiguous 
> physical memory area (IO memory), and I want to manage it with struct 
> pages.  If I'm to write to the page I need to kmap it, therefore (as I
understand it) I
> need to zero the ->virtual field.   What I don't understand is how, given
> the struct page I've allocated and filled out, is the page correlated 
> with the correct physical memory.  Where do I put the information that 
> struct page X points to physical address Y, so that when I kmap(X) I 
> get a virtual address pointing to Y?

You probably want ioremap(), not kmap().


-- wli



  reply	other threads:[~2003-12-07 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07 16:02 Creating a page struct for HIGHMEM pages Amir Hermelin
2003-12-07 16:22 ` William Lee Irwin III
2003-12-07 17:56   ` Amir Hermelin
2003-12-07 17:59     ` William Lee Irwin III
2003-12-07 18:05       ` Amir Hermelin [this message]
2003-12-07 18:08         ` William Lee Irwin III

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='00c401c3bcec$bbd52e40$1d01a8c0@CARTMAN' \
    --to=amir@montilio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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