From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>, qemu-trivial@nongnu.org
Cc: qemu-devel@nongnu.org, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH] target-tricore: check return value before using it
Date: Thu, 30 Oct 2014 08:14:29 +0000 [thread overview]
Message-ID: <5451F365.5040506@mail.uni-paderborn.de> (raw)
In-Reply-To: <1414634608-31292-1-git-send-email-zhang.zhanghailiang@huawei.com>
Geez, thanks. I wonder how I missed that.
Reviewed-by: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
On 10/30/2014 02:03 AM, zhanghailiang wrote:
> We reference the return value of cpu before checking whether it is NULL,
> The checking code is after that which violates code style.
>
> It makes no difference if the cpu is NULL, qemu process will terminate.
> But one will be 'Segmentation fault' and the other will report a error
> which is what we want.
>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> ---
> hw/tricore/tricore_testboard.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/tricore/tricore_testboard.c b/hw/tricore/tricore_testboard.c
> index eeb4922..a059a20 100644
> --- a/hw/tricore/tricore_testboard.c
> +++ b/hw/tricore/tricore_testboard.c
> @@ -71,11 +71,11 @@ static void tricore_testboard_init(MachineState *machine, int board_id)
> machine->cpu_model = "tc1796";
> }
> cpu = cpu_tricore_init(machine->cpu_model);
> - env = &cpu->env;
> if (!cpu) {
> error_report("Unable to find CPU definition");
> exit(1);
> }
> + env = &cpu->env;
> memory_region_init_ram(ext_cram, NULL, "powerlink_ext_c.ram", 2*1024*1024, &error_abort);
> vmstate_register_ram_global(ext_cram);
> memory_region_init_ram(ext_dram, NULL, "powerlink_ext_d.ram", 4*1024*1024, &error_abort);
prev parent reply other threads:[~2014-10-30 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 2:03 [Qemu-devel] [PATCH] target-tricore: check return value before using it zhanghailiang
2014-10-30 6:59 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-10-30 8:14 ` Bastian Koppelmann [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=5451F365.5040506@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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 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).