All,
When doing save/restore testing with the linux-2.6.18-xen.hg tree,
it was discovered that every time a restore happened we would get a
new xenfb thread. While the framebuffer continues to work, this is
an obvious resource leak. The attached patch only starts up a new xenfb
thread the first time the backend connects, and continues to re-use that
in the future. Jeremy''s upstream LKML tree doesn''t suffer
from this
since it uses a completely different mechanism to do screen updates.
Original patch from John Haxby @ Oracle; slightly modified by me to apply
to the linux-2.6.18-xen.hg tree.
Signed-off-by: Chris Lalancette <clalance@redhat.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel