From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v3 00/15] xen/arm: Bug fixes for the vGIC Date: Fri, 20 Feb 2015 10:44:13 +0000 Message-ID: <1424429053.30924.184.camel@citrix.com> References: <1424098255-22490-1-git-send-email-julien.grall@linaro.org> <1424366486.30924.148.camel@citrix.com> <54E61EAE.3030903@linaro.org> <1424368093.30924.154.camel@citrix.com> <54E624DC.8090502@linaro.org> <1424427278.30924.162.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOl4k-00006X-4F for xen-devel@lists.xenproject.org; Fri, 20 Feb 2015 10:44:50 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Vijay Kilari Cc: Vijaya Kumar K , Julien Grall , Tim Deegan , Stefano Stabellini , xen-devel@lists.xenproject.org, Chen Baozi List-Id: xen-devel@lists.xenproject.org On Fri, 2015-02-20 at 15:56 +0530, Vijay Kilari wrote: > On Fri, Feb 20, 2015 at 3:44 PM, Ian Campbell wrote: > > On Thu, 2015-02-19 at 18:01 +0000, Julien Grall wrote: > >> Based on the discussion, what about waiting until someone complain about > >> GICv3 support on Xen 4.5? > > > > That sounds like a reasonable compromise. > > If Xen 4.5 claims GICv3 support, then it is better to backport vgic-v3 patches. > May be ThunderX is the only platform out there with GICv3 support. > At some point of time we might require ThunderX support on 4.5 release. > If you are going to backport only on-demand then it should be for now. Is ThunderX going to be available to purchase before the 4.6 release in the summer? > > > > > My potential backports list now contains: > > > > xen/arm: Bug fixes for the vGIC > > -> 15 patch series, many of which are tagged for backport. > > > > -> Julien: The list of GICv2 patches candidate for backporting are: #10, #11, > > #12, #13. > > fed3569 xen/arm: vgic-v2: Correctly set GICD_TYPER.CPUNumber > > 1fefa55 xen/arm: vgic-v2: Correctly handle RAZ/WI registers > > 26ea82f xen/arm: vgic-v2: Take the lock when writing into GICD_CTLR > > 10af92d xen/arm: vgic-v2: GICD_I{S, C}PENDR* are only word-accessible > > > > -> Julien: Based on the discussion, what about waiting until someone complain about > > GICv3 support on Xen 4.5? > > 8206d05 xen/arm: vgic-v3: Correctly set GICD_TYPER.IDbits > > 834551b xen/arm: vgic-v3: Correctly set GICD_TYPER.CPUNumber > > 5e6958a xen/arm: vgic-v3: Correctly handle RAZ/WI registers > > cfef895 xen/arm: vgic-v3: Correctly implement read into GICR_NSACR > > acf65e5 xen/arm: vgic-v3: Emulate correctly the re-distributor > > > > -> Not tagged for backport: > > 8d91d64 xen/arm: vgic-v3: Correctly handle GICD_CTLR > > 4636e9f xen/arm: vgic-v3: Set stride during domain initialization > > 196f4ef xen/arm: vgic-v3: Use a struct to describe contiguous rdist regions > > b697071 xen/arm: vgic-v3: Clarify which distributor is used in the common emulation > > a41d809 xen/arm: vgic: Drop iactive, ipend, pendsgi field > > 98e7c60 xen/arm: gic-v3: Update some comments in the code > > > > Does that tally with what you intended? > > > > Ian. > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel