oooooohhh, wooooow.... ok, yea, I just misread the code then. That's *just* the default value. I knew something just wasn't right there in how I was looking at it.
The other issue I had was from the "write" value and confusing that with the mode derived from the system register in the translateData(). But, it looks like the "mode" variable is actually determining user/kernel mode while the "write" variable is determining read/write mode. So we're all good there in my opinion. Thanks for the clarification. On Thu, Apr 9, 2009 at 12:18 PM, nathan binkert <[email protected]> wrote: > > The file I'm referring to is arch/alpha/tlb.cc and specifically the > > translateAtomic() function implemented there. > > > > Basically, having the "Read" mode is irrelevant there since it's given a > > default type of "write" when it calls translateData(). Then in the > > translateData() function it goes ahead and gets the mode from a system > > register. > > > > So either I'm mixing up what "mode" means or that extra mode (at least > for > > translateAtomic()) is just extra there. > It's not given write. There's a check to see if the mode is write. > the code is "mode == Write" not "Write", so a true is passed in if > it's a write and a false if it's a read. > > Or is this not the issue? > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > -- ---------- Korey L Sewell Graduate Student - PhD Candidate Computer Science & Engineering University of Michigan
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
