Skip to contentSkip to conversation

32-on-64 work progress

RFC PATCH In review Jan Beulich 3 participants 7 messages Oct 4, 2006 – Oct 11, 2006

lore
Share & tools
lore
#0 lore raw

cover 32-on-64 work progress

In an attempt to get some feedback on the ways I'm currently implementing this, I'm sending the set of patches as I currently have them. These permit a 32-bit PAE Linux dom0 kernel to come up on a 64-bit hypervisor, but progress only goes this far currently (very early during invocation of the first user mode code page table permissions aren't set correctly yet, making Xen kill the guest).

Jan

#1 lore raw
Quoted 6 lines · Jan Beulich

In an attempt to get some feedback on the ways I'm currently implementing this, I'm sending the set of patches as I currently have them. These permit a 32-bit PAE Linux dom0 kernel to come up on a 64-bit hypervisor, but progress only goes this far currently (very early during invocation of the first user mode code page table permissions aren't set correctly yet, making Xen kill the guest).

Patches don't apply for me, which changeset these patches are based on?

cheers,

Gerd

Signature · 2 lines
Gerd Hoffmann <[email protected]>
http://www.suse.de/~kraxel/julika-dora.jpeg
#2 lore raw
Quoted 10 lines
Quoted 1 line
Quoted 1 line

Gerd Hoffmann <[email protected]> 05.10.06 11:41 >>>

Quoted 6 lines · Jan Beulich

In an attempt to get some feedback on the ways I'm currently implementing this, I'm sending the set of patches as I currently have them. These permit a 32-bit PAE Linux dom0 kernel to come up on a 64-bit hypervisor, but progress only goes this far currently (very early during invocation of the first user mode code page table permissions aren't set correctly yet, making Xen kill the guest).

Patches don't apply for me, which changeset these patches are based on?

11690. They may depend on a few changes posted earlier (and not in the tree, yet), and I also didn't specifically check whether they would conflict with any of the few changes I always do right away after snapshotting the tree. There shouldn't be many conflicts, though. I didn't do that because the intention was mainly to have people look at the conceptual aspects, since, as I pointed out, things don't fully work, yet (though for the problem mentioned yesterday I already know the fix, I just wasn't able to implement this so far as I was given a higher priority job for today).

Jan

#3 lore raw

Hi,

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

In an attempt to get some feedback on the ways I'm currently implementing this, I'm sending the set of patches as I currently have them. These permit a 32-bit PAE Linux dom0 kernel to come up on a 64-bit hypervisor, but progress only goes this far currently (very early during invocation of the first user mode code page table permissions aren't set correctly yet, making Xen kill the guest).

Do you have any plans how domU bootup is going to work? Especially how hypercalls where one domain (typically dom0) changes the state of another domain are supposed to work? That includes the complete XEN_DOMCTL_* family, also some memory management hypercalls such as mach2phys and pagetable updates, maybe more. These are used by the domain tools to create a new domain and somehow must handle the case that we want be able to build 32bit guest domains from a 64bit dom0 (and visa versa?).

cheers,

Gerd

Signature · 2 lines
Gerd Hoffmann <[email protected]>
http://www.suse.de/~kraxel/julika-dora.jpeg
#4 lore raw
Quoted 8 lines · Gerd Hoffmann
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

In an attempt to get some feedback on the ways I'm currently implementing this, I'm sending the set of patches as I currently have them. These permit a 32-bit PAE Linux dom0 kernel to come up on a 64-bit hypervisor, but progress only goes this far currently (very early during invocation of the first user mode code page table permissions aren't set correctly yet, making
Xen kill the guest).

Quoted 8 lines

Do you have any plans how domU bootup is going to work? Especially how hypercalls where one domain (typically dom0) changes the state of another domain are supposed to work? That includes the complete XEN_DOMCTL_* family, also some memory management hypercalls such as mach2phys and pagetable updates, maybe more. These are used by the domain tools to create a new domain and somehow must handle the case that we want be able to build 32bit guest domains from a 64bit dom0 (and visa versa?).

The tools are going to have to know that they are building a 32p-on-64 guest. What problems do you perceive?

-- Keir

#5 lore raw
Quoted 11 lines · Keir Fraser
Quoted 8 lines · Gerd Hoffmann

Do you have any plans how domU bootup is going to work? Especially how hypercalls where one domain (typically dom0) changes the state of another domain are supposed to work? That includes the complete XEN_DOMCTL_* family, also some memory management hypercalls such as mach2phys and pagetable updates, maybe more. These are used by the domain tools to create a new domain and somehow must handle the case that we want be able to build 32bit guest domains from a 64bit dom0 (and visa versa?).

Quoted 2 lines

The tools are going to have to know that they are building a 32p-on-64 guest. What problems do you perceive?

Sure, they have to know. Question is what do you pass in when changing a 32bit guest from 64bit dom0. The 32bit struct? The 64bit struct? I think in many cases both will work just fine and we have just have to pick one way. XEN_DOMCTL_setvcpucontext is a icky one though, the 64bit
struct isn't a superset of the 32bit struct, so we probably have to
pass the 32bit version for 32bit guests.

cheers,

Gerd

Signature · 2 lines
Gerd Hoffmann <[email protected]>
http://www.suse.de/~kraxel/julika-dora.jpeg
#6 lore raw
Quoted 2 lines · Gerd Hoffmann

Sure, they have to know. Question is what do you pass in when changing a 32bit guest from 64bit dom0. The 32bit struct? The 64bit struct?

In general, the 64b struct. ABI shims in Xen will be selected based on the execution mode of the caller, not that subject domain (if there is one).

Quoted 4 lines

think in many cases both will work just fine and we have just have to pick one way. XEN_DOMCTL_setvcpucontext is a icky one though, the 64bit
struct isn't a superset of the 32bit struct, so we probably have to
pass the 32bit version for 32bit guests.

In this case we extend the semantics of get/setvcpucontext to say that you pass a pointer to a vcpu_context structure corresponding to the execution mode of the subject.

-- Keir