search for: 1bfbc640

Displaying 3 results from an estimated 3 matches for "1bfbc640".

Did you mean: 1bfbc5f0
2015 Nov 18
0
[RFC] kvmtool: add support for modern virtio-pci
...n=10 ret=1bfbc6f0 (detail=0x1bfbc6c0) Relocating init from 0x000f40a0 to 0x1bfbc6f0 (size 14464) malloc init init ivt init bda Add to e820 map: 0009fc00 00000400 2 init bios32 init PNPBIOS table init keyboard init mouse init pic math cp init PCI probe phys_alloc zone=0x1bfbff38 size=32 align=10 ret=1bfbc640 (detail=0x1bfbc610) PCI device 00:00.0 (vd=1af4:1000 c=0200) phys_alloc zone=0x1bfbff38 size=32 align=10 ret=1bfbc5f0 (detail=0x1bfbc5c0) PCI device 00:01.0 (vd=1af4:1001 c=0180) Found 2 PCI devices (max PCI bus is 00) tsc calibrate start=71959316 end=71968721 diff=9405 CPU Mhz=5 init timer init lp...
2015 Nov 18
2
[RFC] kvmtool: add support for modern virtio-pci
This is a first go at adding support for the modern (based on the 1.0 virtio spec) virtio-pci implementation. kvmtool makes it simple to add additional transports such as this because of it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and virtio-mmio) transport layer, and still allow users to choose to use either the legacy or the modern implementations (but setting
2015 Nov 18
2
[RFC] kvmtool: add support for modern virtio-pci
This is a first go at adding support for the modern (based on the 1.0 virtio spec) virtio-pci implementation. kvmtool makes it simple to add additional transports such as this because of it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and virtio-mmio) transport layer, and still allow users to choose to use either the legacy or the modern implementations (but setting