Re: [rvm-core] Intel boot image runner forces virtual processor high nibble to be >= 3, why?

[Ian R. <ian...@ma...>]

2009/1/27 Richard Jones <R.E...@ke...>:
> I don't know the answer to this specific question but it bit me the
> other day.
> Here's the scenario:
>
> I am running JikesRVM with GCspy, using its C++ server.
> The world is stopped and the GCspy C++ server needs to extend one of
> its arrays; it calls "new short[size]" which succeeds.
> But shortly after, while populating that array, libvm.c tops with an
> error message that the frame is invalid (60).
>
> In the jconfigure days, I recall having to manually adjust the memory
> layout. My suspicion, not based on anything other than a hunch yet, is
> that JikesRVM and GCspy might be in conflict for memory.
>
> Richard

We still specify the memory layout, these days we use a properties
file though. The file is in build/targets and then corresponds to your
host (assuming you're not cross compiling).

By disabling the high nibble test and changing the memory region to
start of 0x1....... rather than 0x6......., I've been able to double
the maximum supported heap for me from 1280MB to 2560MB. I think it'd
make sense that this was the default in the trunk, any opinions?

Thanks,
Ian

> On 26 Jan 2009, at 23:38, Ian Rogers wrote:
>
>> Hi,
>>
>> can anyone remember why in libvm.c line 640 for Intel we fail if the
>> high nibble of a virtual processor is <3 ? Is this some cruft we can
>> now remove?
>>
>> Thanks,
>> Ian
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Jikesrvm-core mailing list
> Jik...@li...
> https://lists.sourceforge.net/lists/listinfo/jikesrvm-core
>