From mboxrd@z Thu Jan  1 00:00:00 1970
From: Vijay Kilari <vijay.kilari@gmail.com>
Subject: Re: [PATCH v2 14/15] xen/arm: Add vgic support for GIC
	v3
Date: Thu, 10 Apr 2014 18:44:59 +0530
Message-ID: <CALicx6shv29w98GZqu+5BBNe5uO5gjSJRG6SJTQR-N1531Lc-g@mail.gmail.com>
References: <1396612593-443-1-git-send-email-vijay.kilari@gmail.com>
	<1396612593-443-15-git-send-email-vijay.kilari@gmail.com>
	<1397125402.9862.102.camel@kazak.uk.xensource.com>
	<CALicx6vbwSGeJpq_YTEmz8xdAG_QkVEAFMNKrtULmacDUeHbQA@mail.gmail.com>
	<1397127066.9862.123.camel@kazak.uk.xensource.com>
	<CALicx6vV9V_1dW3xTk8_=sva92MW4yWWeO7DoMC-qQYn7Qf_bQ@mail.gmail.com>
	<1397129195.9862.135.camel@kazak.uk.xensource.com>
	<CALicx6uzT-zu8p+AOPrNGQZdKjJ6fYLGzGCOG0H0bCnnrhLmBw@mail.gmail.com>
	<1397131712.9862.157.camel@kazak.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1397131712.9862.157.camel@kazak.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>, Vijaya Kumar K <vijaya.kumar@caviumnetworks.com>, Julien Grall <julien.grall@linaro.org>, xen-devel@lists.xen.org, Stefano Stabellini <stefano.stabellini@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Thu, Apr 10, 2014 at 5:38 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Thu, 2014-04-10 at 17:08 +0530, Vijay Kilari wrote:
>> On Thu, Apr 10, 2014 at 4:56 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> > On Thu, 2014-04-10 at 16:49 +0530, Vijay Kilari wrote:
>> >
>> >> I mean, I don't have V2 hardware to test any trivial changes that I do to
>> >> GIC v2. In all my patches, I am not making any changes to functionality of
>> >> v2 except code movement and changing names
>> >
>> > I can test it if necessary. Do you have access to fast models or
>> > anything similar?
>>
>> Currently I don't have one. I can setup.
>> Is it ok if I investigate on this later separately?
>
> I'm afraid that I don't want to add duplicated code to be cleaned up
> later. If this stuff can be shared then it should be done from the
> start. (These things have a habit of not happening otherwise).
>
Let me attempt and send a patch.
However I feel except vgic_distr_mmio_read & vgic_distr_mmio_write of
gicv2 code,
we can move all other functions to either header file (new file
vgic.h) or common code file (vgic.c)
which can be shared with gicv3.This is the simplest approach I think.

Also, in GICD, few register are changed between v2 & v3 ex: GICD_IROUTER

> Ian.
>