[Spice-devel] [PATCH 3/3] Fix corrupted ram data (e.g., release_ring), and unsynchronized worker, after driver is disabled and re-enabled.

Gerd Hoffmann kraxel at redhat.com
Mon Jul 12 02:43:31 PDT 2010


On 07/12/10 11:15, Yonit Halperin wrote:
> On logoff in Win7 guest, and on switch user and login into Winxp guest,
> the driver is disabled and re-enabled (while the miniport in not reset).
> However, before the fix, all the draw objects, e.g., surfaces,
> were still alive in the worker and the release ring still contained objects, while all the driver's data
> was initialized. This caused blue screens, and panics in the worker.

Hmm, I'd suggest to go straight for a plain IO_RESET in the driver 
initialization to start fresh with a known state of the qxl device. 
That should avoid all unpleasant surprises due to the qxl device not 
being in the state the driver expects.

cheers,
   Gerd



More information about the Spice-devel mailing list