From: "Andreas Block" <andreas.block@esd-electronics.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Bad page state with x86_64
Date: Wed, 27 Sep 2006 09:20:48 +0200 [thread overview]
Message-ID: <op.tgiz0y0t8n9ctc@pc-block.esd> (raw)
In-Reply-To: <4519200A.4000109@yahoo.com.au>
On Tue, 26 Sep 2006 14:41:46 +0200, Nick Piggin <nickpiggin@yahoo.com.au>
wrote:
> It is freeing a PageReserved page. You should ensure to balance your
> reference counting on *each* page (or allocate a compound page and
> treat it as a single one). When you map pages into userspace via
> nopage or remap_pfn_range, you need to increment their count, which
> gets decremented by the VM when they are unmapped.
Thanks a lot for your time and help. Still there are a few things a
seemingly don't understand correctly.
Do I understand you right, I don't have to "put_page" after calling
"get_page" in my no-page handler?
Also I'm wondering, why this code works flawlessly on 2.6.10 32-Bit and
several 2.4.x kernels 32-Bit and PPC and is failing to work on x86_64,
only. Do I have to do the "get/put_page" mechanism differnetly on x86_64?
Another question:
In my no-page handler, I reserve the physical page. I do have to clear the
reserve bit of those page after unmap, right? Or is this done implicitly
as well?
Again, thanks for your effort.
--
-------------------------------------------------------------------------
_/_/_/_/ Andreas Block
_/_/_/_/ Dipl.-Ing.
_/_/_/_/ andreas.block@esd-electronics.com
_/_/_/ _/_/_/_/_/_/_/ esd electronic system design gmbh
_/ _/ _/ _/ Vahrenwalder Str. 207
_/ _/ _/_/_/ _/ _/ D-30165 Hannover
_/ _/ _/ _/ Phone: +49-511-37298-0
_/_/_/_/_/_/_/ _/_/_/ Fax: +49-511-37298-68
http://www.esd-electronics.com
-------------------------------------------------------------------------
prev parent reply other threads:[~2006-09-27 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 10:18 Andreas Block
2006-09-26 12:41 ` Nick Piggin
2006-09-27 7:20 ` Andreas Block [this message]
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=op.tgiz0y0t8n9ctc@pc-block.esd \
--to=andreas.block@esd-electronics.com \
--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
all inboxes | Powered by JetHome®