linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paulburton@kernel.org>
To: Jun Sun <jsun@junsun.net>
Cc: qemu-discuss@nongnu.org, debian-mips@lists.debian.org,
	linux-mips@vger.kernel.org, lixing <13699171092@139.com>
Subject: Re: debian bootup hangs on qemu-system-mips64el
Date: Mon, 13 Jan 2020 11:08:23 -0800	[thread overview]
Message-ID: <20200113190823.xa36ojktxoudster@pburton-laptop> (raw)
In-Reply-To: <CAP5Nno5jXhgbryGqDX9j3TAUwXmsBnRnvNuh2MJpDHs-bSG1Cg@mail.gmail.com>

Hi Jun Sun,

On Sun, Jan 12, 2020 at 06:14:12PM -0800, Jun Sun wrote:
> On Sun, Jan 12, 2020 at 11:58 AM Aurelien Jarno <aurelien@aurel32.net> wrote:
> > On 2020-01-12 11:34, Jun Sun wrote:
> > > Are you sure QEMU/MIPS does not support SMP?  Below link written in
> > > 2016 clearly shows something was working then.
> > >
> > > https://www.mips.com/blog/how-to-run-smp-linux-in-qemu-on-a-mips64-release-6-cpu/
> >
> > It's not supported for the malta/mips64r2 combination you are trying to
> > use. It's clearly possible that it is supported for mips64r6, but it's a
> > different instruction set, so you can't run a standard Debian
> > distribution on it.
> 
> How do I specify mips64r6 cpu to start qemu?  A simple cpu listing
> below shows no such CPU.  If mips64r6 is indeed supported with SMP, I
> would think mips64r2 userland should run fine.

I know that using QEMU's I6400 or I6500 CPU emulation works fine with
SMP as far as -smp 8. It emulates a single core system with up to 8 VPs
(hardware threads), and Linux works fine with it. I most often use the
Boston board emulation with a 64r6el_defconfig kernel for this, but it
ought to work for Malta too.

Both I6400 & I6500 are MIPS64r6 CPUs, so as Aurelien said you'd need to
ensure you're using a suitable MIPSr6 root filesystem.

If you wanted to run as I do it'd go something like this:

$ qemu-system-mips64el \
    -M boston \
    -cpu I6500 \
    -smp 8 \
    -kernel arch/mips/boot/vmlinux.gz.itb

Where that's run from the root of a kernel source tree within which
you've built a 64r6el_defconfig kernel.

Not sure what the behavior is with older CPUs; QEMU's CM & CPC emulation
is somewhat incomplete, and whilst I6400 & I6500 have a relatively
straightforward VP model older CPUs have the more complex MT ASE with
VPEs & TCs to worry about.

Thanks,
    Paul

  reply	other threads:[~2020-01-13 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAP5Nno5CPjV2mcf2ny8AtcC2ziqDkv6Kc7f4hCq1TF4DvKvJkw@mail.gmail.com>
2020-01-05  4:46 ` debian bootup hangs on qemu-system-mips64el Jun Sun
2020-01-09 21:24   ` Aurelien Jarno
2020-01-12 19:34     ` Jun Sun
2020-01-12 19:57       ` Aurelien Jarno
2020-01-13  2:14         ` Jun Sun
2020-01-13 19:08           ` Paul Burton [this message]
2020-01-13  1:17       ` Jiaxun Yang
2020-01-13  2:35         ` Jun Sun
2020-01-13  3:23           ` Huacai Chen
2020-01-13  3:29           ` Jiaxun Yang

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=20200113190823.xa36ojktxoudster@pburton-laptop \
    --to=paulburton@kernel.org \
    --cc=13699171092@139.com \
    --cc=debian-mips@lists.debian.org \
    --cc=jsun@junsun.net \
    --cc=linux-mips@vger.kernel.org \
    --cc=qemu-discuss@nongnu.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).