qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.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 19:20:57 +0300	[thread overview]
Message-ID: <4E440169.8030403@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1108111807260.27291@bbs.intern>

On 08/11/2011 07:08 PM, Gerhard Wiesinger wrote:
>
> (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}

Yikes, this looks like corruption, it the leading 0x2000 in 
address_space is out of place.

Can you step through lsi pci bar registration and place a data 
breakpoint on address_space, and see where it gets this value?

'addr' looks bad too.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-08-11 16:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11  7:40 [Qemu-devel] [PATCH 0/2] Fix wide ioport access cracking Avi Kivity
2011-08-11  7:40 ` [Qemu-devel] [PATCH 1/2] memory: abstract cracking of write access ops into a function Avi Kivity
2011-08-11  7:40 ` [Qemu-devel] [PATCH 2/2] memory: crack wide ioport accesses into smaller ones when needed Avi Kivity
2011-08-11  8:25 ` [Qemu-devel] [PATCH 0/2] Fix wide ioport access cracking Gerhard Wiesinger
2011-08-11  8:27   ` Avi Kivity
2011-08-11  8:29     ` Avi Kivity
2011-08-11  9:01       ` Gerhard Wiesinger
2011-08-11  9:44         ` Avi Kivity
2011-08-11 16:08           ` Gerhard Wiesinger
2011-08-11 16:20             ` Avi Kivity [this message]
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=4E440169.8030403@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lists@wiesinger.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).