From: Riku Voipio <riku.voipio@iki.fi>
To: edgar.iglesias@gmail.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/6] cris: Add a CRISv32 default "any" CPU for user mode emulation
Date: Mon, 3 Feb 2014 13:02:34 +0200 [thread overview]
Message-ID: <20140203110234.GB17799@afflict.kos.to> (raw)
In-Reply-To: <1391310292-18008-2-git-send-email-edgar.iglesias@gmail.com>
On Sun, Feb 02, 2014 at 03:04:47AM +0000, edgar.iglesias@gmail.com wrote:
> From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
This is not a regression, but my static busybox sample I have fails to
run with -cpu crisv32. -cpu crisv11 works a little better, but most
syscalls will blow up. Now it is entirely possible my cris busybox binary is
broken, as I have no hw to test it...
./cris-linux-user/qemu-cris -cpu crisv32 /home/voipio/linaro/qemu-smoke/cris/busybox echo hi
PC=80138 CCS=e8 btaken=1 btarget=80138
cc_op=8 cc_src=4 cc_dest=-150999004 cc_result=f6fff020 cc_mask=f
$r0=001dca60 $r1=00000000 $r2=00000000 $r3=00000000
$r4=00000000 $r5=00000000 $r6=00000000 $r7=00000000
$r8=00000000 $r9=0012dc50 $r10=000806a6 $r11=00000003
$r12=f6fff02c $r13=00001966 $sp=f6fff020 $acr=f6fff01c
special regs:
$bz=00000000 $vr=00000020 $pid=00000000 $srs=00000000
$wz=00000000 $exs=00000000 $eda=001dca60 $mof=00000000
$dz=00000000 $ebp=00000000 $erp=00000000 $srp=00000000
$nrp=00000000 $ccs=000000e8 $usp=00000000 $spc=00000000
support function regs bank 0:
s00=00000000 s01=00000000 s02=00000000 s03=00000000
s04=00000000 s05=00000000 s06=00000000 s07=00000000
s08=00000000 s09=00000000 s10=00000000 s11=00000000
s12=00000000 s13=00000000 s14=00000000 s15=00000000
> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
> target-cris/cpu.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/target-cris/cpu.c b/target-cris/cpu.c
> index 44301a4..21f1860 100644
> --- a/target-cris/cpu.c
> +++ b/target-cris/cpu.c
> @@ -239,7 +239,14 @@ static const TypeInfo cris_cpu_model_type_infos[] = {
> .name = TYPE("crisv32"),
> .parent = TYPE_CRIS_CPU,
> .class_init = crisv32_cpu_class_init,
> + },
> +#if defined(CONFIG_USER_ONLY)
> + {
> + .name = TYPE("any"),
> + .parent = TYPE_CRIS_CPU,
> + .class_init = crisv32_cpu_class_init,
> }
> +#endif
> };
>
> #undef TYPE
> --
> 1.8.3.2
>
next prev parent reply other threads:[~2014-02-03 11:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 3:04 [Qemu-devel] [PATCH 0/6] CRIS queue edgar.iglesias
2014-02-02 3:04 ` [Qemu-devel] [PATCH 1/6] cris: Add a CRISv32 default "any" CPU for user mode emulation edgar.iglesias
2014-02-03 11:02 ` Riku Voipio [this message]
2014-02-03 12:12 ` Edgar E. Iglesias
2014-02-03 11:44 ` Andreas Färber
2014-02-03 13:22 ` Edgar E. Iglesias
2014-02-02 3:04 ` [Qemu-devel] [PATCH 2/6] cris: Abort when a v10 takes interrupts while in a delayslot edgar.iglesias
2014-02-02 3:04 ` [Qemu-devel] [PATCH 3/6] cris: Add interrupt signals to the CPU device edgar.iglesias
2014-02-02 23:54 ` Peter Crosthwaite
2014-02-02 3:04 ` [Qemu-devel] [PATCH 4/6] axis-dev88: Connect the PIC upstream IRQs directly to the CPU edgar.iglesias
2014-02-02 23:54 ` Peter Crosthwaite
2014-02-02 3:04 ` [Qemu-devel] [PATCH 5/6] cris: Remove the CRIS PIC glue edgar.iglesias
2014-02-02 23:54 ` Peter Crosthwaite
2014-02-02 3:04 ` [Qemu-devel] [PATCH 6/6] linux-user: Fix trampoline code for CRIS edgar.iglesias
2014-02-03 10:49 ` Riku Voipio
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=20140203110234.GB17799@afflict.kos.to \
--to=riku.voipio@iki.fi \
--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).