From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH qom v3 1/4] cpu: Add wrapper to the set-pc() hook
Date: Thu, 25 Jun 2015 18:21:30 +0200 [thread overview]
Message-ID: <558C2A8A.8070202@suse.de> (raw)
In-Reply-To: <CAFEAcA-mtBoZ5-8XRcGspvXt9RCuRp2yEumJj8EJVSSmK+8q0g@mail.gmail.com>
Am 25.06.2015 um 13:21 schrieb Peter Maydell:
> On 25 June 2015 at 12:12, Andreas Färber <afaerber@suse.de> wrote:
>> Am 24.06.2015 um 21:11 schrieb Peter Maydell:
>>> On 24 June 2015 at 19:09, Andreas Färber <afaerber@suse.de> wrote:
>>>> + g_assert(cc->set_pc != NULL);
>>>> + cc->set_pc(cpu, addr);
>>>> }
>>>
>>> Do we need this assert? If it would have fired
>>> then we'll just crash immediately calling the null pointer,
>>> so it's not like it's guarding against a more subtle failure
>>> at a later point...
>>
>> There seemed uncertainty whether all corner cases of the 17 targets
>> implement set_pc for all subclasses. By my reading, g_assert() calls
>> g_assertion_message_expr(), which is marked G_GNUC_NORETURN - and I
>> assume it to abort after printing the message, raising a signal and
>> either exiting the process or falling back to an attached debugger.
>>
>> It may be unnecessary, but I don't see it calling the null pointer here.
>
> What I mean is:
> * with the assert, QEMU will die in this function if cc->set_pc
> is NULL, in an easily debuggable way
> * without the assert, QEMU will still die in this function if
> cc->set_pc is NULL, in an easily debuggable way
>
> So the assert doesn't hurt, but it doesn't really gain anything IMHO.
> Assertions are most useful when they turn something that would be
> a really confusing failure much later in execution into an easily
> debuggable crash earlier on, I think.
>
> Still, this is a very minor thing, so it's a personal taste/style
> question, as you say. You can leave the assert in or remove it,
> whichever you prefer.
Okay, dropping the assertion:
diff --git a/include/qom/cpu.h b/include/qom/cpu.h
index e7ee6c6..5db1ea3 100644
--- a/include/qom/cpu.h
+++ b/include/qom/cpu.h
@@ -610,7 +610,6 @@ static inline void cpu_set_pc(CPUState *cpu, vaddr addr)
{
CPUClass *cc = CPU_GET_CLASS(cpu);
- g_assert(cc->set_pc != NULL);
cc->set_pc(cpu, addr);
}
Cheers,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-06-25 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 3:19 [Qemu-devel] [PATCH qom v3 0/4] qom-cpu: Wrap set_pc hook and use in bootloaders Peter Crosthwaite
2015-06-24 3:19 ` [Qemu-devel] [PATCH qom v3 1/4] cpu: Add wrapper to the set-pc() hook Peter Crosthwaite
2015-06-24 18:09 ` Andreas Färber
2015-06-24 19:11 ` Peter Maydell
2015-06-25 11:12 ` Andreas Färber
2015-06-25 11:21 ` Peter Maydell
2015-06-25 16:21 ` Andreas Färber [this message]
2015-06-24 3:19 ` [Qemu-devel] [PATCH qom v3 2/4] gdbstub: Use cpu_set_pc() helper Peter Crosthwaite
2015-06-24 3:19 ` [Qemu-devel] [PATCH qom v3 3/4] arm: boot: Use cpu_set_pc() Peter Crosthwaite
2015-06-24 18:22 ` Andreas Färber
2015-06-24 18:26 ` Peter Crosthwaite
2015-06-24 19:13 ` Peter Maydell
2015-06-24 3:19 ` [Qemu-devel] [PATCH qom v3 4/4] microblaze: " Peter Crosthwaite
2015-06-24 18:00 ` Andreas Färber
2015-06-24 18:29 ` Andreas Färber
2015-06-25 2:08 ` Peter Crosthwaite
2015-06-24 18:36 ` [Qemu-devel] [PATCH qom v3 0/4] qom-cpu: Wrap set_pc hook and use in bootloaders Andreas Färber
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=558C2A8A.8070202@suse.de \
--to=afaerber@suse.de \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.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 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.