qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Shashidhar Mysore" <shashimc@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Minos-type integrity checking in QEMU
Date: Wed, 25 Apr 2007 01:16:27 -0700	[thread overview]
Message-ID: <12835c8f0704250116i15a82885j7f6311715ad4374b@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

Hi,

I am trying to incorporate into QEMU (x86) some structures to maintain
integrity of data that flows in the processor. Specifically, I want to
maintain a bit for every physical memory address and transfer the state
information for every address along onto the virtual memory, and also down
to the instructions which operate on data, and bit arrays for registers (so
that when an operand is fetched from a particular register, we also have the
state information for that register). I am trying to build a Minos type
architecture ( http://minos.cs.ucdavis.edu/) but in QEMU instead of Bochs.

For this, as far as I can see, I need to maintain a set of new structures to
shadow the physical memory and make changes to the micro ops defined in
target-i386/op.c so that every instruction can track the state and store
them for every register used as an operand. I'm not sure if somebody has
already implemented such a system on QEMU? I am just beginning to think and
work on this, so any pointers/suggestions would be greatly appreciated.
Please let me know your views on this.

Thanks,
-Shashi.

[-- Attachment #2: Type: text/html, Size: 1241 bytes --]

             reply	other threads:[~2007-04-25  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25  8:16 Shashidhar Mysore [this message]
2007-04-25 11:06 ` [Qemu-devel] Minos-type integrity checking in QEMU maestro
2007-04-26  8:40   ` Shashidhar Mysore

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=12835c8f0704250116i15a82885j7f6311715ad4374b@mail.gmail.com \
    --to=shashimc@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).