Possible data structure corruption about kvm-guest-drivers-windows

[YanVugenfirer]

We are testing the code now with HCK (MS certification tool). I think
during next week we will have a stable code for sharing.

Best regards,
Yan.

On Tue, May 24, 2016 at 9:56 PM, pturschmid [email protected]
wrote:

By any chance do you have an estimate of when you'll rework the pause
behavior? Alternately can you provide a description of what the fix may
look like? I want to try a fix ahead of time if possible to see if it makes
our repro go away. :-) Thanks!

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/YanVugenfirer/kvm-guest-drivers-windows/issues/65#issuecomment-221364484

---

Daynix Computing LTD
Yan Vugenfirer, CEO
Email: [email protected]
Phone (Israel): [phone]
Phone (USA): [phone]
Phone (UK): [phone]
Web: www.daynix.com

[YanVugenfirer]

Thank you for the report and analysis. We are reworking the "Pause" behaviour right now and will address all the issues related to it.

[YanVugenfirer]

There were two patch sets that addressed the issue: bacc1c2-911bad680ee29619fa521e0d87b3e1b6c7f2dd3f and e1de11f-7ef084b8f739e524bc690bda876c58ba955646c7

[pturschmid]

By any chance do you have an estimate of when you'll rework the pause behavior? Alternately can you provide a description of what the fix may look like? I want to try a fix ahead of time if possible to see if it makes our repro go away. :-) Thanks!

[pturschmid]

Thanks Yan for the super quick turnaround! :-)

[YanVugenfirer]

Please try the following build: https://dl.dropboxusercontent.com/u/97739133/virtio-win-prewhql-0.1-118.zip

[pturschmid]

Thanks Yan. Will try it out ASAP! :-)

[pturschmid]

Good news! Fixed the bug perfectly! Thanks!

I checked the latest commits but I couldn't tell which one if any were for this issue. Can you point me to the commit when it's ready?

[YanVugenfirer]

Thank you for the feedback!

On 10 ביוני 2016, at 21:33, pturschmid [email protected] wrote:

Good news! Fixed the bug perfectly! Thanks!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.