[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

OS Headers hypercall.h/hypervisor.h



The hypercalls implementation for Linux and FreeBSD have two key headers,
hypercall.h and hypervisor.h.  I'm curious why the implementations for
x86 and ARM* are so distinct.

I found it fairly straightforward to implement ARM* versions of the x86
_hypercall#() macros.  Once that is done, most of the wrappers in the x86
hypercall.h can be moved to a shared hypervisor.h header.

Why does Xen/ARM on Linux still have hypercall.S when merging the
headers should reduce maintainance?

Was GCC extended inline assembly language for ARM* thought too awful?

I'm also curious why these headers are part of the Linux kernel, instead
of being maintained by the Xen Project?


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg@xxxxxxx  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445





 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.