Re: [Gems-users] non-cacheable memory

[Mike Marty <mikem@xxxxxxxxxxx>]

If memory is non-cacheable, you certainly do not want to return
immediately from ruby_operate.

Choose a protocol that has silent S eviction, and add a request type to
ensure your cache doesn't get the block in M state (exclusive).  Ok, we've
covered loads.  Not sure how you want to handle Stores.

--mike


> Hi,
>
> I would like to treat certain memory locations as
> non-cacheable because I don't want to pollute the L1
> cache. So, I was wondering if there was a way to do
> this in Ruby. Perhaps I could return immediately from
> ruby_operate? What should be the returned value from
> ruby_operate? The number of cycles that Simics has to
> wait (the latency of the operation)?
>
> Thank you,
>
> Dave
>
>
>
> ____________________________________________________________________________________
> Expecting? Get great news right away with email Auto-Check.
> Try the Yahoo! Mail Beta.
> http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>