mem: Allow non-invalidating uncacheable snoops
Review Request #3767 - Created Dec. 19, 2016 and updated
| Information | |
|---|---|
| Eric Clark | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 11766:3a8eb6336012
---------------------------
mem: Allow non-invalidating uncacheable snoopsThis is a follow up to changeset 11285. Uncacheable snoops do
not invalidate so this panics if we are responding to an uncacheable
write snoop.This panic happens under ARM Linux 4.3. It affects myself and at
least one other user:https://www.mail-archive.com/gem5-users@gem5.org/msg13105.html
Ran {ARM,X86} debug/quick/se regressions but I don't have the spec binaries. Used with ARM full system simulation to complete my course project.
Thanks for this patch Eric. Can you elaborate a bit more on the case that fails?
I was under the impression that the current conditions that trigger this panic cannot be satisfied by cacheable requests. The panic here https://www.mail-archive.com/gem5-users@gem5.org/msg13105.html seems to be due to a WriteReq which in the form of a snoop can only be seen as an uncacheable request if I am not mistaken.