[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 12:03:15 +0200
  • Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 07 Jun 2006 03:03:37 -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=Gm4l4p6UmHn86xqC3Jwoi4z3EV1I+wbwy8HYEihfa+vtgjr8xeALo+raNcWfQOlsFD7CIu6JJHmT6321zTeuBZuyF4dM6JgynKNkVKdxkh01f43CNyHiIN+8nj9B26PDn7mmlvkujodRswbDTFI5x49nhuRtk+399KbgqpkRJKE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 6/6/06, Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote:
Subject: Linux support for vdevice bus

This patch provides the Linux implementation of the vdevice bus.

FIXME: currently it does not support save/restore of the domain: it
should call stop before shutting down, and remap shares afterwards
before calling reconnect.  This depends on exactly what we do with
shared pages on restore.

In general I find the 'remember to suspend on save' approach that we
are currently using for xenbus and drivers problematic, and I much
favor a 'reset on resume' approach instead. Sometimes when doing a
save (or migration, or, in my case, self-migration), the domain wants
to continue running after the save, and then having to shut down all
external devices just to immediately resume them is inelegant and
often creates a lot of trouble. If we are to change the IPC/sharing
mechanism (and you make some good arguments for that), I think we
should design for 'reset on resume' rather than 'suspend-on-save'.

Just my DKK0.02.


Xen-devel mailing list



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