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] [PATCH 6/9] Linux support for vdevice bus

To: "Rusty Russell" <rusty@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 6/9] Linux support for vdevice bus
From: "Jacob Gorm Hansen" <jacobg@xxxxxxx>
Date: Wed, 7 Jun 2006 13:09:02 +0200
Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 07 Jun 2006 04:09:28 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=OnYjEwKcllVjwO6Wa5VwRsRhKhUWqbGiNo7aQfaRtlv55JpEHKwRbBWschtqlHV5RhNQSyOmN365dMlOJob7a1sJVa4rmos/Inq5a+0UBS7XzjPlxkQiKsE2KB6KKqT7enX9ZaLj6m/slCLHnCpm3Tb8GrOxMJV6XWNNG2UWM5U=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1149677938.5183.284.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <1149572143.5183.25.camel@xxxxxxxxxxxxxxxxxxxxx> <1149573287.5183.41.camel@xxxxxxxxxxxxxxxxxxxxx> <e08041f30606070303r7a679ce1t80d65c5b84a9e4a5@xxxxxxxxxxxxxx> <1149677938.5183.284.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 6/7/06, Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote:

So if we really want all the action to happen on restore, I think we
need a stop!() function for drivers called before interrupts are
re-enabled, and then we can call restart() later at our leisure.

The driver, other than ensuring that "stop" can be called with
interrupts off, doesn't have to know whether it's called during save or
restore.

Seem reasonable?

Yes, that sounds fine to me.

Jacob

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

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