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

Re: [Xen-devel] [PATCH V2] libxl: write IO ABI for disk frontends

To: Wei Liu <wei.liu2@xxxxxxxxxx>
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Thu, 25 Apr 2013 16:02:08 +0100
Cc: Roger Pau Monne <roger.pau@xxxxxxxxxx>, Valtteri Kiviniemi <kiviniemi.valtteri@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
Delivery-date: Thu, 25 Apr 2013 15:02:26 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Thu, 2013-04-25 at 15:57 +0100, Wei Liu wrote:

> This string is propogated from Python libxc binding, and it is only
> placed in pyxc_linux_build. So unless I'm mistaken, Xend only does this
> for PV.
> 
> Removing the type check and write the node for each type of domain
> should do no harm.  For newer frontends, they just blindly write that
> node whether it pre-exists or not.

We should probably stick with the xend behaviour, even if it is slightly
more code.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH V2] libxl: write IO ABI for disk frontends
  - From: Wei Liu
- Re: [Xen-devel] [PATCH V2] libxl: write IO ABI for disk frontends
  - From: Ian Campbell
- Re: [Xen-devel] [PATCH V2] libxl: write IO ABI for disk frontends
  - From: Wei Liu

Prev by Date: Re: [Xen-devel] Xen 4.2.2 release patch
Next by Date: Re: [Xen-devel] [PATCH v3 03/13] xen: introduce cpumask_from_bitmap
Previous by thread: Re: [Xen-devel] [PATCH V2] libxl: write IO ABI for disk frontends
Next by thread: [Xen-devel] [PATCH 0/2 v8] arm: introduce psci_smp_ops
Index(es):
- Date
- Thread

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