[Bug 1785734] Re: movdqu partial write at page boundary

2021-07-10 Thread Launchpad Bug Tracker
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1785734 Title: movdqu

[Bug 1785734] Re: movdqu partial write at page boundary

2021-05-10 Thread Thomas Huth
The QEMU project is currently moving its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting the bug state to "Incomplete" now. If the bug has already been fixed in the latest upstream version of QEMU, then

[Qemu-devel] [Bug 1785734] Re: movdqu partial write at page boundary

2018-08-07 Thread pranith
** Changed in: qemu Status: New => Confirmed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1785734 Title: movdqu partial write at page boundary Status in QEMU: Confirmed Bug

[Qemu-devel] [Bug 1785734] Re: movdqu partial write at page boundary

2018-08-07 Thread Richard Henderson
This is a part of a class of related problems for qemu linux-user, in that any non-atomic store is not validated before initiating a partial write. For instance, qemu-x86_64, built for arm32, would show this same partial store problem for any 64-bit write crossing a page boundary because we are