From: Guenter Roeck <linux@roeck-us.net>
To: Qais Yousef <qsyousef@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-next@vger.kernel.org, linux-mips@linux-mips.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 14 (mips qemu failure bisected)
Date: Thu, 17 Mar 2016 05:43:50 -0700 [thread overview]
Message-ID: <56EAA686.5010300@roeck-us.net> (raw)
In-Reply-To: <CA+mqd+5AUfGSh1WvLa5bOt-HQM=eA+BmLeb7_xZo+-tswLcqiQ@mail.gmail.com>
On 03/16/2016 10:25 PM, Qais Yousef wrote:
[ ... ]
>
> Yeah it is assumed that a Malta should always have a GIC and no one got around to fix this in qemu yet.
>
> I can only improve on the patch to do
>
> if (!ipidomain && nr_cpu_ids == 1)
> return 0;
>
> Which is more generic way to do it. I think a WARN_ON () would still be useful as SMP without ipis will not work really.
>
> I can send a proper patch if Ralf is OK with that.
>
> I got the console output from qemu by the way. I didn't use your script though.
>
What command line did you use ?
Thanks,
Guenter
next prev parent reply other threads:[~2016-03-17 12:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 6:40 linux-next: Tree for Mar 14 Stephen Rothwell
2016-03-14 14:37 ` Guenter Roeck
2016-03-14 16:51 ` James Morse
2016-03-14 19:18 ` Guenter Roeck
2016-03-14 23:55 ` Michael Ellerman
2016-03-15 2:31 ` Guenter Roeck
2016-03-15 5:26 ` linux-next: Tree for Mar 14 (mips qemu failure bisected) Guenter Roeck
2016-03-15 21:55 ` Qais Yousef
2016-03-16 0:17 ` Guenter Roeck
2016-03-16 13:22 ` Guenter Roeck
2016-03-16 20:27 ` Qais Yousef
2016-03-16 22:17 ` Qais Yousef
2016-03-17 2:10 ` Guenter Roeck
2016-03-17 2:36 ` Guenter Roeck
[not found] ` <CA+mqd+5AUfGSh1WvLa5bOt-HQM=eA+BmLeb7_xZo+-tswLcqiQ@mail.gmail.com>
2016-03-17 12:43 ` Guenter Roeck [this message]
2016-03-15 0:30 ` linux-next: Tree for Mar 14 Sergey Senozhatsky
2016-03-15 6:43 ` Wolfram Sang
2016-03-15 6:52 ` Sergey Senozhatsky
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=56EAA686.5010300@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=qsyousef@gmail.com \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
/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).