I don't know... that's basically a page fault.  Do you know the address
range that your file is mapped to?  It may or may not be directly related
to mmap.

Steve

On Fri, Oct 31, 2014 at 6:33 AM, Ahmad Hassan <ahmad.has...@gmail.com>
wrote:

> Hi Steve,
>
> I am running x96 SE mode. The writeBlob() works fine for very small test
> application. For real benchmark with 1GB working set, the simulation ends
> with exception:
>
> panic: Tried to read unmapped address
> 0x2800000002d773b0.
> 0x2aaaaaaab000ULL
>  @ tick 771687885000
> [invoke:build/X86/arch/x86/faults.cc, line 160]
> Memory Usage: 11788528 KBytes
> Program aborted at tick 771687885000
>
> Any ideas why 0x2800 range is getting problems by writeBlob?
>
> Thanks.
>
>
>
> On 7 October 2014 15:20, Steve Reinhardt <ste...@gmail.com> wrote:
>
>> We have a patch internally that implements more of mmap(), but
>> unfortunately it's not quite ready to post.
>>
>> If you just want to do a read mapping (you don't care if writes to the
>> mmap'd region get written back to disk), and you don't mind just reading
>> the whole mmap region in up front (which you need to do, since SE mode
>> doesn't support page faulting), it's not too hard; just call
>> p->allocateMem() to allocate the memory in the simulated process, and then
>> read the data out of the file and use writeBlob() to copy it into the
>> memory you just allocated.
>>
>> Steve
>>
>> On Tue, Oct 7, 2014 at 6:14 AM, Ahmad Hassan via gem5-users <
>> gem5-users@gem5.org> wrote:
>>
>>> Hi,
>>>
>>> The existing implementation in GEM5 SE mode only supports MMAP to
>>> /dev/zero. Has anyone implemented MMAP in gem5 that can map a file from the
>>> disk? If not, how can I extend this?
>>>
>>> Regards,
>>>
>>> _______________________________________________
>>> gem5-users mailing list
>>> gem5-users@gem5.org
>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>
>>
>>
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to