mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javi Merino <javi.merino@arm.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Nicolas Pitre <nico@linaro.org>
Subject: Re: [PATCH] irqchip: gic: Don't complain in gic_get_cpumask() if UP system
Date: Fri, 12 Jul 2013 12:13:22 +0100	[thread overview]
Message-ID: <20130712111322.GC3213@e102654-lin.cambridge.arm.com> (raw)
In-Reply-To: <1373067573-29946-1-git-send-email-sboyd@codeaurora.org>

On Sat, Jul 06, 2013 at 12:39:33AM +0100, Stephen Boyd wrote:
> In a uniprocessor implementation the interrupt processor targets
> registers are read-as-zero/write-ignored (RAZ/WI). Unfortunately
> gic_get_cpumask() will print a critical message saying
> 
>  GIC CPU mask not found - kernel will fail to boot.
> 
> if these registers all read as zero, but there won't actually be
> a problem on uniprocessor systems and the kernel will boot just
> fine. Skip this check if we're running a UP kernel or if we
> detect that the hardware only supports a single processor.
> 
> Cc: Nicolas Pitre <nico@linaro.org>
> Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
> 
> Maybe we should just drop the check entirely? It looks like it may
> just be debug code that won't ever trigger in practice, even on the
> 11MPCore that caused this code to be introduced.

I agree, we should drop the check.  It's annoying in uniprocessors and
unlikely to be found in the real world unless your gic entry in the dt
is wrong.


  reply	other threads:[~2013-07-12 11:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 23:39 Stephen Boyd
2013-07-12 11:13 ` Javi Merino [this message]
2013-07-12 12:10   ` Stephen Boyd
2013-07-17 21:53     ` Stephen Boyd
2013-07-17 22:34       ` Nicolas Pitre
2013-07-17 22:36         ` Stephen Boyd
2013-07-17 22:53           ` Nicolas Pitre
2013-07-17 23:06             ` Stephen Boyd
2013-08-22 18:43               ` Stephen Boyd
2013-08-22 18:59                 ` Nicolas Pitre
2013-08-23  4:35                   ` Stephen Boyd
2013-08-23  4:51                     ` Nicolas Pitre
2013-08-23  9:15                       ` Russell King - ARM Linux
2013-07-20  7:27 ` Bedia, Vaibhav
2013-07-23 17:01   ` Stephen Boyd
2015-01-31  0:43 Stephen Boyd
2015-01-31  7:09 ` Felipe Balbi
2015-02-12  3:51   ` Nishanth Menon
2015-02-01 21:25 ` Stefan Agner

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=20130712111322.GC3213@e102654-lin.cambridge.arm.com \
    --to=javi.merino@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@linaro.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=sboyd@codeaurora.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

all inboxes | Powered by JetHome®