This website requires JavaScript.
Explore
Help
Register
Sign In
leandrof
/
linux
Watch
1
Star
0
Fork
0
You've already forked linux
forked from
Minki/linux
Code
Issues
Pull Requests
Packages
Projects
Releases
Wiki
Activity
3611553ef9
linux
/
drivers
/
virtio
/
Makefile
3 lines
76 B
Makefile
Raw
Normal View
History
Unescape
Escape
Virtio interface This attempts to implement a "virtual I/O" layer which should allow common drivers to be efficiently used across most virtual I/O mechanisms. It will no-doubt need further enhancement. The virtio drivers add buffers to virtio queues; as the buffers are consumed the driver "interrupt" callbacks are invoked. There is also a generic implementation of config space which drivers can query to get setup information from the host. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Dor Laor <dor.laor@qumranet.com> Cc: Arnd Bergmann <arnd@arndb.de>
2007-10-22 01:03:36 +00:00
obj-$(CONFIG_VIRTIO)
+=
virtio.o
Virtio helper routines for a descriptor ringbuffer implementation These helper routines supply most of the virtqueue_ops for hypervisors which want to use a ring for virtio. Unlike the previous lguest implementation: 1) The rings are variable sized (2^n-1 elements). 2) They have an unfortunate limit of 65535 bytes per sg element. 3) The page numbers are always 64 bit (PAE anyone?) 4) They no longer place used[] on a separate page, just a separate cacheline. 5) We do a modulo on a variable. We could be tricky if we cared. 6) Interrupts and notifies are suppressed using flags within the rings. Users need only get the ring pages and provide a notify hook (KVM wants the guest to allocate the rings, lguest does it sanely). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Dor Laor <dor.laor@qumranet.com>
2007-10-22 01:03:40 +00:00
obj-$(CONFIG_VIRTIO_RING)
+=
virtio_ring.o
Reference in New Issue
Copy Permalink