Hi, On 31/10/2007, TeLeMan <[EMAIL PROTECTED]> wrote: > If the 0x10008000 page is writable and 0x10007FFF isn't, softmmu can raise > this exception before modifing 0x10007FFF-0x10008002 because softmmu checks > 0x10007FFF at first. I don't know if reversing the order is an exact > solution,but its simple and working.
Assuming that DATA_SIZE is less than page size, I think it is okay for a workaround, I committed it. It shows that permissions are checked two times for the first byte (0x10007ffff) but maybe that's okay since this is a slow access anyway. Regards
