From: Al Viro <viro@zeniv.linux.org.uk>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
David Miller <davem@davemloft.net>,
arnd@arndb.de, guoren@kernel.org, linux-csky@vger.kernel.org,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/3] sparc: port to copy_thread_tls() and struct kernel_clone_args
Date: Sun, 17 May 2020 23:13:46 +0100 [thread overview]
Message-ID: <20200517221346.GL23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <cfc07b63-29e6-cda9-c611-235e37970763@ilande.co.uk>
On Sun, May 17, 2020 at 05:34:34PM +0100, Mark Cave-Ayland wrote:
> FWIW if you're running a more recent version of QEMU (>=3.1) then you can also boot
> from the virtio-blk-pci device directly instead of having to switch back to the IDE
> device after installation as you have done above. Should be something like:
>
> qemu-system-sparc64 \
> -m 4096 \
> -device virtio-blk-pci,bus=pciB,drive=hd \
> -drive
> file=/home/brauner/.local/share/qemu/sparc64.img,format=raw,if=none,id=hd,bootindex=0 \
> -net nic \
> -net user \
> -nographic
>
> Note the removal of the legacy -boot argument and the addition of "bootindex=0" to
> the -drive argument.
Is virtio-blk-pci more resilent to lost interrupt bug introduced in
"sun4u: update PCI topology to include simba PCI bridges"? I hadn't tried
it yet (reverted to the last working mainline qemu commit for now); IDE
definitely is screwed by that - both the Linux and NetBSD drivers, actually.
A 50Mb worth of wget(1) is more than enough to trigger that crap;
commit 063833a6ec
Merge: d634fc0499 bcf9e2c2f2
Author: Peter Maydell <peter.maydell@linaro.org>
Date: Thu Oct 19 18:42:51 2017 +0100
Merge remote-tracking branch 'remotes/mcayland/tags/qemu-sparc-signed' into staging
hangs, d634fc0499 works, bcf9e2c2f2 hangs.
I hadn't looked into details (the branch itself is only two commits long, but it
incorporates an openbios update - 35 commits there, some obviously pci- and
sun4u-related), but it's really easy to reproduce - -m 1024 and -hda <image>
are probably the only relevant arguments. Even dd if=/dev/sda of=/dev/null bs=64m
is often enough to hang it, so I rather doubt that networking (e1000 on pciB,
FWIW, with tap for backend) has anything to do with that.
next prev parent reply other threads:[~2020-05-17 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 17:15 [PATCH 0/3] sparc: port to copy_thread_tls() and struct kernel_clone_args Christian Brauner
2020-05-12 17:15 ` [PATCH 1/3] sparc64: enable HAVE_COPY_THREAD_TLS Christian Brauner
2020-05-12 20:04 ` David Miller
2020-05-12 17:15 ` [PATCH 2/3] sparc: share process creation helpers between sparc and sparc64 Christian Brauner
2020-05-12 17:15 ` [PATCH 3/3] sparc: unconditionally enable HAVE_COPY_THREAD_TLS Christian Brauner
2020-05-12 20:06 ` [PATCH 0/3] sparc: port to copy_thread_tls() and struct kernel_clone_args David Miller
2020-05-17 15:01 ` Christian Brauner
2020-05-17 16:34 ` Mark Cave-Ayland
2020-05-17 22:13 ` Al Viro [this message]
2020-05-18 18:18 ` Al Viro
2020-05-18 18:23 ` Christian Brauner
2020-05-18 19:58 ` Mark Cave-Ayland
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=20200517221346.GL23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=arnd@arndb.de \
--cc=christian.brauner@ubuntu.com \
--cc=davem@davemloft.net \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=sparclinux@vger.kernel.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