[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Re: Reproducable data corruption on xen-unstable

A few minutes ago, I wrote:
So, it looks like we are looking for a code path in which TS doesn't end
up set after a task switch.

Aha! Shouldn't the stts macro in xeno-linux be calling __HYPERVISOR_fpu_taskswitch instead of trying to write to CR0 itself?
Writing to CR0 directly is impossible in ring 1, isn't it?

I think I may have solved the mystery! I'll have to try that out in the next few days.

stts is called by _mmx_memcpy, which is called by memcpy on Athlons. That _might_ explain why people who aren't using Athlons haven't seen this.


This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.