All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Julien Grall <julien.grall@arm.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
	"sstabellini@kernel.org" <sstabellini@kernel.org>,
	Linuxarm <linuxarm@huawei.com>
Subject: Re: Xen Dom0 boot failure on platform that supports ARM GICv4
Date: Tue, 4 Sep 2018 16:02:08 +0000	[thread overview]
Message-ID: <5FC3163CFD30C246ABAA99954A238FA838780832@FRAEML521-MBX.china.huawei.com> (raw)
In-Reply-To: <f9d6b1ed-4797-3216-804e-d298fc71a31b@arm.com>



> -----Original Message-----
> From: Julien Grall [mailto:julien.grall@arm.com]
> Sent: 04 September 2018 12:22
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>;
> xen-devel@lists.xen.org
> Cc: sstabellini@kernel.org; Linuxarm <linuxarm@huawei.com>; Andre
> Przywara <andre.przywara@arm.com>
> Subject: Re: Xen Dom0 boot failure on platform that supports ARM GICv4

[...] 
 
> >> I may have an idea what is happening. As we populate more regions than
> >> necessary, it is possible that Linux is trying to access them. Would it
> >> be possible to add some debug in the Linux function gic_iterate_rdists
> >> to know what the kernel is trying to read?
> >
> > Ok, enabled earlycon for Dom0. Please find the log below,
> 
> Thank you for the log. I now have an idea what's is going wrong. The function
> gic_iterate_rdists can be used to go through all the re-distributor (for instance
> to check whether vLPIs is available).
> 
> Because some of the regions are empty (i.e not emulated), you end up to trap.
> Your
> patch solves the problem by making regions not empty in the case of GICv4. But
> I
> think this can also happen when the number of vCPUs for Dom0 get restricted.

Yes, that’s right. I didn’t consider that.

> Can you have a try at the patch below? I haven't tested on ACPI.
> 
> If that works for you, I will add the DT case, clean it up and send it.

Thanks for the patch. It works. Please CC me when you send the revised one,
I can retest and provide T-by.

Cheers,
Shameer

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2018-09-04 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 14:53 Xen Dom0 boot failure on platform that supports ARM GICv4 Shameerali Kolothum Thodi
2018-09-03 16:13 ` Julien Grall
2018-09-03 16:54   ` Shameerali Kolothum Thodi
2018-09-03 17:13     ` Julien Grall
2018-09-03 18:37       ` Shameerali Kolothum Thodi
2018-09-04 11:22         ` Julien Grall
2018-09-04 16:02           ` Shameerali Kolothum Thodi [this message]

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=5FC3163CFD30C246ABAA99954A238FA838780832@FRAEML521-MBX.china.huawei.com \
    --to=shameerali.kolothum.thodi@huawei.com \
    --cc=andre.przywara@arm.com \
    --cc=julien.grall@arm.com \
    --cc=linuxarm@huawei.com \
    --cc=sstabellini@kernel.org \
    --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.