[OpenAFS-devel] i386_xenlinux26?

[John S. Bucy]

On Fri, Jun 17, 2005 at 11:08:13AM -0400, chas williams - CONTRACTOR wrote:
> In message <20050617143808.GB6394@bismuth.club.cc.cmu.edu>,"John S. Bucy" write
> s:
> >This was the first thing I tried; it crashes because its compiling
> >against asm-i386 instead of asm-xen, I think.  I was under the
> 
> building for a 2.6 kernel will probably get this right.  for a 2.4
> kernel it will likely be wrong.

It symlinks asm-i386 and I think it needs asm-xen.  I tried changing
it and I still get the GP fault.  My trace is similar to Rob Lee's;
its dying in osi_linux_mask().  "hardware protection" things like
interrupts and page tables are manipulated by calls into xen so it
needs xen's version of spin_lock_irq()/local_irq_disable()/etc.  I'm
guessing that its trying to use the native op to disable interrupts or
something which is triggering the #GP.

fyi: in xen, all domains run in ring 1.  The only difference between
domain 0 and unpriviledged domains is that domain 0 has access to
hardware and provides device drivers, etc.  xen then provides a
virtual block device and virtual ethernet device between dom0 and
domU.  dom0 can export lvm vols, etc, to domU.  The network is done
through the bridging stuff.  In both cases, its transparent to the
whole stack (net,vfs) above the device driver level.  A dom0 kernel
works fine in domU; you just save a little memory by compiling a domU
kernel with no device drivers -- that's the only difference.



john