Subject: Re: Fixing Linux emulated brk()
To: None <email@example.com>
From: Christos Zoulas <firstname.lastname@example.org>
Date: 03/15/2001 01:17:23
In article <1eqae8e.m1agqu4dykmkM@[10.0.12.137]>,
Emmanuel Dreyfus <email@example.com> wrote:
>> p_emul is const, so it's not a very good candidate. choosing p_vmspace
>> is just adding an emulation specific stuff in uvm, it's not very clean.
>> There is p_emuldata, but I'm not sure about how to use it. On what
>> should it point?
>I thought a bit about it: p_vmspace seems the good place. After all, we
>might want show a consistent break address to all processes, not only
>Linux ones. We can keep track the break address as seen by the process
>here. The real break address is beyond, page aligned, and we already
>keep track of it in p_vmspace.
As no other OS wants this, for now I would put it in p_emuldata.
If we find any other use, we can move it later. Don't change MI
code if there is no real need for it, and do the simplest change
to achieve your goal.