[Gems-users] Separate User and OS Execution


Date: Mon, 25 Sep 2006 12:32:26 -0700 (PDT)
From: "Dave Z." <zhu_dave@xxxxxxxxx>
Subject: [Gems-users] Separate User and OS Execution
Hello,

I'm trying to separate user and OS execution, in other
words I'm trying to see how my benchmarks behave
isolated from the OS (e.g. state transitions only in
user mode, etc) . So, I'm trying to isolate the
program simulation as I don't want to get metrics
related with the OS. On my previous inquiry, Dan
recommended that I modify Ruby's commands.C
(operate_memory()). I couldn't find that function, the
closest I could find is observe_memory(). I did the
following change:

void
mh_memorytracer_observe_memory(memory_transaction_t
*mem_trans)
{
  // Pass this request off to
SimicsDriver::makeRequest()
  SimicsDriver* simics_interface_ptr =
static_cast<SimicsDriver*>(g_system_ptr->getDriver());
  mem_trans->priv = 1; // THIS IS WHAT I'VE ADDED
 
simics_interface_ptr->observeMemoryAccess(mem_trans);
}

As the priv bit is set, it should return from the
function instead of calling any other Ruby
functionality, right? But I still get the same results
including user accesses and supervisor accesses. Am I
missing something?

Thank you very much.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
[← Prev in Thread] Current Thread [Next in Thread→]
  • [Gems-users] Separate User and OS Execution, Dave Z. <=