From: Fabien Chouteau <chouteau@adacore.com>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Michael Eager <eager@eagerm.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] clk_setup decl missing in virtex_init
Date: Mon, 14 Nov 2011 09:52:05 +0100 [thread overview]
Message-ID: <4EC0D6B5.3010203@adacore.com> (raw)
In-Reply-To: <20111107230521.GC14307@zapo>
On 08/11/2011 00:05, Edgar E. Iglesias wrote:
> On Mon, Nov 07, 2011 at 02:46:47PM -0800, Michael Eager wrote:
>> The declaration of clk_setup is missing in
>> qemu/hw/virtex_ml507.c:
>>
>> static void virtex_init(ram_addr_t ram_size,
>> const char *boot_device,
>> const char *kernel_filename,
>> const char *kernel_cmdline,
>> const char *initrd_filename, const char *cpu_model)
>> {
>> ...
>> <no decl for clk_setup>
>> ...
>> memset(clk_setup, 0, sizeof(clk_setup));
>>
>> This SEGVs because clk_setup is an inline function defined in ppc.h.
>> (I presume that the linker generates an out-of-line copy.)
>>
>> It isn't clear what the declaration should be. In ppc405_uc.c, there
>> is a decl:
>> clk_setup_t clk_setup[PPC405EP_CLK_NB];
>
>
> Hi
>
> the following patch seems to work on my side. Fabien, could
> you please see if this was your intention? It seems to be
> commit ddd1055b07fdfe488a22c2275adaca75f4206d30 that
> introduced the segfault.
>
That's right the memset should have been removed in my patch.
Thanks,
--
Fabien Chouteau
prev parent reply other threads:[~2011-11-14 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 22:46 [Qemu-devel] clk_setup decl missing in virtex_init Michael Eager
2011-11-07 23:05 ` Edgar E. Iglesias
2011-11-07 23:25 ` Michael Eager
2011-11-08 21:01 ` Edgar E. Iglesias
2011-11-14 8:52 ` Fabien Chouteau [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=4EC0D6B5.3010203@adacore.com \
--to=chouteau@adacore.com \
--cc=eager@eagerm.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).