verlap and it wasn't told to go ahead and
clobber those, so it has to give up.
Gabe
On Tue, Oct 26, 2021 at 5:13 PM Monsalve, Jose Manuel via gem5-users
mailto:gem5-users@gem5.org>> wrote:
Jason,
Thanks for the answer.
Let me take a look into this idea and I will get back to you.
o go ahead and
clobber those, so it has to give up.
Gabe
On Tue, Oct 26, 2021 at 5:13 PM Monsalve, Jose Manuel via gem5-users
mailto:gem5-users@gem5.org>> wrote:
Jason,
Thanks for the answer.
Let me take a look into this idea and I will get back to you.
Jose
From: Jason Lowe
; argument which will tell the mapping
function to overwrite existing mappings. You can see in the panic that that's
what it's checking, ie it found an overlap and it wasn't told to go ahead and
clobber those, so it has to give up.
Gabe
On Tue, Oct 26, 2021 at 5:13 PM Monsalve, Jose Manuel via
y what the underlying "problem" is. That said,
we may be able to solve it "correctly" by generally skipping the mapping during
the elf loading if it's already been manually mapped by the process.map
function. This may be useful to upstream if this idea works.
Cheers,
Jason
On Fri,
Hi everyone,
I am working on developing the simulation of a system that contains two
different regions of memory. One that maps to the cachable system memory
(including cache hierarchy) but another region that is non-cachable, and which
goes to a different memory (similar to scratchpad memory
