xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Shanker Donthineni <shankerd@codeaurora.org>
To: Julien Grall <julien.grall@arm.com>,
	xen-devel <xen-devel@lists.xensource.com>
Cc: Philip Elcan <pelcan@codeaurora.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Vikram Sethi <vikrams@codeaurora.org>
Subject: Re: [PATCH] arm/gic-v3: Fix driver probe fail on GICv4 hardware
Date: Fri, 27 May 2016 08:48:22 -0500	[thread overview]
Message-ID: <57485026.7030304@codeaurora.org> (raw)
In-Reply-To: <57483F0E.1080009@arm.com>

Hi Julien,

On 05/27/2016 07:35 AM, Julien Grall wrote:
> Hello Shanker,
>
> Please mention in the title and the commit message that is patch is ACPI only.
>

I'll change commit text.
> On 27/05/16 00:59, Shanker Donthineni wrote:
>> The current driver probe fails on hardware which has GICv4 version,
>> even though it is fully compatible to GICv3. This patch fixes the
>> issue by registering the same probe function for GICv4 hardware.
>>
>> Signed-off-by: Shanker Donthineni <shankerd@codeaurora.org>
>> ---
>>   xen/arch/arm/gic-v3.c     | 13 +++++++++++++
>>   xen/include/asm-arm/gic.h |  1 +
>>   2 files changed, 14 insertions(+)
>>
>> diff --git a/xen/arch/arm/gic-v3.c b/xen/arch/arm/gic-v3.c
>> index a095064..594cf6e 100644
>> --- a/xen/arch/arm/gic-v3.c
>> +++ b/xen/arch/arm/gic-v3.c
>> @@ -1604,10 +1604,23 @@ static int __init gicv3_acpi_preinit(const void *data)
>>       return 0;
>>   }
>>
>> +static int __init gicv4_acpi_preinit(const void *data)
>> +{
>> +    gicv3_info.hw_version = GIC_V4;
>
> It will crash Xen as soon as DOM0 is created (see the BUG() in arch_domain_create). Please test any patch before sending on the ML.
>
> Anyway, there is no support of GICv4 in Xen. Instead Xen will drive it using the GICv3 driver. So the hardware version should be GIC_V3 here.
>
Yes, I know I am going to fix in a separate to fix dom0 boot issue some thing like below.

 diff --git a/xen/arch/arm/domain.c b/xen/arch/arm/domain.c
index 1365b4a..56a47f5 100644
--- a/xen/arch/arm/domain.c
+++ b/xen/arch/arm/domain.c
@@ -571,6 +571,11 @@ int arch_domain_create(struct domain *d, unsigned int domcr_flags,
             d->arch.vgic.version = GIC_V3;
             break;
 
+        case GIC_V4:
+            config->gic_version = XEN_DOMCTL_CONFIG_GIC_V3;
+            d->arch.vgic.version = GIC_V3;
+            break;
+
         default:
             BUG();
         }

-- 
Shanker Donthineni
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-05-27 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 23:59 [PATCH] arm/gic-v3: Fix driver probe fail on GICv4 hardware Shanker Donthineni
2016-05-27 12:35 ` Julien Grall
2016-05-27 13:48   ` Shanker Donthineni [this message]
2016-05-27 14:07     ` Julien Grall
2016-05-27 14:31       ` Shanker Donthineni
2016-05-27 15:00         ` Julien Grall

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=57485026.7030304@codeaurora.org \
    --to=shankerd@codeaurora.org \
    --cc=julien.grall@arm.com \
    --cc=pelcan@codeaurora.org \
    --cc=sstabellini@kernel.org \
    --cc=vikrams@codeaurora.org \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).