qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: david@gibson.dropbear.id.au, imammedo@redhat.com
Subject: [Qemu-devel] Segfault with coalesced mmio and boot CPU removal
Date: Wed, 27 Jul 2016 08:22:51 +0530	[thread overview]
Message-ID: <20160727025251.GF7036@in.ibm.com> (raw)

Hi,

Coalesced mmio buffer is part of vCPU 0's kvm_run mmap'ed area
and with the introduction of CPU hotplug, vCPU 0 can be removed on
PowerPC leading to the below seen segfault in QEMU.

0x00000000100a1d34 in kvm_flush_coalesced_mmio_buffer ()
    at qemu/kvm-all.c:1828
1828	        while (ring->first != ring->last) {

#0  0x00000000100a1d34 in kvm_flush_coalesced_mmio_buffer ()
    at qemu/kvm-all.c:1828
#1  0x00000000100160e0 in qemu_flush_coalesced_mmio_buffer ()
    at qemu/exec.c:1206
#2  0x00000000100a961c in memory_region_transaction_begin ()
    at qemu/memory.c:904
#3  0x00000000100add90 in memory_region_set_enabled (mr=0x3fff96420310, enabled=false)
    at qemu/memory.c:1974
#4  0x00000000104577b0 in pci_default_write_config (d=0x3fff96420010, addr=4, val_in=258, 
    l=2) at hw/pci/pci.c:1340
#5  0x0000000010465d0c in pci_host_config_write_common (pci_dev=0x3fff96420010, addr=4, 
    limit=4096, val=258, len=2) at hw/pci/pci_host.c:66
#6  0x0000000010170500 in finish_write_pci_config (spapr=0x10fc6290, 
    buid=576460752840294400, addr=4, size=2, val=258, rets=20547656)
    at qemu/hw/ppc/spapr_pci.c:199
#7  0x0000000010170620 in rtas_ibm_write_pci_config (cpu=0x3fffac590010, spapr=0x10fc6290, 
    token=8215, nargs=5, args=20547636, nret=1, rets=20547656)
    at qemu/hw/ppc/spapr_pci.c:223
#8  0x000000001016e540 in spapr_rtas_call (cpu=0x3fffac590010, spapr=0x10fc6290, token=8215, 
    nargs=5, args=20547636, nret=1, rets=20547656)
    at qemu/hw/ppc/spapr_rtas.c:675
#9  0x0000000010167dfc in h_rtas (cpu=0x3fffac590010, spapr=0x10fc6290, opcode=61440, 
    args=0x3fffac570030) at qemu/hw/ppc/spapr_hcall.c:665
#10 0x00000000101693ec in spapr_hypercall (cpu=0x3fffac590010, opcode=61440, 
    args=0x3fffac570030) at qemu/hw/ppc/spapr_hcall.c:1094
#11 0x000000001026c82c in kvm_arch_handle_exit (cs=0x3fffac590010, run=0x3fffac570000)
    at qemu/target-ppc/kvm.c:1731
#12 0x00000000100a246c in kvm_cpu_exec (cpu=0x3fffac590010)
    at qemu/kvm-all.c:2005
#13 0x000000001007d8d4 in qemu_kvm_cpu_thread_fn (arg=0x3fffac590010) 

This happens because during CPU removal, though we park the kvm_fd
corresponding to the removed vCPU thread, we unmap the kvm_run (and
hence coalesced mmio ring).

What would be the best way to fix this ? Is disassociating coalesced_mmio_ring
from vCPU 0's kvm_run the correct solution ?

Regards,
Bharata.

             reply	other threads:[~2016-07-27  2:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  2:52 Bharata B Rao [this message]
2016-07-27  4:31 ` [Qemu-devel] Segfault with coalesced mmio and boot CPU removal Bharata B Rao
2016-07-27  4:46   ` David Gibson

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=20160727025251.GF7036@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=imammedo@redhat.com \
    --cc=qemu-devel@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).