qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: G Portokalidis <georgios.portokalidis@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Running code from IO memory
Date: Sat, 28 Jan 2006 01:14:03 +0100	[thread overview]
Message-ID: <ef735050601271614j553be737g@mail.gmail.com> (raw)

I've been hacking Qemu for Argos, and i was wondering whether it is
possible to execute code from a virtual peripherals memory.

To be more explicit, i have coded a virtual peripheral that does
nothing, but register some physical memory for memory io. This
physical address is mapped into a process's address space. I would
like to place code to be executed into that memory space.

Can qemu's JIT handle such cases?
I point eip to the corresponding virtual address, but everything crashes.

Anyone?

Cheers,
Giorgos

             reply	other threads:[~2006-01-28 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28  0:14 G Portokalidis [this message]
2006-01-29 10:25 ` [Qemu-devel] Running code from IO memory Paul Brook

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=ef735050601271614j553be737g@mail.gmail.com \
    --to=georgios.portokalidis@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).