|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] xen_phys_start for 32b
On 64b builds of Xen, xen_phys_start holds the starting (physical) address of
the hypervisor. However, on 32b systems it is 0. While I realize that 32b Xen
does not relocate the hypervisor, why not set this variable to the start of the
code (__pa(&_start)) so that it will represent the same thing on all builds?
Joe
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] xen_phys_start for 32b,
Cihula, Joseph <=
- Re: [Xen-devel] xen_phys_start for 32b, Keir Fraser
- RE: [Xen-devel] xen_phys_start for 32b, Cihula, Joseph
- Re: [Xen-devel] xen_phys_start for 32b, Keir Fraser
- RE: [Xen-devel] xen_phys_start for 32b, Cihula, Joseph
- Re: [Xen-devel] xen_phys_start for 32b, Keir Fraser
- RE: [Xen-devel] xen_phys_start for 32b, Cihula, Joseph
- Re: [Xen-devel] xen_phys_start for 32b, Keir Fraser
- RE: [Xen-devel] xen_phys_start for 32b, Cihula, Joseph
- Re: [Xen-devel] xen_phys_start for 32b, Keir Fraser
- [Xen-devel] Xenheap disappearance: (was: xen_phys_start for 32b), Dan Magenheimer
|
|
|
|
|