[RFC] First (incomplete) cut of Xen paravirt binding

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

 



Zachary Amsden <zach at vmware.com> writes:
>
> Yes, so we prefix all of this code with a third check - by probing for the VMI
> ROM.  A compatible PCI option ROM is only going to be detected on
> paravirtualized systems, and we do have a PCI vendor ID.  So we really need a
> probe type interface that happens after the head.S entry point (while it could
> be in head.S, the code is simpler to understand when written in C).

Yes.  Having a magic VMWare pci device at a fixed location on bus 0.
Sounds like an easy thing to test for.  It is a weird special case
in the code flow but it doesn't sound to bad.  And it is using a
mechanism that won't have architectural conflicts in the future.

I was half wondering if there was a BIOS call we might make in setup.S
to see if we were running under vmware.

Certainly there are some rough edges to work out here.

Eric


[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux