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

[Xen-devel] Re: A wrong assert in get_ioreq()?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: A wrong assert in get_ioreq()?
From: "Paul Samon" <paul.samon@xxxxxxxxx>
Date: Wed, 4 Jul 2007 19:12:32 +0800
Delivery-date: Wed, 04 Jul 2007 04:10:22 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=c3uJ0id0kIZWQUmgOZ2WkZLkOz4UH5HRwXrAYgLRccWCvFEZzXvwhyfz05T+F+KkFd9Ga1taM4RcuhvOXbrW8lJWUR2yGLUEO9vsGK/y7MG/XJI14H5IcfAjynq/tAF3bvzKlEH+hqH5QqAfZOLQtgC4Clq40NH6bgbvX+SAK68=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=mabxd/vLPKA3sUGomb5M5ClVv+k4zU+9hOf5Wpp50pHvPdry40F4YS1LKHjdLClIwNeHiejYW7lsn1D0FOLfBWOVkXXK1h4CziX+U2Uv+EaqRpgxF5CuR93tYTUsSXYaz+2gEpejNlKp4Nv3pZMbNhPXqfim/2uH+rOWDx0e1us=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <34cec8c90707040405x368042cdifacb300725fc0e5b@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <34cec8c90707040405x368042cdifacb300725fc0e5b@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Sorry, I meant the assert should "ASSERT(v == current)."
 
On 7/4/07, Paul Samon <paul.samon@xxxxxxxxx> wrote:
I don't think it should be
    ASSERT(v == current).
we don't get the lock first, and I think we needn't it.
 
Am I missing something?
 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>