Re: [Xen-devel] Tapdisk2 problem

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 15/08/2010 20:35, "Daniel Stodden" <daniel.stodden@xxxxxxxxxx> wrote:

> The problem is that the kernel has those changes. What's going to happen
> is that if tapdisk2 anticipates the ring 'message' at offset 17, not 16
> as intended, it will fail to find/clear the ring message, while the
> kernel will keep it spinning through select(), and that's what you're
> seeing.
> 
> Keir, okay to just pull that stuff?

What stuff to where?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel