On 10/1/05, Subhobroto Sinha <[EMAIL PROTECTED]> wrote: > > When the Child is in control, its address tables > > will map to the real > > address stack for the child, while the same virtual > > address for the > > parent will translate to its own real address that > > is different from > > the child. > > So while every process have same initial stackframe > > address the real > > address for each will be different. > > Wow ! That is EXACTLY what I thought myself, as I > could not come up with a different explanation ! > > As a result I would very much like your explanation > from a citable source. Can you please tell me the name > of a book or something so that I can show my friends > that what I said is actually correct ! > The best source I could think of is what I read recently on "XEN Virtualization" http://openlab-mu-internal.web.cern.ch/openlab-mu-internal/Documents/Reports/Technical/Thesis_HarvardBjerke.pdf Please refer to Chapter 2, it gives details of a typical processor architecture and how the OS (linux) switches processes and a new set of register values are obtained for Page Tables and TLBs. This in essence gives each process its freedom and its own "space" and hence a common address for the stack. If you need additional references, I will send it later.
> BTW - are you the same J.P Mathew whowm I met at WBUT > (FGPA/ GCC port) ? If so, I would very much like to > talk to you again. I do have your cell no, but please > clarify (offlist please) I am the same J.P. Mathew you met in WBUT (but I got lost for some time). Now I am back and plan to install XEN soon!. > > Regards > > Subhobroto Sinha > Cheers JPM (Mathew) -- To unsubscribe, send mail to [EMAIL PROTECTED] with the body "unsubscribe ilug-cal" and an empty subject line. FAQ: http://www.ilug-cal.org/node.php?id=3
