From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] arch/x86/hvm: Bind xen-created event channels to building domain Date: Wed, 09 Jan 2013 15:02:30 +0000 Message-ID: References: <50ED8206.2090006@tycho.nsa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <50ED8206.2090006@tycho.nsa.gov> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Daniel De Graaf , Ian Campbell Cc: Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 09/01/2013 14:43, "Daniel De Graaf" wrote: >> 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. 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) earlier in the > build process and use that parameter in the event channel creation > instead of 0 or current->domain->domain_id. This is the fix I have just applied as xen-unstable:26339. See what you think. It will require you to set HVM_PARAM_DM_DOMAIN from the toolstack at some point during domain creation, any time before the device model starts running. -- Keir