From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH] xen/arm: Handle translated addresses for hardware domains in GICv2 Date: Tue, 24 Feb 2015 17:09:01 +0000 Message-ID: <54ECB02D.8050706@linaro.org> References: <1424425080-3927-1-git-send-email-frediano.ziglio@huawei.com> <54EB5593.5070508@linaro.org> <1424793700.27930.368.camel@citrix.com> <54ECA515.2090909@linaro.org> <1424797207.20243.10.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1424797207.20243.10.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Frediano Ziglio , Stefano Stabellini , Tim Deegan , zoltan.kiss@huawei.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 24/02/15 17:00, Ian Campbell wrote: >> Furthermore, the current code rely on how the device has been written. >> For instance the calxeda device tree is using ranges and, therefore, the >> regs contains offset. >> Fortunately, the offset and the translated address is the same. >> >>> I certainly wouldn't want to backport a fix to gic v2 only. >> >> As we didn't backport other patches related to GICv3, it would not make >> much sense to backport a similar fix for GICv3.. > > We should consider each patch/series on its own merits. The other GICv3 > fixes were far more invasive and complicated than what is being done > here. Agreed. Just it doesn't make sense to backport new GICv3 patches as we know that without the previous series any Linux >= 3.19 won't boot at all. Regards, -- Julien Grall