From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH v4 2/2] allow hardware domain != dom0 Date: Tue, 15 Apr 2014 15:45:59 +0100 Message-ID: <534D4627.4050408@citrix.com> References: <1397510594-5301-1-git-send-email-dgdegra@tycho.nsa.gov> <1397510594-5301-2-git-send-email-dgdegra@tycho.nsa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1397510594-5301-2-git-send-email-dgdegra@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 Cc: Keir Fraser , Ian Campbell , Tim Deegan , Ian Jackson , xen-devel@lists.xen.org, Jan Beulich List-Id: xen-devel@lists.xenproject.org On 14/04/14 22:23, Daniel De Graaf wrote: > diff --git a/xen/common/domain.c b/xen/common/domain.c > index 3c05711..11c905a 100644 > --- a/xen/common/domain.c > +++ b/xen/common/domain.c > @@ -61,6 +61,11 @@ struct domain *domain_list; > > struct domain *hardware_domain __read_mostly; > > +#ifdef CONFIG_LATE_HWDOM > +domid_t hardware_domid __read_mostly; > +integer_param("hardware_dom", hardware_domid); > +#endif > + Is it worth putting a custom_param() in here which clamps hardware_domid below FIRST_RESERVED_DOMID, or allow anyone specifying hardware_dom=0xffff to keep all the broken pieces they find? Aliasing the magic domids is sure to break things. ~Andrew