Il 18/08/2014 19:47, Hulin, Patrick - 0559 - MITLL ha scritto:
>> We'll have done the page for the first byte at the top of
>> helper_{le,be}_{ld,st}_name. When we discover it's an unaligned
>> access, we should load and check the pte for the second page. We
>> might have to shuffle those two tests around, since in theory the
>> second page could be I/O mapped and we'd want to pass off the
>> whole access to io_mem_*.
>>
>> Since two adjacent pages can't conflict in our direct-mapped TLB,
>> we can then safely pass off the work to secondary helpers without
>> fear the first TLB entry will be flushed.
>
> This isn’t about cross-page writes, although that might make fixing
> the problem a little tricky. The issue occurs with two adjacent TBs
> on the same page: because the individual writes are split up and done
> in reverse order, writes (and reads) off the back of the current TB
> happen twice. In the case of an xor this means the original xor gets
> undone, which is what breaks in Windows 7.
If you fill the TLB beforehand as suggested by Richard, you can reverse
again the direction of the "for" loop. This should hopefully fix your bug.
Of course if the write is not cross-page, there's no need to do the TLB
pre-fill.
Thanks for the test case!
Paolo
