Thank you for the response. It is really helpful.

On Thu, Apr 9, 2020 at 11:24 PM Ciro Santilli <ciro.santi...@gmail.com>
wrote:

> On Thu, Apr 9, 2020 at 6:29 PM Ajumal P A <ajupazhama...@gmail.com> wrote:
> >
> > Hi All,
> > I have a couple of doubts about how the event queue works and how stats
> are being calculated. Please help me with the following questions.
> > I have a loop which runs for 100 times, each iteration do an add
> operation and this loop is working on a single-core CPU system. I have
> wrapped that work as an event.
> > 1. I tried to schedule this event at the same cycle and the DPRINTF
> statements show that it's actually working at the same cycle, how and why?
>
> Not sure I understand, but one cycle can have multiple events. This
> can be seen clearly from logs as recommended below.
>
> > 2. What happens when I schedule above-mentioned event say at tick 100?
> Will the Gem5 calculates the curTick+TimeRequiredToCompleteThisEvent and
> log the stats? If not please let me know how to actually make the Gem5 take
> this time into consideration when it writes the stats?
>
> Maybe there's something I don't know, but I think all events are
> instantaneous. Everything that is not instantaneous is done by
> scheduling another event in the future.
>
> > 3. Is there any way to visually see the eventq? (I tried to look at this
> queue using GDB, but it's giving some address which I could not understand
> what it actually means)
> >
>
> --debug-flags Event,ExecAll gives good information. Not fully visual,
> but makes it possible to understand everything with a bit of staring.
> This may also help:
> https://cirosantilli.com/linux-kernel-module-cheat/#gem5-event-queue
>
> > Thanks in advance,
> > Aj.
> > _______________________________________________
> > gem5-users mailing list
> > gem5-users@gem5.org
> > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to