[Top] [All Lists]

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

Re: [Xen-devel] [PATCH] Change the global suspend event channel lock file to a per-domain lock file

To: Shriram Rajagopalan <rshriram@xxxxxxxxx>
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Thu, 29 Apr 2010 23:38:44 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 29 Apr 2010 23:39:30 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Mail-followup-to: rshriram@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx

On Tuesday, 27 April 2010 at 23:05, Shriram Rajagopalan wrote:
> This allows multiple guests to be migrated or protected by Remus 
> simultaneously.
> 
> Signed-off-by: Shriram Rajagopalan <rshriram@xxxxxxxxx>

Acked-by: Brendan Cully <brendan@xxxxxxxxx>

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

References:
- [Xen-devel] [PATCH] Change the global suspend event channel lock file to a per-domain lock file
  - From: Shriram Rajagopalan

Prev by Date: Re: [Xen-devel] libxenlight and xl: missing features
Next by Date: [Xen-devel] x86-64/kexec: crashkernel= without @xM suffix
Previous by thread: [Xen-devel] [PATCH] Change the global suspend event channel lock file to a per-domain lock file
Next by thread: [Xen-devel] PV kernel boot parameter maxcpus has no effect?
Index(es):
- Date
- Thread

Rackspace

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