From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brade Subject: Re: Tapdisk2 problem Date: Mon, 16 Aug 2010 00:07:35 +0200 Message-ID: <201008160007.37502.brade@kde.org> References: <1281909283.2427.183.camel@ramone.somacoma.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1281909283.2427.183.camel@ramone.somacoma.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sunday 15 August 2010 23:54:43 Daniel Stodden wrote: > On Sun, 2010-08-15 at 16:48 -0400, Keir Fraser wrote: > > On 15/08/2010 21:36, "Daniel Stodden" wrote: > > > On Sun, 2010-08-15 at 16:28 -0400, Keir Fraser wrote: > > >> On 15/08/2010 20:35, "Daniel Stodden" =20 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. > > >>>=20 > > >>> Keir, okay to just pull that stuff? > > >>=20 > > >> What stuff to where? > > >=20 > > > changeset: 21707:feee0abed6aa > > > user: Keir Fraser > > > date: Fri Jul 02 18:58:02 2010 +0100 > > > summary: blktap2: make protocol specific usage of shared sring > > > explicit > > >=20 > > > Into 4.0.1. > >=20 > > Okay, done. >=20 > Thanks! Where can I find this change? I am using xen-4.0-testing.hg but the last ch= nage=20 is a few days old? Thanks, =2D-=20 Michael Brade; KDE Developer |-mail: echo brade !#|tr -d "c oh"|s\e\d 's/e/\@/2;s/$/.org/;s/bra/k/2' =C2=B0--web: http://www.behindkde.org/people/michaelb/ KDE 4: Beyond Your Expectations