From: Michael Walle <michael@walle.cc>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] Re: [PATCH 02/17] lm32: translation routines
Date: Mon, 7 Feb 2011 23:55:11 +0100 [thread overview]
Message-ID: <201102072355.11839.michael@walle.cc> (raw)
In-Reply-To: <20110207222033.GD9697@laped.lan>
On Mon, Feb 07 2011, 23:20:33, Edgar E. Iglesias wrote:
> Yes, I found the nop tracking handy too but It exposes a way for guests
> to completely abort the vm with valid code. On microblaze, even guest
> userspace can trig the cpu_abort. Your port doesn't have an MMU so guest
> userland can probably kill the vm anyway, so it might be less of an issue.
>
> Maybe the event could be logged instead of cpu_abort:ed?
If the program jumps to uninitialized memory, it'll likely execute until the
end of the memory and then kill the VM.
Maybe we can add some kind of runtime configuration option for
enabling/disabling this?
--
Michael
next prev parent reply other threads:[~2011-02-07 22:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 0:30 [Qemu-devel] [PATCH 00/17] LatticeMico32 target Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 01/17] LatticeMico32 target support Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 02/17] lm32: translation routines Michael Walle
2011-02-07 18:41 ` [Qemu-devel] " Edgar E. Iglesias
2011-02-07 22:00 ` Michael Walle
2011-02-07 22:20 ` Edgar E. Iglesias
2011-02-07 22:55 ` Michael Walle [this message]
2011-02-07 23:01 ` Alexander Graf
2011-02-08 17:32 ` [Qemu-devel] " Richard Henderson
2011-02-08 20:00 ` Edgar E. Iglesias
2011-02-08 21:32 ` Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 03/17] lm32: translation code helper Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 04/17] lm32: machine state loading/saving Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 05/17] lm32: gdbstub support Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 06/17] lm32: interrupt controller model Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 07/17] lm32: juart model Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 08/17] lm32: pic and juart helper functions Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 09/17] lm32: timer model Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 10/17] lm32: uart model Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 11/17] lm32: system control model Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 12/17] lm32: support for creating device tree Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 13/17] lm32: EVR32 and uclinux BSP Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 14/17] lm32: todo and documentation Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 15/17] lm32: opcode testsuite Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 16/17] Add lm32 target to configure Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 17/17] MAINTAINERS: add LatticeMico32 maintainer Michael Walle
2011-02-07 16:28 ` [Qemu-devel] Re: [PATCH 00/17] LatticeMico32 target Alexander Graf
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=201102072355.11839.michael@walle.cc \
--to=michael@walle.cc \
--cc=agraf@suse.de \
--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).