qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] isapc: Fix segfault during initialization
Date: Sun, 15 Jan 2012 08:38:28 -0600	[thread overview]
Message-ID: <4F12E4E4.8030001@codemonkey.ws> (raw)
In-Reply-To: <4F117F49.1090208@web.de>

[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]

On 01/14/2012 07:12 AM, Jan Kiszka wrote:
> From: Jan Kiszka<jan.kiszka@siemens.com>
>
> Linking the RTC device state to the PIIX does not belong into the
> common path that is shared with the isapc. QEMU crashes otherwise.
>
> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>

Does isapc actually work for you?  I tried to write a qemu-test test case 
(attached below) to help prevent future regressions.  I can reproduce your SEGV 
but with your patch applied, I get no output (not even the BIOS runs).

Here's the command line.  Even a simple 'qemu-system-x86_64 -M isapc' reproduces it:

/home/anthony/build/qemu/x86_64-softmmu/qemu-system-x86_64 -kernel 
bin/vmlinuz-3.0 -initrd .tmp-3510/initramfs-3510.img.gz -append console=ttyS0 
seed=24689 -M isapc -pidfile .tmp-3510/pidfile-3510.pid -qmp 
unix:.tmp-3510/qmpsock-3510.sock,server,nowait

Regards,

Anthony Liguori


> ---
>   hw/pc_piix.c |   22 +++++++++++-----------
>   1 files changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/hw/pc_piix.c b/hw/pc_piix.c
> index b70431f..3aea3cc 100644
> --- a/hw/pc_piix.c
> +++ b/hw/pc_piix.c
> @@ -201,6 +201,17 @@ static void pc_init1(MemoryRegion *system_memory,
>           }
>           idebus[0] = qdev_get_child_bus(&dev->qdev, "ide.0");
>           idebus[1] = qdev_get_child_bus(&dev->qdev, "ide.1");
> +
> +        /* FIXME there's some major spaghetti here.  Somehow we create the
> +         * devices on the PIIX before we actually create it.  We create the
> +         * PIIX3 deep in the recess of the i440fx creation too and then lose
> +         * the DeviceState.
> +         *
> +         * For now, let's "fix" this by making judicious use of paths.  This
> +         * is not generally the right way to do this.
> +         */
> +        qdev_property_add_child(qdev_resolve_path("/i440fx/piix3", NULL),
> +                                "rtc", (DeviceState *)rtc_state, NULL);
>       } else {
>           for(i = 0; i<  MAX_IDE_BUS; i++) {
>               ISADevice *dev;
> @@ -211,17 +222,6 @@ static void pc_init1(MemoryRegion *system_memory,
>           }
>       }
>
> -    /* FIXME there's some major spaghetti here.  Somehow we create the devices
> -     * on the PIIX before we actually create it.  We create the PIIX3 deep in
> -     * the recess of the i440fx creation too and then lose the DeviceState.
> -     *
> -     * For now, let's "fix" this by making judicious use of paths.  This is not
> -     * generally the right way to do this.
> -     */
> -
> -    qdev_property_add_child(qdev_resolve_path("/i440fx/piix3", NULL),
> -                            "rtc", (DeviceState *)rtc_state, NULL);
> -
>       audio_init(isa_bus, pci_enabled ? pci_bus : NULL);
>
>       pc_cmos_init(below_4g_mem_size, above_4g_mem_size, boot_device,


[-- Attachment #2: isapc.sh --]
[-- Type: application/x-shellscript, Size: 124 bytes --]

  parent reply	other threads:[~2012-01-15 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-14 13:12 [Qemu-devel] [PATCH] isapc: Fix segfault during initialization Jan Kiszka
2012-01-14 14:37 ` Andreas Färber
2012-01-15 14:38 ` Anthony Liguori [this message]
2012-01-15 14:40   ` Jan Kiszka
2012-01-15 16:12     ` Anthony Liguori
2012-01-15 16:16       ` Jan Kiszka
2012-01-15 16:20         ` 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=4F12E4E4.8030001@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jan.kiszka@web.de \
    --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).