From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: [PATCH v1 07/12] libxl: add prepare/unprepare operations to the libxl public interface Date: Fri, 15 Mar 2013 12:42:46 +0100 Message-ID: <51430936.70002@citrix.com> References: <1358963317-10221-1-git-send-email-roger.pau@citrix.com> <1358963317-10221-8-git-send-email-roger.pau@citrix.com> <20800.42788.524880.95800@mariner.uk.xensource.com> <514306F9.7060709@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <514306F9.7060709@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Ian Campbell , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 15/03/13 12:33, Roger Pau Monn=E9 wrote: > The caller should take care of this states by himself (just as we do > with add or remove), so it knows if the device has been prepared or not. Just as a clarification, the way to know if a device has been prepared but not added is to look for the xenstore entries. If the device only has /libxl//hotplug/status// then it has been prepared but not added, on the other hand, if the device has the above xenstore path, and also /local/domain//device/vbd//backend then it has been prepared and added. But I can't come up with any reason a libxl user should look at this paths by himself.