From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>, Zachary Amsden <zach@vmware.com>
Subject: Re: bad paravirt/Xen interaction in "x86 - Enhance DEBUG_RODATA support - alternatives"
Date: Mon, 03 Mar 2008 09:58:03 -0800 [thread overview]
Message-ID: <47CC3C2B.6000807@goop.org> (raw)
In-Reply-To: <20080303173057.GA14598@Krystal>
Mathieu Desnoyers wrote:
> I think kmap_atomic is only implemented on x86_32 and only deals with
> highmem pages. It will simply return the original page address without
> changing the protection for other pages, which is not what we want.
> Would ioremap() be a good alternative ?
>
Perhaps, though that's uncached by default. You could reserve a fixmap
slot and use set_fixmap to create the mapping. Or use vmap, which may
make dealing with instructions crossing page boundaries a little easier.
J
next prev parent reply other threads:[~2008-03-03 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 20:39 bad paravirt/Xen interaction in "x86 - Enhance DEBUG_RODATA support - alternatives" Jeremy Fitzhardinge
2008-02-29 20:56 ` H. Peter Anvin
2008-02-29 21:09 ` Jeremy Fitzhardinge
2008-03-03 17:30 ` Mathieu Desnoyers
2008-03-03 17:35 ` Andi Kleen
2008-03-03 17:58 ` Jeremy Fitzhardinge [this message]
2008-03-03 18:03 ` Andi Kleen
2008-03-03 18:05 ` Jeremy Fitzhardinge
2008-03-03 20:53 ` Mathieu Desnoyers
2008-03-03 22:15 ` Jeremy Fitzhardinge
2008-03-04 4:12 ` Mathieu Desnoyers
2008-02-29 21:24 ` Ingo Molnar
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=47CC3C2B.6000807@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=zach@vmware.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 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.