Re: x86-64: memset()/memcpy() not fully standards compliant

[H. Peter Anvin]

On 01/06/2012 11:44 AM, Andi Kleen wrote:
>> enough beyond 292G. At some later point ->node_page_cgroup[]
>> also exceeds 4G. Finally, the phys-to-machine mapping (which gets
>> resized during boot) exceeds 4G when crossing the 2T boundary.
> 
> Ok it's moot then because the old systems with problem didn't have
> that much memory. So you could do without an errata workaround
> and just extend the moves at the minor cost of a few prefixes
> (I think that is what you did in your patch)
> 

That seems like the way to go unless we can identify a real problem.

	-hpa

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