xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xenproject.org
Cc: stefano.stabellini@citrix.com, Zoltan Kiss <zoltan.kiss@huawei.com>
Subject: Re: [PATCH v2 5/7] xen/arm: gic: Check the size of the CPU and vCPU interface retrieved from DT
Date: Thu, 1 Oct 2015 13:54:23 +0100	[thread overview]
Message-ID: <1443704063.11707.41.camel@citrix.com> (raw)
In-Reply-To: <560D2A7A.20101@citrix.com>

On Thu, 2015-10-01 at 13:43 +0100, Julien Grall wrote:
> On 01/10/15 13:08, Ian Campbell wrote:
> > On Tue, 2015-09-29 at 17:21 +0100, Julien Grall wrote:
> > > @@ -641,7 +643,30 @@ static int __init gicv2_init(void)
> > >          panic("GICv2: Cannot find the maintenance IRQ");
> > >      gicv2_info.maintenance_irq = res;
> > >  
> > > -    /* TODO: Add check on distributor, cpu size */
> > > +    /* TODO: Add check on distributor */
> > > +
> > > +    /*
> > > +     * The GICv2 CPU interface should at least be 8KB. Although,
> > > most of the DT
> > > +     * doesn't correctly set it and use the GICv1 CPU interface size
> > > (i.e 4KB).
> > > +     * Warn and then fixup.
> > > +     */
> > > +    if ( csize < SZ_8K )
> > > +    {
> > > +        printk(XENLOG_WARNING "GICv2: WARNING: "
> > > +               "The CPU interface size is wrong: %#"PRIx64
> > > +               " expected %#x\n",
> > 
> > You missed fixing a split string constant here.
> 
> Hmmm right. Although, I think the sentence is small so I don't need to
> rewrite it.

Correct. (If it weren't for the other comments I'd probably have just
unwrapped it when I committed)

> There is a lot small things to fix in this patch series. Shall I resend
> it?

Yes, please. I'm in the process of applying #1..#4 so you might want to
wait until they show up in staging and then rebase.

  reply	other threads:[~2015-10-01 12:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 16:21 [PATCH v2 0/7] xen/arm: gic-v2: Detect automatically aliased GIC 400 Julien Grall
2015-09-29 16:21 ` [PATCH v2 1/7] xen/arm: gic: Make it clear the GIC node is passed to make_hwdom_dt_node Julien Grall
2015-09-29 16:21 ` [PATCH v2 2/7] xen/arm: Retrieve the correct number of cells when building dom0 DT Julien Grall
2015-10-01 11:57   ` Ian Campbell
2015-09-29 16:21 ` [PATCH v2 3/7] xen/arm: Warn when a device tree path will be re-used by Xen Julien Grall
2015-10-01 12:01   ` Ian Campbell
2015-10-01 12:39     ` Julien Grall
2015-09-29 16:21 ` [PATCH v2 4/7] xen/arm: vgic-v2: Drop cbase from arch_domain Julien Grall
2015-09-29 16:21 ` [PATCH v2 5/7] xen/arm: gic: Check the size of the CPU and vCPU interface retrieved from DT Julien Grall
2015-10-01 12:08   ` Ian Campbell
2015-10-01 12:43     ` Julien Grall
2015-10-01 12:54       ` Ian Campbell [this message]
2015-09-29 16:21 ` [PATCH v2 6/7] xen/arm: gic-v2: Automatically detect aliased GIC400 Julien Grall
2015-10-01 12:10   ` Ian Campbell
2015-09-29 16:21 ` [PATCH v2 7/7] xen/arm: platform: Drop the quirks callback Julien Grall
2015-09-29 16:55   ` Julien Grall
2015-10-01 12:10     ` Ian Campbell
2015-10-01 12:56 ` [PATCH v2 0/7] xen/arm: gic-v2: Detect automatically aliased GIC 400 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=1443704063.11707.41.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zoltan.kiss@huawei.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).