From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: Regular oops on shutdown of KVM/ARM64 machines with VGA device
Date: Tue, 30 Jun 2015 11:34:59 +0100 [thread overview]
Message-ID: <559270D3.8030305@arm.com> (raw)
In-Reply-To: <CAL5wTH7EUh0ciutXKs2s-4VjKnRM65QmrUQQiRdM=R+_VXi6DA@mail.gmail.com>
On 30/06/15 08:54, Dirk M?ller wrote:
> Hi Marc,
>
>> Also, care to provide some hints about your kernel configuration?
>
> I believe the relevant parameters are:
>
> CONFIG_PGTABLE_LEVELS=4
> # CONFIG_ARM64_64K_PAGES is not set
> # CONFIG_ARM64_VA_BITS_39 is not set
> CONFIG_ARM64_VA_BITS_48=y
> CONFIG_ARM64_VA_BITS=48
> CONFIG_KVM_MMIO=y
> CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y
> CONFIG_KVM_COMPAT=y
> CONFIG_VIRTUALIZATION=y
> CONFIG_KVM=y
> CONFIG_KVM_ARM_HOST=y
> CONFIG_KVM_ARM_MAX_VCPUS=4
>
>
> the full config is here: http://pastebin.com/raw.php?i=GKAaVLYE
>
>> What is the VGA device you mention in $subject?
>> A QEMU command line so that we can try and reproduce the issue you're
>> seeing?
>
> with qemu 2.3.0:
>
> qemu-system-aarch64 --enable-kvm -M virt -cpu host -vnc :4 -bios
> /usr/share/qemu/qemu-uefi-aarch64.bin -m 1G -device VGA
>
> then connecting to the vnc to cause the VGA device to be initialized,
> and then simply ctrl-c'ing the qemu process, you'll get this crash
> 100% of each and every time. If you want additional debug output or
> try out something, just let me know and I'll be happy to provide you
> with it.
Can try the following patch?
diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mmu.c
index 7b42012..d902a53 100644
--- a/arch/arm/kvm/mmu.c
+++ b/arch/arm/kvm/mmu.c
@@ -109,7 +109,7 @@ static void kvm_flush_dcache_pud(pud_t pud)
*/
static void stage2_dissolve_pmd(struct kvm *kvm, phys_addr_t addr, pmd_t *pmd)
{
- if (!kvm_pmd_huge(*pmd))
+ if (pmd_none(*pmd) || !kvm_pmd_huge(*pmd))
return;
pmd_clear(pmd);
It seems to fix the issue for me, though with a relatively different
configuration.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-06-30 10:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 21:16 Regular oops on shutdown of KVM/ARM64 machines with VGA device Dirk Müller
2015-06-29 10:03 ` Mark Rutland
2015-06-29 12:55 ` Marc Zyngier
2015-06-30 7:54 ` Dirk Müller
2015-06-30 10:34 ` Marc Zyngier [this message]
2015-06-30 16:16 ` Dirk Müller
2015-06-30 16:20 ` Marc Zyngier
2015-06-30 18:50 ` Christoffer Dall
2015-07-01 8:20 ` Marc Zyngier
2015-07-01 11:27 ` Catalin Marinas
2015-07-01 11:44 ` Steve Capper
2015-07-01 12:05 ` Christoffer Dall
2015-06-30 7:46 ` Dirk Müller
2015-06-30 9:04 ` Mark Rutland
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=559270D3.8030305@arm.com \
--to=marc.zyngier@arm.com \
--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).