All of lore.kernel.org
 help / color / mirror / Atom feed
From: julien.grall@arm.com
To: xen-devel@lists.xenproject.org
Cc: Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>,
	andre.przywara@arm.com, Julien Grall <julien.grall@arm.com>,
	sstabellini@kernel.org
Subject: [PATCH 3/3] xen/arm: domain_builder: irq sanity check logic fix
Date: Tue, 27 Feb 2018 15:15:55 +0000	[thread overview]
Message-ID: <20180227151555.1953-4-julien.grall@arm.com> (raw)
In-Reply-To: <20180227151555.1953-1-julien.grall@arm.com>

From: Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>

Since commit "xen/arm: domain_build: Rework the way to allocate the
event channel interrupt", it is not possible for an irq to be both below 16
and greater/equal than 32.

Also fix the reference to linux documentation while we're at it.

Signed-off-by: Stewart Hildebrand <stewart.hildebrand@dornerworks.com>
Signed-off-by: Julien Grall <julien.grall@arm.com>
[Slightly rework the commit message]
---
 xen/arch/arm/domain_build.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index ed1a393bb5..28ee876b92 100644
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -503,9 +503,10 @@ static void set_interrupt_ppi(gic_interrupt_t interrupt, unsigned int irq,
 {
     __be32 *cells = interrupt;
 
-    BUG_ON(irq < 16 && irq >= 32);
+    BUG_ON(irq < 16);
+    BUG_ON(irq >= 32);
 
-    /* See linux Documentation/devictree/bindings/arm/gic.txt */
+    /* See linux Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt */
     dt_set_cell(&cells, 1, 1); /* is a PPI */
     dt_set_cell(&cells, 1, irq - 16); /* PPIs start at 16 */
     dt_set_cell(&cells, 1, (cpumask << 8) | level);
-- 
2.11.0


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

  parent reply	other threads:[~2018-02-27 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 15:15 [PATCH 0/3] xen/arm: Rework the way to allocate event channel IRQ for hwdom julien.grall
2018-02-27 15:15 ` [PATCH 1/3] xen/arm: domain_build: Prepare DTB/ACPI tables after specific mappings julien.grall
2018-03-02 23:10   ` Stefano Stabellini
2018-02-27 15:15 ` [PATCH 2/3] xen/arm: domain_build: Rework the way to allocate the event channel interrupt julien.grall
2018-03-02 23:10   ` Stefano Stabellini
2018-02-27 15:15 ` julien.grall [this message]
2018-03-02 23:10   ` [PATCH 3/3] xen/arm: domain_builder: irq sanity check logic fix 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=20180227151555.1953-4-julien.grall@arm.com \
    --to=julien.grall@arm.com \
    --cc=Stewart.Hildebrand@dornerworks.com \
    --cc=andre.przywara@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.