[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 6/9] Linux support for vdevice bus

  • To: "Rusty Russell" <rusty@xxxxxxxxxxxxxxx>
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

Seem reasonable?

Yes, that sounds fine to me.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.