> Steve: Would you suggest that I do this in the BaseCache? Clock =
> Parent.clock? That would make the iocache use the system clock (which isn't
> necessarily a bad thing).
>
> Nate: The 2c is a tricky one. I have indeed got your patch, the issue is that
> it looks at the clock period at that v
On Fri, Sep 14, 2012 at 8:46 AM, Andreas Hansson wrote:
> Steve: Would you suggest that I do this in the BaseCache? Clock =
> Parent.clock? That would make the iocache use the system clock (which isn't
> necessarily a bad thing).
>
That sounds reasonable to me. It's overridable, so you could set
erred Python parameter resolution for CPU clock
On Fri, Sep 14, 2012 at 8:31 AM, nathan binkert wrote:
> > If ClockedObjects also had a list of children,
> > then we could traverse the tree of clocked objects any time a clock
> > period was changed and thus be able to deal wit
5.org] On Behalf Of
nathan binkert
Sent: 14 September 2012 16:31
To: gem5 Developer List
Subject: Re: [gem5-dev] Deferred Python parameter resolution for CPU clock
> The idea with Parent is that you would go into the icache and dcache, and
> in each of those say:
>
> self.clo
On Fri, Sep 14, 2012 at 8:31 AM, nathan binkert wrote:
> > If ClockedObjects also had a list of children,
> > then we could traverse the tree of clocked objects any time a clock
> > period was changed and thus be able to deal with DVFS (and the general
> > notion of clock domains) more easily.
> The idea with Parent is that you would go into the icache and dcache, and
> in each of those say:
>
> self.clock = Parent.clock
>
> which would set their clock parameters to a proxy object that will wait
> until instantiation, then search up the hierarchy for the nearest enclosing
> object's
The idea with Parent is that you would go into the icache and dcache, and
in each of those say:
self.clock = Parent.clock
which would set their clock parameters to a proxy object that will wait
until instantiation, then search up the hierarchy for the nearest enclosing
object's clock value.
Hi all,
Following the introduction of Cycles as a parameter type, it would be good to
get the cache latencies expressed in Cycles rather than absolute time (Ticks).
To get there, a first step is to ensure that the caches have an appropriate
clock period. My first stab at this was to change
Bas
