From: Igor Mammedov <imammedo@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
Eric Auger <eric.auger@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] arm: isolate and clean up dtb generation
Date: Mon, 7 May 2018 09:51:26 +0200 [thread overview]
Message-ID: <20180507095126.2fd146b7@redhat.com> (raw)
In-Reply-To: <CAFEAcA-6nkVOEBc59H0mcgnRy9ifPRoRjUrvJ_4Gcr94GdjuSQ@mail.gmail.com>
On Fri, 4 May 2018 17:28:55 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 3 May 2018 at 16:03, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 1 May 2018 at 13:08, Igor Mammedov <imammedo@redhat.com> wrote:
> >>
> >> Changelog v2->v3:
> >> * drop already merged patches
> >> 'arm: always start from first_cpu when registering loader cpu reset callback'
> >> 'ppc: e500: switch E500 based machines to full machine definition'
> >> * add small not related cleanup
> >> 'arm: boot: set boot_info starting from first_cpu'
> >> * add extra suggested patch
> >> 'make sure that we aren't overwriting mc->get_hotplug_handler by accident'
> >> * make sure that dtb_limit initialized to 0
> >> * drop stale comment
> >> * drop not needed line movement
> >> * drop not needed extra new line
> >> Changelog v1->v2:
> >> * drop "arm: reuse arm_boot_address_space() in armv7m_load_kernel()"
> >> * move "arm: always start from first_cpu when registering loader cpu reset callback"
> >> at the begigning of series and rebase
> >> * add "ppc: e500: switch E500 based machines to full machine definition"
> >> and rebase 4/5 on top of it
> >> * fixup typo in virt_machine_get_hotpug_handler() name
> >> * add doc comment to skip_dtb_autoload field
> >> * 1-2/5 are queued in respective arm/ppc trees and are included for series
> >> completness so it would be easier to test, I expect series to go through
> >> arm tree
> >>
> >
> > Applied to target-arm.next, thanks.
>
> Doing further testing within target-arm.next shows that this series (and
> specifically patch 3/5) causes segfaults for the "no DTB provided" case.
>
> $ gdb --args ./build/x86/arm-softmmu/qemu-system-arm -M vexpress-a15
[...]
> arm_load_dtb() is trying to call the binfo->get_dtb() hook and is not
> handling the case where it is NULL (which it is on pretty much every
> board except "virt").
>
> (You get a segfault with an actual guest kernel as well; I just used
> /dev/null here as an easy no-dependencies-required repro case.)
>
> I've left patch 4 in target-arm.next as that was a standalone bugfix,
> but have dropped the rest of the series for now.
Fix is really trivial, I've lost have_dtb() guard, while consolidating
multiple load_dtb() calls into one.
I'll respin v4 shortly with fixed 3/5.
> thanks
> -- PMM
prev parent reply other threads:[~2018-05-07 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 12:08 [Qemu-devel] [PATCH v3 0/5] arm: isolate and clean up dtb generation Igor Mammedov
2018-05-01 12:08 ` [Qemu-devel] [PATCH v3 1/5] pc: simplify MachineClass::get_hotplug_handler handling Igor Mammedov
2018-05-01 12:08 ` [Qemu-devel] [PATCH v3 2/5] platform-bus-device: use device plug callback instead of machine_done notifier Igor Mammedov
2018-05-02 1:39 ` David Gibson
2018-05-01 12:08 ` [Qemu-devel] [PATCH v3 3/5] arm/boot: split load_dtb() from arm_load_kernel() Igor Mammedov
2018-05-01 12:08 ` [Qemu-devel] [PATCH v3 4/5] arm: boot: set boot_info starting from first_cpu Igor Mammedov
2018-05-01 12:19 ` Peter Maydell
2018-05-01 13:34 ` Igor Mammedov
2018-05-01 13:44 ` [Qemu-devel] [PATCH v4 " Igor Mammedov
2018-05-03 15:03 ` Peter Maydell
2018-05-04 8:05 ` Igor Mammedov
2018-05-01 12:08 ` [Qemu-devel] [PATCH v3 5/5] make sure that we aren't overwriting mc->get_hotplug_handler by accident Igor Mammedov
2018-05-02 0:45 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-05-03 15:03 ` [Qemu-devel] [PATCH v3 0/5] arm: isolate and clean up dtb generation Peter Maydell
2018-05-04 16:28 ` Peter Maydell
2018-05-07 7:51 ` Igor Mammedov [this message]
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=20180507095126.2fd146b7@redhat.com \
--to=imammedo@redhat.com \
--cc=eric.auger@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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;
as well as URLs for NNTP newsgroup(s).