From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Alistair Francis <alistai@xilinx.com>,
Sai Pavan Boddu <sai.pavan.boddu@xilinx.com>
Subject: Re: [Qemu-devel] [PULL v1 0/8] Xilinx queue
Date: Tue, 16 Jan 2018 21:49:57 +0700 [thread overview]
Message-ID: <20180116144957.GA5516@toto> (raw)
In-Reply-To: <CAFEAcA8v1pmDLD6xz_5yysqyV+aG3EiSF1j9ahYC9f2XatF80Q@mail.gmail.com>
On Tue, Jan 16, 2018 at 02:17:04PM +0000, Peter Maydell wrote:
> On 16 January 2018 at 11:50, Edgar E. Iglesias <edgar.iglesias@gmail.com> wrote:
> > From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
> >
> > The following changes since commit f521eeee3bd060b460c99e605472b7e03967db43:
> >
> > Merge remote-tracking branch 'remotes/juanquintela/tags/migration/20180115' into staging (2018-01-15 13:17:47 +0000)
> >
> > are available in the git repository at:
> >
> > git@github.com:edgarigl/qemu.git tags/edgar/xilinx-next-2018-01.for-upstream
> >
> > for you to fetch changes up to e451272ac191cd3ac408bc89ea63a401e84d4224:
> >
> > xlnx-zynqmp: Connect the IPI device to the ZynqMP SoC (2018-01-16 11:44:49 +0100)
> >
> > ----------------------------------------------------------------
> > Xilinx queue
> >
> > ----------------------------------------------------------------
> > Alistair Francis (8):
> > xlnx-zynqmp-pmu: Initial commit of the ZynqMP PMU
> > xlnx-zynqmp-pmu: Add the CPU and memory
> > aarch64-softmmu.mak: Use an ARM specific config
> > xlnx-pmu-iomod-intc: Add the PMU Interrupt controller
> > xlnx-zynqmp-pmu: Connect the PMU interrupt controller
> > xlnx-zynqmp-ipi: Initial version of the Xilinx IPI device
> > xlnx-zynqmp-pmu: Connect the IPI device to the PMU
> > xlnx-zynqmp: Connect the IPI device to the ZynqMP SoC
> >
>
> Hi -- this trips some new runtime sanitizer warnings:
Hi Peter,
This didn't show up on my clang testing, do you mind sharing configure line and clang version you use?
@Alistair, it does seem like the call to microblaze_load_kernel is passing wrong arguments.
Can you have a look?
Cheers,
Edgar
>
> GTESTER check-qtest-microblaze
> /home/petmay01/linaro/qemu-for-merges/vl.c:2279:16: runtime error:
> null pointer passed as argument 1, which is declared to never be null
> /usr/include/unistd.h:290:60: note: nonnull attribute specified here
> /home/petmay01/linaro/qemu-for-merges/vl.c:2279:16: runtime error:
> null pointer passed as argument 1, which is declared to never be null
> /usr/include/unistd.h:290:60: note: nonnull attribute specified here
> make: Leaving directory '/home/petmay01/linaro/qemu-for-merges/build/clang'
> make: Entering directory '/home/petmay01/linaro/qemu-for-merges/build/clang'
> GTESTER check-qtest-microblazeel
> /home/petmay01/linaro/qemu-for-merges/vl.c:2279:16: runtime error:
> null pointer passed as argument 1, which is declared to never be null
> /usr/include/unistd.h:290:60: note: nonnull attribute specified here
> /home/petmay01/linaro/qemu-for-merges/vl.c:2279:16: runtime error:
> null pointer passed as argument 1, which is declared to never be null
> /usr/include/unistd.h:290:60: note: nonnull attribute specified here
>
> This is because you've called qemu_find_file() with a NULL pointer
> (which it then passes to access(), which it isn't valid to call with
> a NULL pathname argument). Backtrace:
>
> #0 0x0000555555e446c1 in qemu_find_file (type=0, name=0x0)
> at /home/petmay01/linaro/qemu-for-merges/vl.c:2279
> #1 0x0000555555dfd693 in microblaze_load_kernel (cpu=0x55555824da28,
> ddr_base=<optimised out>, ramsize=0, initrd_filename=<optimised out>,
> dtb_filename=0x0, machine_cpu_reset=0x0)
> at /home/petmay01/linaro/qemu-for-merges/hw/microblaze/boot.c:128
> #2 0x0000555555dfd519 in xlnx_zynqmp_pmu_init (machine=<optimised out>)
> at /home/petmay01/linaro/qemu-for-merges/hw/microblaze/xlnx-zynqmp-pmu.c:190
> #3 0x0000555555f2fd5d in machine_run_board_init (machine=<optimised out>)
> at /home/petmay01/linaro/qemu-for-merges/hw/core/machine.c:792
> #4 0x0000555555e4a357 in main (argc=<optimised out>, argv=<optimised
> out>, envp=<optimised out>)
> at /home/petmay01/linaro/qemu-for-merges/vl.c:4622
>
> thanks
> -- PMM
next prev parent reply other threads:[~2018-01-16 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 11:50 [Qemu-devel] [PULL v1 0/8] Xilinx queue Edgar E. Iglesias
2018-01-16 11:51 ` [Qemu-devel] [PULL v1 1/8] xlnx-zynqmp-pmu: Initial commit of the ZynqMP PMU Edgar E. Iglesias
2018-01-16 11:51 ` [Qemu-devel] [PULL v1 2/8] xlnx-zynqmp-pmu: Add the CPU and memory Edgar E. Iglesias
2018-01-16 11:51 ` [Qemu-devel] [PULL v1 3/8] aarch64-softmmu.mak: Use an ARM specific config Edgar E. Iglesias
2018-01-16 11:51 ` [Qemu-devel] [PULL v1 4/8] xlnx-pmu-iomod-intc: Add the PMU Interrupt controller Edgar E. Iglesias
2018-01-16 11:51 ` [Qemu-devel] [PULL v1 6/8] xlnx-zynqmp-ipi: Initial version of the Xilinx IPI device Edgar E. Iglesias
2018-01-16 11:51 ` [Qemu-devel] [PULL v1 7/8] xlnx-zynqmp-pmu: Connect the IPI device to the PMU Edgar E. Iglesias
2018-01-16 14:17 ` [Qemu-devel] [PULL v1 0/8] Xilinx queue Peter Maydell
2018-01-16 14:49 ` Edgar E. Iglesias [this message]
2018-01-16 14:54 ` Peter Maydell
2018-01-16 22:45 ` Alistair Francis
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=20180116144957.GA5516@toto \
--to=edgar.iglesias@xilinx.com \
--cc=alistai@xilinx.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sai.pavan.boddu@xilinx.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.