[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 09 Sep 2008 08:48:06 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Keir Fraser <keir.fraser@...citrix.com>
CC: Avi Kivity <avi@...ranet.com>, Ingo Molnar <mingo@...e.hu>,
Xen Devel <xen-devel@...ts.xensource.com>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Xen-devel] Re: [PATCH 1 of 7] x86: add _PAGE_IOMAP pte flag
for IO mappings
Keir Fraser wrote:
> That's basically what our _PAGE_IO flag (in our old Linux patchset) means.
> We use it to cause pte_pfn() to return an invalid pfn and hence avoid
> reference counting that way. Since kernel mappings are never reference
> counted (I think?) perhaps we could use _PAGE_SPECIAL even if it is
> restricted to use on user mappings.
Well, _PAGE_IOMAP's most important semantic from Xen's perspective is
that the frame number is considered to already be an MFN and so isn't
converted. It may be that _PAGE_SPECIAL is also useful for its "no
refcount" properties, but we could set both in that case.
At present we can't set _PAGE_SPECIAL on kernel mappings because we
assume its usermode only, and its shared with _PAGE_CPA_TEST which is
kernel-only. Most _PAGE_IOMAP mappings are in kernel space, but I
wouldn't discount user mappings if we end up allowing direct access to
passthrough devices.
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists