From: Jan Kiszka <jan.kiszka@web.de>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Avi Kivity <avi@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] Memory API conversions, batch 5
Date: Thu, 25 Aug 2011 21:32:58 +0200 [thread overview]
Message-ID: <4E56A36A.4090806@web.de> (raw)
In-Reply-To: <20110825182739.GA21302@zapo>
[-- Attachment #1: Type: text/plain, Size: 2292 bytes --]
On 2011-08-25 20:27, Edgar E. Iglesias wrote:
> On Thu, Aug 25, 2011 at 08:04:34AM -0500, Anthony Liguori wrote:
>> On 08/25/2011 03:01 AM, Avi Kivity wrote:
>>> Please pull from
>>>
>>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/batch
>>>
>>> to receive the fifth memory API conversions batch. There is really
>>> nothing notable, except perhaps the first use of the transaction API.
>>>
>>> While the patches have been on the list for just a short time, they have
>>> received quite extensive review, for which I am thankful.
>>
>> Pulled. Thanks.
>
> Guys, please start testing before applying these patches. It's not hard,
> there are images on the wiki with scripts that area easy to run.
>
> Cheers
>
> $ gdb --args ~/src/c/qemu/build-qemu/microblaze-softmmu/qemu-system-microblaze -kernel linux.bin -serial stdio
> GNU gdb (Ubuntu/Linaro 7.3-0ubuntu1) 7.3-2011.08~bzr
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /home/edgar/src/c/qemu/build-qemu/microblaze-softmmu/qemu-system-microblaze...done.
> (gdb) run
> Starting program: /home/edgar/src/c/qemu/build-qemu/microblaze-softmmu/qemu-system-microblaze -kernel linux.bin -serial stdio
> [Thread debugging using libthread_db enabled]
> [New Thread 0x7fffeef3e700 (LWP 25891)]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000041be54 in memory_region_init_rom_device (mr=0xfb6900,
> ops=<optimized out>, dev=<optimized out>,
> name=0x564c5d "petalogix_s3adsp1800.flash", size=16777216)
> at /home/edgar/src/c/qemu/qemu/memory.c:973
> 973 mr->ram_addr |= cpu_register_io_memory(memory_region_read_thunk,
> (gdb)
That looks pretty much like what I stumbled over today as well. Should
be fine with [1], need to test again.
Jan
[1] http://thread.gmane.org/gmane.comp.emulators.qemu/114619
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-08-25 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 8:01 [Qemu-devel] [PULL] Memory API conversions, batch 5 Avi Kivity
2011-08-25 13:04 ` Anthony Liguori
2011-08-25 18:27 ` Edgar E. Iglesias
2011-08-25 18:58 ` Blue Swirl
2011-08-25 19:02 ` Anthony Liguori
2011-08-25 19:16 ` Blue Swirl
2011-08-31 6:30 ` Markus Armbruster
2011-08-25 19:17 ` Edgar E. Iglesias
2011-08-25 19:24 ` Avi Kivity
2011-08-25 19:32 ` Jan Kiszka [this message]
2011-08-25 19:36 ` Avi Kivity
2011-08-25 19:38 ` Jan Kiszka
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=4E56A36A.4090806@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.com \
--cc=edgar.iglesias@gmail.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).