On Tue, Sep 11, 2012 at 11:36 AM, Addison Mayberry <[email protected]>wrote:
> Greetings, > I've observed that a cache request's kernel mode (reported via is_kernel) > does not always match up with the kernel mode reported by marss in the > Context object. I noticed this because I was tracing memory requests over > the course of system call and noticed that user-level requests were > appearing during the call. Is this intended behavior, and if so, could > anyone explain the exact meaning of what "is_kernel" indicates? > > Does these user level requests were generated as OP_READ or OP_WRITE? Sometimes there are requests generated as OP_UPDATE and OP_INVALIDATE due to older user level read/write. So can you check if these user level requests types. The 'is_kernel' is set when 'core' request a cache operation. When a cache read/write request generates cache eviction/writeback then new eviction/writeback request also keeps the same 'is_kernel' flag. - Avadh Thanks to anyone who can help. > Sincerely, > Addison > > ______________________________**_________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected].**edu <[email protected]> > https://www.cs.binghamton.edu/**mailman/listinfo/marss86-devel<https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel> >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
