qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] sh7750: Fix crash when accessing PVR/PRR/CVR
Date: Tue, 26 Mar 2013 14:44:42 +0000	[thread overview]
Message-ID: <CAFEAcA8JNqqyLoYN7=B75U_J5ccnKAPgPqPF_a=_zMLtoWWncg@mail.gmail.com> (raw)
In-Reply-To: <5151B249.6050602@suse.de>

On 26 March 2013 14:35, Andreas Färber <afaerber@suse.de> wrote:
> Am 26.03.2013 13:20, schrieb Peter Maydell:
>> Commit b350ab75 causes segfaults on accesses to PVR/PRR/CVR because
>> it tries to call SUPERH_CPU_GET_CLASS() on a pointer that isn't a
>> QOM object. Fix this by getting the actual QOM CPU object first.
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> Tested with the r2d image/instructions from
>> https://oss.renesas.com/modules/document/?Getting%20Started%20with%20SH4%20and%20QEMU
>
> Oops, reproduces with the test image from the QEMU Wiki as well. Seems
> to be a result of cherry-picking this commit before the full SH7750
> QOM'ification.
>
> Is this blocking any work of yours? Otherwise I would try rebasing my
> SH7750 patches so that s->cpu becomes a SuperHCPU as expected here.
> (Not sure if simply reverting my offending patch still works?)

Well, I have a workaround so it doesn't affect me now :-)
I wasn't really doing anything much with the sh4 board, I was just
looking at whether we could get rid of its use of taddr properties.
(Oddly it uses qdev_prop_set_taddr() to set a property which isn't
defined as a TADDR property, but this works anyway...)

-- PMM

  reply	other threads:[~2013-03-26 14:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 12:20 [Qemu-devel] [PATCH] sh7750: Fix crash when accessing PVR/PRR/CVR Peter Maydell
2013-03-26 14:35 ` Andreas Färber
2013-03-26 14:44   ` Peter Maydell [this message]
2013-04-08 12:52   ` Peter Maydell
2013-04-09 14:52     ` 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='CAFEAcA8JNqqyLoYN7=B75U_J5ccnKAPgPqPF_a=_zMLtoWWncg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=patches@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 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).