> But as this code may be used in general acpi_read/write path too in the
> future, can you verify whether it is harmless on ia64?
This might be a problem on ia64 - it is s/w responsibility to make sure
that we don't map the same underlying physical address using different
cache attributes - e.g. we must not map memory both cacheable and uncacheable
at the same time. Accessing such a mis-attributed page will result in a
machine check.
So I'd worry that if the memory in question was being used as uncacheable,
this code might result in a cached access, which would crash the machine.
-Tony
��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
