| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <54D9F8DC.1070906@roeck-us.net> Date: Tue, 10 Feb 2015 04:26:04 -0800 From: Guenter Roeck <linux@...ck-us.net> To: "Edgar E. Iglesias" <edgar.iglesias@...il.com>, Jesper Nilsson <jesper.nilsson@...s.com> CC: Rabin Vincent <rabin@....in>, linux-kernel@...r.kernel.org, Jesper Nilsson <jespern@...s.com>, "viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>, linux-cris-kernel <linux-cris-kernel@...s.com> Subject: Re: [PATCH 3/3] CRISv32: handle multiple signals On 02/10/2015 03:04 AM, Edgar E. Iglesias wrote: > Hi, > > Sorry for top posting, on my phone. > > Qemu has support for the crisv10 CPU but lacks the v10 MMU setup. The MMU models are basically available as the v10 mmu is very similar to the v32 mmu IIRC. > > It's a matter of putting in the effort to wire everything up. The v10 setup interacts with the mmu via mmio while the v32 has special regs/insns for accessing the mmu. There might be other difficulties I haven't thought of though. > Too bad. And even if someone would spend the time it looks like it is becoming very difficult to get changes accepted to qemu nowadays. One step at a time ... I would be happy if we can get crisv32 to the point where I can run my automated qemu tests on it with unpatched kernels. Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists