Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

host code #4

Open
ysreea opened this issue Nov 10, 2019 · 10 comments
Open

host code #4

ysreea opened this issue Nov 10, 2019 · 10 comments

Comments

@ysreea
Copy link

ysreea commented Nov 10, 2019

Hi,
When I tried to run the zsim code for host.cfg(./build/opt/zsim tests/host.cfg).It's not generating multiple traces for multiple cores. But pim.cfg seems like working fine though. Can someone please let me know what might be the possible thing I'm missing here.

@dchakra336
Copy link

dchakra336 commented Jan 6, 2020

Hi, I'm facing the same issue.
Setting the merge_hostTraces knob to either true or false raises an error.
Any updates?

@minititanxi
Copy link

I meet the same problem, and i did not find the way to solve it.

@maryam1364
Copy link

@dchakra336 : For host processing versus pim processing, you need to run Ramulator a little bit different. You can run Ramulator with split traces to be true or split traces to be false.
I did this for my runs and it works fine.

@dchakra336
Copy link

@maryam1364: That's great! How did you run it differently?

@maryam1364
Copy link

When there is one trace file, run ramulator without --split-trace option!

@geraldofojunior
Copy link
Collaborator

Hi, the host code is always generated into a single file to ensure that the DRAM memory requests are ordered following the application's memory access pattern when simulating the host configuration on Ramulator. Recall that host traces are filtered by L3 in zsim and are intended to be used to simulate only the memory device on Ramulator (without PIM cores). Therefore, there is no reason to split host traces per core id.

I would advise to not use split traces for host code. Also, I would advise to not run host traces on PIM mode in Ramulator.

@FanYang98
Copy link

Hi, the host code is always generated into a single file to ensure that the DRAM memory requests are ordered following the application's memory access pattern when simulating the host configuration on Ramulator. Recall that host traces are filtered by L3 in zsim and are intended to be used to simulate only the memory device on Ramulator (without PIM cores). Therefore, there is no reason to split host traces per core id.

I would advise to not use split traces for host code. Also, I would advise to not run host traces on PIM mode in Ramulator.

Hi,
if i follow your configuration on Ramulator,i can't get host.stats to compare with pim.stats . So how can i get the host.stats ?
Thanks!

@FanYang98
Copy link

@maryam1364 hi ,when i run ramulator without --split-trace option,i get a meaningless stats file. 😭 is there any problem ?

@maryam1364
Copy link

@XDUFanYang : For host run: it creates one ".out" file and when I want to run Ramulator, I make sure that split-traces option is false.
For PIM run: it creates 4 ".out" file. and when I run Ramulator, I makes sure that split-trace option is true.

I was working with ramulator-pim 6 months ago and these are the things I remember.

@FanYang98
Copy link

@XDUFanYang : For host run: it creates one ".out" file and when I want to run Ramulator, I make sure that split-traces option is false.
For PIM run: it creates 4 ".out" file. and when I run Ramulator, I makes sure that split-trace option is true.

I was working with ramulator-pim 6 months ago and these are the things I remember.

Thx, I got!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants