WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] GPLPV Drivers 0.9.11-pre4 hang during boot - WindowsXP P

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] GPLPV Drivers 0.9.11-pre4 hang during boot - WindowsXP Pro SP2
From: Wayne Gong <wayne.gong@xxxxxxxxxx>
Date: Fri, 04 Jul 2008 23:15:54 +0800
Cc: Sandro Sigala <sandro@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 Jul 2008 08:17:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0148FCDD@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <485A8681.10503@xxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0148FABB@trantor> <485AD22D.7070303@xxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0148FAEE@trantor> <485F726C.2000908@xxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0148FB24@trantor><4861D361.9070806@xxxxxxxxx> <486C7997.80503@xxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0148FCBA@trantor> <486CDFE4.6040006@xxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0148FCC5@trantor> <486DD394.4060403@xxxxxxxxx> <486DDF74.1010909@xxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0148FCDD@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Windows/20080421)

That patch appears to be to your wdf version of the code... can you give
me a summary of what the change you made is?

At a guess, the difference to the original code is that you are doing
two separate notify's, and a KeMemoryBarrier after each. Can you tell my
why the barrier is required?

I just noticed that the for() loop will never actually do anything as
req->nr_segments is initialised to zero... that's the same in my current
code too! I wonder how long that has been a problem for? I'll change my
code to initialise nr_segments to the maximum.

James

Yes, as you mentioned, there are only two difference. When I meet the bug, I have no idea to deal with it. So I try several method and times to fix it. After I changed the code up to the patch as I send to you, it works fine. And till now I am not very such whether this bug has been fixed. So I this patch just a try and I cannot explain it exactly even today.

Best regards -- Wayne


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

<Prev in Thread] Current Thread [Next in Thread>