From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 07/10] xen/arm: Force domains to use normal GICv2 driver on Hip04 platform Date: Tue, 13 Jan 2015 11:54:24 +0000 Message-ID: <1421150064.19103.36.camel@citrix.com> References: <1415009522-6344-1-git-send-email-frediano.ziglio@huawei.com> <1415009522-6344-8-git-send-email-frediano.ziglio@huawei.com> <54578E4A.4020907@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54578E4A.4020907@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall Cc: Frediano Ziglio , Tim Deegan , Stefano Stabellini , zoltan.kiss@huawei.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Mon, 2014-11-03 at 14:16 +0000, Julien Grall wrote: > Hi Frediano, > > FYI, this is only force DOM0 to use the normal GICv2 drivers. > > Do you have any plan to support hi-silicon vGIC in Xen? This would allow > guest running with more than 8 cores. I'm against exposing any non-standardised vGIC to guests. So long as the host can use all processors I think it is OK to constrain the guests in this way. I don't want to end up having loads of custom vGIC drivers for every time a silicon vendor deviates from the architecturally specified components.