For the first question,
Access()'s memcpy is for WriteBXK data, these are data evicted from higher 
level caches.
HandleFill()'s memcpy is for ReadReq(or ReadExReq) data, these data are from 
lower level caches (or memory).

For the second question,
I don't quite understand what you mean by "write data to cache" ... 
conventional caches are not changed the content of its storage. It can only 
store these data.

-----邮件原件-----
发件人: [email protected] [mailto:[email protected]] 代表 Oka 
Keitarou
发送时间: 2010年12月3日星期五 20:10
收件人: [email protected]
主题: Re: [m5-users] How to get write block data

Thank you for reply.

I looked at access() and handleFill() in cache_impl.hh,and I had two 
quetions.

Fisrt,I didn't understand difference between access() and handleFill().
Shoud I have to insert "DPRINTF" both of access() and handleFill()?

Second,how can I pick out write data to only L2cache?
I think these functions include write to both of L1cache and L2cache.

Thanks
oka
---------------------------------------------------------------------

zhanglunkai
Thu, 02 Dec 2010 23:50:35 -0800

Look at access() and handleFill() functions in cache_impl.hh.

Both of these two functions use memcpy to write data to L2 cache.

-----邮件原件-----
发件人: [email protected] [mailto:[email protected]] 代表
Oka Keitarou
发送时间: 2010年12月3日星期五 12:03
收件人: [email protected]
主题: [m5-users] How to get write block data to L2 cache

Hi,

I'd like to get the information of write block data to L2 cache.

I found in srm/mem/cache/cache_impl.hh that "pkt->getPtr<uint8_t>" is
pointer to data.
so I want to add like following code.
DPRINTF(Cache,"L2blkdata%x",*(pkt->getPtr<uint8_t>()))
However I can't find where pkt is written to L2 cache.
Could you tell me how can I get block data to L2 cache?

thanks
oka

_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

Reply via email to