From: Gerhard Wiesinger <lists@wiesinger.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix wide ioport access cracking
Date: Thu, 11 Aug 2011 18:08:18 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1108111807260.27291@bbs.intern> (raw)
In-Reply-To: <4E43A482.5040401@redhat.com>
On Thu, 11 Aug 2011, Avi Kivity wrote:
> On 08/11/2011 12:01 PM, Gerhard Wiesinger wrote:
>> Hello Avi,
>>
>> #0 0x0000003a060328f5 in raise () from /lib64/libc.so.6
>> #1 0x0000003a060340d5 in abort () from /lib64/libc.so.6
>> #2 0x0000003a0602b8b5 in __assert_fail () from /lib64/libc.so.6
>> #3 0x0000000000435339 in memory_region_del_subregion (mr=<value optimized
>> out>, subregion=<value optimized out>) at
>> /root/download/qemu/git/qemu-kvm-test/memory.c:1168
>> #4 0x000000000041eb9b in pci_update_mappings (d=0x1a90bc0) at
>> /root/download/qemu/git/qemu-kvm-test/hw/pci.c:1134
>> #5 0x0000000000420a9c in pci_default_write_config (d=0x1a90bc0, addr=4,
>> val=<value optimized out>, l=<value optimized out>) at
>> /root/download/qemu/git/qemu-kvm-test/hw/pci.c:1213
>> #6 0x00000000004329a6 in kvm_handle_io (env=0x1931af0) at
>> /root/download/qemu/git/qemu-kvm-test/kvm-all.c:858
>> #7 kvm_cpu_exec (env=0x1931af0) at
>> /root/download/qemu/git/qemu-kvm-test/kvm-all.c:997
>> #8 0x000000000040bd4a in qemu_kvm_cpu_thread_fn (arg=0x1931af0) at
>> /root/download/qemu/git/qemu-kvm-test/cpus.c:806
>> #9 0x0000003a06807761 in start_thread () from /lib64/libpthread.so.0
>> #10 0x0000003a060e098d in clone () from /lib64/libc.so.6
>>
>
> In frame 4, can you print out i, *r, and d->io_regions[0 through 6]? Some of
> them may be optimized out unfortunately.
See below.
Ciao,
Gerhard
(gdb) frame 4
#4 0x000000000041eb9b in pci_update_mappings (d=0x1a90bc0)
at /root/download/qemu/git/qemu-kvm-test/hw/pci.c:1134
1134 memory_region_del_subregion(r->address_space,
r->memory);
(gdb) print i
$1 = <value optimized out>
(gdb) print *r
$2 = {addr = 22058952032257, size = 32, filtered_size =
171717340864446496,
type = 1 '\001', memory = 0x1a90000, address_space = 0x200019282f0}
(gdb) print d->io_regions[0]
$3 = {addr = 22058952032257, size = 32, filtered_size =
171717340864446496,
type = 1 '\001', memory = 0x1a90000, address_space = 0x200019282f0}
(gdb) print d->io_regions[1]
$4 = {addr = 17113088, size = 32, filtered_size = 32, type = 0 '\000',
memory = 0x1a911c8, address_space = 0x1920000}
(gdb) print d->io_regions[2]
$5 = {addr = 0, size = 0, filtered_size = 0, type = 0 '\000', memory =
0x0,
address_space = 0x0}
(gdb) print d->io_regions[3]
$6 = {addr = 0, size = 0, filtered_size = 0, type = 239 '\357', memory =
0x0,
address_space = 0x0}
(gdb) print d->io_regions[4]
$7 = {addr = 0, size = 0, filtered_size = 0, type = 0 '\000', memory =
0x0,
address_space = 0x0}
(gdb) print d->io_regions[5]
$8 = {addr = 0, size = 0, filtered_size = 0, type = 0 '\000', memory =
0x0,
address_space = 0x0}
(gdb) print d->io_regions[6]
$9 = {addr = 0, size = 0, filtered_size = 0, type = 0 '\000', memory =
0x0,
address_space = 0x0}
--
http://www.wiesinger.com/
next prev parent reply other threads:[~2011-08-11 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 7:40 [PATCH 0/2] Fix wide ioport access cracking Avi Kivity
2011-08-11 7:40 ` [PATCH 1/2] memory: abstract cracking of write access ops into a function Avi Kivity
2011-08-11 7:40 ` [PATCH 2/2] memory: crack wide ioport accesses into smaller ones when needed Avi Kivity
2011-08-11 8:25 ` [PATCH 0/2] Fix wide ioport access cracking Gerhard Wiesinger
2011-08-11 8:27 ` Avi Kivity
2011-08-11 8:29 ` [Qemu-devel] " Avi Kivity
2011-08-11 9:01 ` Gerhard Wiesinger
2011-08-11 9:44 ` [Qemu-devel] " Avi Kivity
2011-08-11 16:08 ` Gerhard Wiesinger [this message]
2011-08-11 16:20 ` Avi Kivity
2011-08-11 16:22 ` Avi Kivity
2011-08-11 19:01 ` Gerhard Wiesinger
2011-08-22 10:46 ` Avi Kivity
2011-08-11 16:11 ` Gerhard Wiesinger
2011-08-11 16:15 ` Avi Kivity
2011-08-22 14:42 ` Anthony Liguori
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=alpine.LFD.2.02.1108111807260.27291@bbs.intern \
--to=lists@wiesinger.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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