From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: IOCTL_PRIVCMD_MMAPBATCH on Xen 4.13.0
Date: Fri, 15 May 2020 23:06:29 +0200 [thread overview]
Message-ID: <20200515210629.GA10976@antioche.eu.org> (raw)
In-Reply-To: <d623cd12-4024-82ba-7388-21f606e1a0bd@citrix.com>
On Fri, May 15, 2020 at 10:00:07PM +0100, Andrew Cooper wrote:
> What is qemu doing at the time? Is it by any chance trying to map the
> IOREQ server frame?
Here's what gdb says about it:
Core was generated by `qemu-dm'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000000000046997d in cpu_x86_init (
cpu_model=cpu_model@entry=0x4d622d "qemu32")
at /home/bouyer/pkgbuild/current/sysutils/xentools413/work/xen-4.13.0/tools/qemu-xen-traditional/i386-dm/helper2.c:156
156 rc = xenevtchn_bind_interdomain(
--Type <RET> for more, q to quit, c to continue without paging--
[Current thread is 1 (process 1480)]
(gdb) where
#0 0x000000000046997d in cpu_x86_init (
cpu_model=cpu_model@entry=0x4d622d "qemu32")
at /home/bouyer/pkgbuild/current/sysutils/xentools413/work/xen-4.13.0/tools/qemu-xen-traditional/i386-dm/helper2.c:156
#1 0x000000000043628d in pc_init1 (ram_size=<optimized out>,
vga_ram_size=4194304, boot_device=0x7f7fff460397 "cda", pci_enabled=1,
cpu_model=0x4d622d "qemu32", initrd_filename=<optimized out>,
kernel_cmdline=<optimized out>, kernel_filename=<optimized out>)
at /home/bouyer/pkgbuild/current/sysutils/xentools413/work/xen-4.13.0/tools/qemu-xen-traditional/hw/pc.c:829
#2 0x00000000004636e7 in xen_init_fv (ram_size=0, vga_ram_size=4194304,
boot_device=0x7f7fff460397 "cda", kernel_filename=0x0,
kernel_cmdline=0x4abff6 "", initrd_filename=0x0, cpu_model=0x0,
direct_pci=0x0)
at /home/bouyer/pkgbuild/current/sysutils/xentools413/work/xen-4.13.0/tools/qemu-xen-traditional/hw/xen_machine_fv.c:405
#3 0x00000000004a975b in main (argc=23, argv=0x7f7fff45fc78,
envp=<optimized out>)
at /home/bouyer/pkgbuild/current/sysutils/xentools413/work/xen-4.13.0/tools/qemu-xen-traditional/vl.c:6014
Does it help ?
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
next prev parent reply other threads:[~2020-05-15 21:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 20:29 IOCTL_PRIVCMD_MMAPBATCH on Xen 4.13.0 Manuel Bouyer
2020-05-15 21:00 ` Andrew Cooper
2020-05-15 21:06 ` Manuel Bouyer [this message]
2020-05-15 21:38 ` Andrew Cooper
2020-05-15 21:53 ` Manuel Bouyer
2020-05-16 16:18 ` Andrew Cooper
2020-05-17 9:30 ` Manuel Bouyer
2020-05-17 17:32 ` Manuel Bouyer
2020-05-17 17:56 ` Manuel Bouyer
2020-05-18 7:36 ` Paul Durrant
2020-05-18 17:31 ` Manuel Bouyer
2020-05-19 7:34 ` Jan Beulich
2020-05-19 8:46 ` Manuel Bouyer
2020-05-19 8:51 ` Jan Beulich
2020-05-19 9:54 ` Roger Pau Monné
2020-05-19 10:28 ` Manuel Bouyer
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=20200515210629.GA10976@antioche.eu.org \
--to=bouyer@antioche.eu.org \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.