From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH v3 01/15] xen: add xenstore domain flag to
	hypervisor
Date: Fri, 8 Jan 2016 16:13:14 +0000
Message-ID: <568FE01A.1010405@citrix.com>
References: <1452258526-4797-1-git-send-email-jgross@suse.com>
	<1452258526-4797-2-git-send-email-jgross@suse.com>
	<568FD0B902000078000C4E8F@prv-mh.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <568FD0B902000078000C4E8F@prv-mh.provo.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>, Juergen Gross <JGross@suse.com>
Cc: Tim Deegan <tim@xen.org>, wei.liu2@citrix.com, Ian.Campbell@citrix.com, stefano.stabellini@eu.citrix.com, Andrew Cooper <andrew.cooper3@citrix.com>, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org, Keir Fraser <keir@xen.org>, dgdegra@tycho.nsa.gov
List-Id: xen-devel@lists.xenproject.org

On 08/01/16 14:07, Jan Beulich wrote:
>>>> On 08.01.16 at 14:08, <JGross@suse.com> wrote:
>> --- a/xen/common/domain.c
>> +++ b/xen/common/domain.c
>> @@ -318,6 +318,12 @@ struct domain *domain_create(domid_t domid, unsigned int domcr_flags,
>>          hardware_domain = d;
>>      }
>>  
>> +    if ( domcr_flags & DOMCRF_xs_domain )
>> +    {
>> +        d->is_xenstore = 1;
>> +        d->disable_migrate = 1;
>> +    }
> 
> It only occurred to me now: Wouldn't it be worth denying the domain
> creation request if there already is a xenstore domain?

Running multiple xenstore domains, one for each isolated set of domains
managed by their own toolstack domain with their own backends seems like
a valid (future) use case.

David