Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: paawan oza <paawan1982@yahoo.com>
To: Hui Zhu <teawater@gmail.com>, Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: regarding recording of registers....
Date: Fri, 07 Aug 2009 08:39:00 -0000	[thread overview]
Message-ID: <768187.31536.qm@web112501.mail.gq1.yahoo.com> (raw)
In-Reply-To: <daef60380908041829p6fba6af6ga093e6440c9f979@mail.gmail.com>


Hi Hui & Michael,

There has been one thing I have been thinking. May be I will need your opinions.

there are many registers we save and sometimes we may not be 100% sure, for e.g. some staus registers like eflags, or any status, control, opcode registers whose change depedns purely on the current state of the syetem and more precisely current instruction's execution.

so how about implementing a cache mechinism (or it may be already there), which has a state of all registers all the time, and we record only those registers which are actauylly changed.as and wehn it is changed we update cache. this has intension to save record memory. of course this is only applicable when we are in record mode.

I would be looking forward to having some inputs whether this is a good idea to do !

Regards,
Oza.










      


  reply	other threads:[~2009-08-07  7:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 13:06 final i386.floating.record.patch paawan oza
2009-08-04 13:58 ` Hui Zhu
2009-08-04 14:18   ` paawan oza
2009-08-04 14:26   ` paawan oza
2009-08-04 14:43     ` Hui Zhu
2009-08-04 17:59       ` paawan oza
2009-08-05  1:29         ` Hui Zhu
2009-08-07  8:39           ` paawan oza [this message]
2009-08-05  1:34         ` Michael Snyder
2009-08-05 13:48           ` paawan oza

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=768187.31536.qm@web112501.mail.gq1.yahoo.com \
    --to=paawan1982@yahoo.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.com \
    /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