David Miller <davem@davemloft.net> writes:

quoted text
> From: Tilman Schmidt <tilman@imap.cc>
> Date: Sun, 17 Feb 2008 20:24:56 +0100
>
>> No, that's not the real problem. Even if the kernel didn't lack
>> any required functionality and it could all be done today without
>> VirtualBox, pulling the rug from underneath it like that leaves
>> all those who are currently relying on it without the ability to
>> continue testing newer kernels until they find the time to redesign
>> their working environment.
>
> No, it is VirtualBox's problem.  Nobody outside of the kernel
> should be using that symbol, 

quoted text
> it can only be used for totally
> unsupportable things as far as upstream is concerned.

Creating any uncacheable or write protected mappings in unsupportable? 
I suspect you would have a hard time actually justifying this. That's
a relatively common and useful operation in device drivers.

The only special case I would agree with you is doing write-combined
mappings using this which is indeed generally unsupported yet on x86
before the full PAT infrastructure goes in (but 
I cannot imagine VirtualBox would use WC for anything) 

Most likely if they just want to write protect something
they should either use the new interface or just open code
it using lookup_address() / change ptes / flush tlbs.

-Andi

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/