From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/8] arm/arm64: KVM: dynamic VGIC sizing
Date: Thu, 25 Sep 2014 15:35:31 +0200 [thread overview]
Message-ID: <20140925133531.GA15736@cbox> (raw)
In-Reply-To: <54240E20.8060505@huawei.com>
On Thu, Sep 25, 2014 at 08:44:16PM +0800, Shannon Zhao wrote:
> Hi all,
>
> I have a problem that I want to ask for your advice.
> Before I send this mail to Marc and Christoffer. But it seems that they are busy or not online recently.
>
> I git clone Marc's "kvmtool-vgic-dyn" branch and run it on Fastmodel Cortex-A57*4 with qemu 2.1.0.
> https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
>
> I want to do repeated lifecycle test. The test is that start 2 VMs, sleep 10 and do pkill qemu.
> Test script is following:
> #!/bin/sh
> while true
> do
> qemu-system-aarch64 \
> -enable-kvm -smp 4 \
> -kernel Image \
> -m 512 -machine virt,kernel_irqchip=on \
> -initrd guestfs.cpio.gz \
> -cpu host \
> -chardev pty,id=pty0,mux=on -monitor chardev:pty0 \
> -serial chardev:pty0 -daemonize \
> -vnc 0.0.0.0:0 \
> -append "rdinit=/sbin/init console=ttyAMA0 mem=512M root=/dev/ram earlyprintk=pl011,0x9000000 rw" &
>
> qemu-system-aarch64 \
> -enable-kvm -smp 4 \
> -kernel Image \
> -m 512 -machine virt,kernel_irqchip=on \
> -initrd guestfs.cpio.gz \
> -cpu host \
> -chardev pty,id=pty0,mux=on -monitor chardev:pty0 \
> -serial chardev:pty0 -daemonize \
> -vnc 0.0.0.0:1 \
> -append "rdinit=/sbin/init console=ttyAMA0 mem=512M root=/dev/ram earlyprintk=pl011,0x9000000 rw" &
> sleep 10
> pkill qemu
> done
>
> After repeating sometimes there is something wrong happened as followed.
> Look forward for your reply.
> Thanks,
> Shannon
>
Hi Shannon,
This appears to be related to a bug in vgic_set_attr() which messes up
the bitmap initialization, I'm working on a patch.
-Christoffer
next prev parent reply other threads:[~2014-09-25 13:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 11:09 [PATCH v4 0/8] arm/arm64: KVM: dynamic VGIC sizing Marc Zyngier
2014-09-11 11:09 ` [PATCH v4 1/8] KVM: ARM: vgic: plug irq injection race Marc Zyngier
2014-09-11 11:09 ` [PATCH v4 2/8] arm/arm64: KVM: vgic: switch to dynamic allocation Marc Zyngier
2014-09-11 22:36 ` Christoffer Dall
2014-09-12 9:13 ` Marc Zyngier
2014-09-12 17:43 ` Christoffer Dall
2014-09-11 11:09 ` [PATCH v4 3/8] arm/arm64: KVM: vgic: Parametrize VGIC_NR_SHARED_IRQS Marc Zyngier
2014-09-11 11:09 ` [PATCH v4 4/8] arm/arm64: KVM: vgic: kill VGIC_MAX_CPUS Marc Zyngier
2014-09-11 11:09 ` [PATCH v4 5/8] arm/arm64: KVM: vgic: handle out-of-range MMIO accesses Marc Zyngier
2014-09-11 11:09 ` [PATCH v4 6/8] arm/arm64: KVM: vgic: kill VGIC_NR_IRQS Marc Zyngier
2014-09-11 22:37 ` Christoffer Dall
2014-09-11 11:09 ` [PATCH v4 7/8] arm/arm64: KVM: vgic: delay vgic allocation until init time Marc Zyngier
2014-09-11 11:09 ` [PATCH v4 8/8] arm/arm64: KVM: vgic: make number of irqs a configurable attribute Marc Zyngier
2014-09-11 22:38 ` Christoffer Dall
2014-09-25 12:44 ` [PATCH v4 0/8] arm/arm64: KVM: dynamic VGIC sizing Shannon Zhao
2014-09-25 13:35 ` Christoffer Dall [this message]
2014-09-26 1:15 ` Shannon Zhao
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=20140925133531.GA15736@cbox \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).