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

Re: [Xen-devel] [PATCH] arch/x86/hvm: Bind xen-created event channels to building domain

On Wed, 2013-01-09 at 14:43 +0000, Daniel De Graaf wrote:
> On 01/09/2013 06:12 AM, Ian Campbell wrote:
> > On Thu, 2013-01-03 at 18:28 +0000, Daniel De Graaf wrote:
> >> Instead of using a hardcoded domain 0 as the endpoint for the event
> >> channels created in hvm_vcpu_initialise, use the domain ID of the
> >> building domain so that a domain builder in a domain other than dom0 has
> >> the expected access to the event channels.
> > 
> > OOI what is the builder (I assume it's not specific to being a separate
> > domain) doing that requires it to access to the IOEMU event channels?
> > 
> > Ian.
> > 
> I believe this caused problems when the device model was running in the 
> same domain as the domain builder (where that was not dom0), not during
> the domain build process.

I thought the DM set HVM_PARAM_DM_DOMAIN itself?

> After seeing Keir and Jan's comments, I think
> the best solution is for the domain builder to set HVM_PARAM_DM_DOMAIN 
> to DOMID_SELF (or the actual device model domain ID)
libxc probably doesn't know this, FWIW.

>  earlier in the 
> build process and use that parameter in the event channel creation
> instead of 0 or current->domain->domain_id.

Xen-devel mailing list



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