xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, Julien Grall <julien.grall@linaro.org>,
	andre.przywara@linaro.org
Subject: [PATCH v2 0/2] xen/arm: GICv3: Only initialize ITS when LPIs are available
Date: Wed, 24 Jan 2018 18:26:14 +0000	[thread overview]
Message-ID: <20180124182616.3384-1-julien.grall@linaro.org> (raw)

Hi all,

This small patch series fix an issue I discovered when using the Foundation
model and the DT provided by Linux upstream.

Indeed the Device-Tree is exposing an ITS but LPIs are not available.
Resulting to an early crash on Xen.

Whilst this looks a DT issue, Linux is able to cope with it. So I think Xen
should also cope with such DT.

Cheers,

Julien Grall (2):
  xen/arm: GICv3: Parse ITS information from the firmware tables later
    on
  xen/arm: GICv3: Only initialize ITS when the distributor supports
    LPIs.

 xen/arch/arm/gic-v3-its.c        | 47 +++++++++++++++++++++++++---------------
 xen/arch/arm/gic-v3.c            | 19 +++++++++-------
 xen/include/asm-arm/gic_v3_its.h | 12 ----------
 3 files changed, 41 insertions(+), 37 deletions(-)

-- 
2.11.0


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

             reply	other threads:[~2018-01-24 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 18:26 Julien Grall [this message]
2018-01-24 18:26 ` [PATCH v2 1/2] xen/arm: GICv3: Parse ITS information from the firmware tables later on Julien Grall
2018-01-30 17:55   ` Stefano Stabellini
2018-01-24 18:26 ` [PATCH v2 2/2] xen/arm: GICv3: Only initialize ITS when the distributor supports LPIs Julien Grall
2018-01-30 17:55   ` Stefano Stabellini

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=20180124182616.3384-1-julien.grall@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=andre.przywara@linaro.org \
    --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 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).