From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel De Graaf Subject: Re: [PATCH] xenbus: Add support for xenbus backend in stub domain Date: Wed, 18 Jan 2012 09:44:21 -0500 Message-ID: <4F16DAC5.2030806@tycho.nsa.gov> References: <1326411330-7915-1-git-send-email-dgdegra@tycho.nsa.gov> <1326411373-7971-1-git-send-email-dgdegra@tycho.nsa.gov> <1326888429.14689.221.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1326888429.14689.221.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 01/18/2012 07:07 AM, Ian Campbell wrote: > On Thu, 2012-01-12 at 23:36 +0000, Daniel De Graaf wrote: >> This adds an ioctl to the /dev/xen/xenbus_backend device allowing the >> xenbus backend to be started after the kernel has booted. This is >> intended to allow dom0 to start another domain to run xenstore. > > Does this new ioctl need to be made oneshot? What happens if you call it > twice? > > Also it should be disabled once a local xenstored has connected > shouldn't it? > > Diego's original patch handled that sort of thing, any reason not to > simply forward port it? > My original patch was trying to be more flexible in allowing xenstored to be created later (migrating watches), or restarted in a different domain. However, since the current version lacks that ability the oneshot safeguards from Diego's patch should probably be added.