All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Vijay Kilari <vijay.kilari@gmail.com>,
	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>,
	Tim Deegan <tim@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	manish.jaggi@caviumnetworks.com
Subject: Re: [PATCH v7 1/5] xen/arm: Add support for GIC v3
Date: Tue, 22 Jul 2014 12:15:14 +0100	[thread overview]
Message-ID: <53CE47C2.3000801@linaro.org> (raw)
In-Reply-To: <CALicx6uNCOu67khRGVLtCRBPBQrH1F_Q1YjSm+_FfWzq7G+uoA@mail.gmail.com>



On 22/07/14 12:12, Vijay Kilari wrote:
> On Tue, Jul 22, 2014 at 4:25 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> On Tue, 2014-07-22 at 16:19 +0530, Vijay Kilari wrote:
>>>>
>>>>>>> + * Additional registers defined in GIC v3.
>>>>>>> + * Common GICD registers are defined in gic.h
>>>>>>> + */
>>>>>>> +
>>>>>>> +#define GICD_STATUSR                 (0x010)
>>>>>>> [...][
>>>>>>> +#define GICV3_GICD_PIDR0             (0x92)
>>>>>>
>>>>>> What is the distinction between variables with GIC[DR]_ prefixes and
>>>>>> those with GICV3_GIC[DR]_ ones?
>>>>>
>>>>> GICV3 is prefixed for indicating that there are values not the addresses.
>>>>> In anycase I will remove GICV3 prefixes and postfix _VAL
>>>>
>>>> You mean the value used when emulating a read, I think?
>>>
>>>     Yes, it is used in gicv3 driver for checking presence of re-distributor
>>
>> In the phsyical h/w? That sounds wrong. 0x92 is just one possible value
>> of this register (and the spec says it should be 0x94...). I don't see
>> you using this #define in that way anywhere though so perhaps I've
>> misunderstood.
>
> I am using 20.0 version. which specifies 0x92 for ARM implementations of GICv3.
> May be other vendors can use different value. So it is better propagate hw value
> for emulation
>
>   GICD_PIDR0:
>   Bits [7:0]. Bits [7:0] of the ARM-defined DevID field. This field is 0x92 in
> ARM implementations of a GICv3 or later Distributor.
>
> In any case, GICD_PIDR0 is not used by gicv3 driver. GICD_PIDR2 & GICR_PIDR2 are
>   used where check is made on ARCH_REV [7:4]
>
>>
>>> and also in vgicv3 for emulating read.
>>
>> I wonder if we should instead propagate the underlying hardware value?
>
> Yes,we can propagate hardware value.

I don't think we should propagate the hardware value. We may emulate a 
different distributor than the hardware one. In this case, 
implementation defined register won't work as expected by the kernel.

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-07-22 11:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 12:51 [PATCH v7 0/5] xen/arm: Add GICv3 support vijay.kilari
2014-07-11 12:51 ` [PATCH v7 1/5] xen/arm: Add support for GIC v3 vijay.kilari
2014-07-16 11:41   ` Ian Campbell
2014-07-22  9:48     ` Vijay Kilari
2014-07-22 10:01       ` Julien Grall
2014-07-22 10:43         ` Ian Campbell
2014-07-22 11:13           ` Julien Grall
2014-07-22 11:30             ` Vijay Kilari
2014-07-22 11:45               ` Ian Campbell
2014-07-22 10:39       ` Ian Campbell
2014-07-22 10:49         ` Vijay Kilari
2014-07-22 10:55           ` Ian Campbell
2014-07-22 11:12             ` Vijay Kilari
2014-07-22 11:15               ` Julien Grall [this message]
2014-07-22 11:19                 ` Ian Campbell
2014-07-11 12:51 ` [PATCH v7 2/5] xen/arm: Add virtual GICv3 support vijay.kilari
2014-07-14 15:59   ` Julien Grall
2014-07-16 11:47   ` Ian Campbell
2014-07-16 11:56     ` Vijay Kilari
2014-07-11 12:51 ` [PATCH v7 3/5] xen/arm: Update Dom0 GIC dt node with GICv3 information vijay.kilari
2014-07-16 11:53   ` Ian Campbell
2014-07-11 12:51 ` [PATCH v7 4/5] xen/arm: add SGI handling for GICv3 vijay.kilari
2014-07-11 13:43   ` Julien Grall
2014-07-11 14:08     ` Ian Campbell
2014-07-11 14:12       ` Julien Grall
2014-07-11 14:18         ` Ian Campbell
2014-07-22 13:48   ` Stefano Stabellini
2014-07-22 14:13     ` Vijay Kilari
2014-07-23  5:48       ` Vijay Kilari
2014-07-23 10:35         ` Stefano Stabellini
2014-07-11 12:51 ` [PATCH v7 5/5] xen/arm: check for GICv3 platform support vijay.kilari
2014-07-16 12:11   ` Ian Campbell
2014-07-16 10:35 ` [PATCH v7 0/5] xen/arm: Add GICv3 support Ian Campbell
2014-07-16 11:47   ` Vijay Kilari
2014-07-16 12:38     ` Ian Campbell
2014-07-16 13:32       ` Ian Campbell
2014-07-23 10:51         ` Vijay Kilari
2014-07-23 11:31           ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53CE47C2.3000801@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=Prasun.Kapoor@caviumnetworks.com \
    --cc=manish.jaggi@caviumnetworks.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=vijay.kilari@gmail.com \
    --cc=vijaya.kumar@caviumnetworks.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.