2009-07-30 22:03:45 +00:00
|
|
|
/*P:100
|
|
|
|
* This is the Launcher code, a simple program which lays out the "physical"
|
|
|
|
* memory for the new Guest by mapping the kernel image and the virtual
|
|
|
|
* devices, then opens /dev/lguest to tell the kernel about the Guest and
|
|
|
|
* control it.
|
|
|
|
:*/
|
2007-07-19 08:49:29 +00:00
|
|
|
#define _LARGEFILE64_SOURCE
|
|
|
|
#define _GNU_SOURCE
|
|
|
|
#include <stdio.h>
|
|
|
|
#include <string.h>
|
|
|
|
#include <unistd.h>
|
|
|
|
#include <err.h>
|
|
|
|
#include <stdint.h>
|
|
|
|
#include <stdlib.h>
|
|
|
|
#include <elf.h>
|
|
|
|
#include <sys/mman.h>
|
2007-08-28 21:35:59 +00:00
|
|
|
#include <sys/param.h>
|
2007-07-19 08:49:29 +00:00
|
|
|
#include <sys/types.h>
|
|
|
|
#include <sys/stat.h>
|
|
|
|
#include <sys/wait.h>
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
#include <sys/eventfd.h>
|
2007-07-19 08:49:29 +00:00
|
|
|
#include <fcntl.h>
|
|
|
|
#include <stdbool.h>
|
|
|
|
#include <errno.h>
|
|
|
|
#include <ctype.h>
|
|
|
|
#include <sys/socket.h>
|
|
|
|
#include <sys/ioctl.h>
|
|
|
|
#include <sys/time.h>
|
|
|
|
#include <time.h>
|
|
|
|
#include <netinet/in.h>
|
|
|
|
#include <net/if.h>
|
|
|
|
#include <linux/sockios.h>
|
|
|
|
#include <linux/if_tun.h>
|
|
|
|
#include <sys/uio.h>
|
|
|
|
#include <termios.h>
|
|
|
|
#include <getopt.h>
|
2007-10-22 01:24:22 +00:00
|
|
|
#include <assert.h>
|
|
|
|
#include <sched.h>
|
2008-02-05 04:49:56 +00:00
|
|
|
#include <limits.h>
|
|
|
|
#include <stddef.h>
|
2008-07-29 14:58:35 +00:00
|
|
|
#include <signal.h>
|
2011-01-21 03:37:28 +00:00
|
|
|
#include <pwd.h>
|
|
|
|
#include <grp.h>
|
2015-02-11 04:45:10 +00:00
|
|
|
#include <sys/user.h>
|
2015-02-11 04:45:11 +00:00
|
|
|
#include <linux/pci_regs.h>
|
2011-01-21 03:37:28 +00:00
|
|
|
|
2013-07-15 01:20:13 +00:00
|
|
|
#ifndef VIRTIO_F_ANY_LAYOUT
|
|
|
|
#define VIRTIO_F_ANY_LAYOUT 27
|
|
|
|
#endif
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:110
|
2011-07-22 05:09:50 +00:00
|
|
|
* We can ignore the 43 include files we need for this program, but I do want
|
2009-07-30 22:03:45 +00:00
|
|
|
* to draw attention to the use of kernel-style types.
|
2007-10-25 04:09:25 +00:00
|
|
|
*
|
|
|
|
* As Linus said, "C is a Spartan language, and so should your naming be." I
|
|
|
|
* like these abbreviations, so we define them here. Note that u64 is always
|
|
|
|
* unsigned long long, which works on all Linux systems: this means that we can
|
2009-07-30 22:03:45 +00:00
|
|
|
* use %llu in printf for any u64.
|
|
|
|
*/
|
2007-10-25 04:09:25 +00:00
|
|
|
typedef unsigned long long u64;
|
|
|
|
typedef uint32_t u32;
|
|
|
|
typedef uint16_t u16;
|
|
|
|
typedef uint8_t u8;
|
2007-07-26 17:41:03 +00:00
|
|
|
/*:*/
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2015-02-11 04:49:01 +00:00
|
|
|
#define VIRTIO_CONFIG_NO_LEGACY
|
2015-02-11 04:45:11 +00:00
|
|
|
#define VIRTIO_PCI_NO_LEGACY
|
2015-02-11 04:45:12 +00:00
|
|
|
#define VIRTIO_BLK_NO_LEGACY
|
2015-02-11 04:45:11 +00:00
|
|
|
|
|
|
|
/* Use in-kernel ones, which defines VIRTIO_F_VERSION_1 */
|
|
|
|
#include "../../include/uapi/linux/virtio_config.h"
|
2015-02-11 04:46:01 +00:00
|
|
|
#include "../../include/uapi/linux/virtio_net.h"
|
2015-02-11 04:45:12 +00:00
|
|
|
#include "../../include/uapi/linux/virtio_blk.h"
|
2013-07-04 01:52:58 +00:00
|
|
|
#include <linux/virtio_console.h>
|
2015-02-11 04:47:01 +00:00
|
|
|
#include "../../include/uapi/linux/virtio_rng.h"
|
2013-07-04 01:52:58 +00:00
|
|
|
#include <linux/virtio_ring.h>
|
2015-02-11 04:45:11 +00:00
|
|
|
#include "../../include/uapi/linux/virtio_pci.h"
|
2013-07-04 01:52:58 +00:00
|
|
|
#include <asm/bootparam.h>
|
|
|
|
#include "../../include/linux/lguest_launcher.h"
|
|
|
|
|
2007-07-19 08:49:29 +00:00
|
|
|
#define BRIDGE_PFX "bridge:"
|
|
|
|
#ifndef SIOCBRADDIF
|
|
|
|
#define SIOCBRADDIF 0x89a2 /* add interface to bridge */
|
|
|
|
#endif
|
2007-10-22 01:03:26 +00:00
|
|
|
/* We can have up to 256 pages for devices. */
|
|
|
|
#define DEVICE_PAGES 256
|
2008-07-29 14:58:37 +00:00
|
|
|
/* This will occupy 3 pages: it must be a power of 2. */
|
|
|
|
#define VIRTQUEUE_NUM 256
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:120
|
|
|
|
* verbose is both a global flag and a macro. The C preprocessor allows
|
|
|
|
* this, and although I wouldn't recommend it, it works quite nicely here.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
static bool verbose;
|
|
|
|
#define verbose(args...) \
|
|
|
|
do { if (verbose) printf(args); } while(0)
|
2007-07-26 17:41:03 +00:00
|
|
|
/*:*/
|
|
|
|
|
2007-10-22 01:03:26 +00:00
|
|
|
/* The pointer to the start of guest memory. */
|
|
|
|
static void *guest_base;
|
|
|
|
/* The maximum guest physical address allowed, and maximum possible. */
|
2015-02-11 04:45:11 +00:00
|
|
|
static unsigned long guest_limit, guest_max, guest_mmio;
|
2009-06-13 04:26:59 +00:00
|
|
|
/* The /dev/lguest file descriptor. */
|
|
|
|
static int lguest_fd;
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2008-01-07 13:05:23 +00:00
|
|
|
/* a per-cpu variable indicating whose vcpu is currently running */
|
|
|
|
static unsigned int __thread cpu_id;
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* 5 bit device number in the PCI_CONFIG_ADDR => 32 only */
|
|
|
|
#define MAX_PCI_DEVICES 32
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* This is our list of devices. */
|
2009-07-30 22:03:46 +00:00
|
|
|
struct device_list {
|
2007-10-22 01:24:22 +00:00
|
|
|
/* Counter to assign interrupt numbers. */
|
|
|
|
unsigned int next_irq;
|
|
|
|
|
|
|
|
/* Counter to print out convenient device numbers. */
|
|
|
|
unsigned int device_num;
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* The descriptor page for the devices. */
|
2007-10-22 01:24:22 +00:00
|
|
|
u8 *descpage;
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* A single linked list of devices. */
|
2007-07-19 08:49:29 +00:00
|
|
|
struct device *dev;
|
2009-07-30 22:03:45 +00:00
|
|
|
/* And a pointer to the last device for easy append. */
|
2008-02-05 04:49:56 +00:00
|
|
|
struct device *lastdev;
|
2015-02-11 04:45:11 +00:00
|
|
|
|
|
|
|
/* PCI devices. */
|
|
|
|
struct device *pci[MAX_PCI_DEVICES];
|
2007-07-19 08:49:29 +00:00
|
|
|
};
|
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* The list of Guest devices, based on command line arguments. */
|
|
|
|
static struct device_list devices;
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
struct virtio_pci_cfg_cap {
|
|
|
|
struct virtio_pci_cap cap;
|
|
|
|
u32 window; /* Data for BAR access. */
|
|
|
|
};
|
|
|
|
|
|
|
|
struct virtio_pci_mmio {
|
|
|
|
struct virtio_pci_common_cfg cfg;
|
|
|
|
u16 notify;
|
|
|
|
u8 isr;
|
|
|
|
u8 padding;
|
|
|
|
/* Device-specific configuration follows this. */
|
|
|
|
};
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* This is the layout (little-endian) of the PCI config space. */
|
|
|
|
struct pci_config {
|
|
|
|
u16 vendor_id, device_id;
|
|
|
|
u16 command, status;
|
|
|
|
u8 revid, prog_if, subclass, class;
|
|
|
|
u8 cacheline_size, lat_timer, header_type, bist;
|
|
|
|
u32 bar[6];
|
|
|
|
u32 cardbus_cis_ptr;
|
|
|
|
u16 subsystem_vendor_id, subsystem_device_id;
|
|
|
|
u32 expansion_rom_addr;
|
|
|
|
u8 capabilities, reserved1[3];
|
|
|
|
u32 reserved2;
|
|
|
|
u8 irq_line, irq_pin, min_grant, max_latency;
|
2015-02-11 04:45:11 +00:00
|
|
|
|
|
|
|
/* Now, this is the linked capability list. */
|
|
|
|
struct virtio_pci_cap common;
|
|
|
|
struct virtio_pci_notify_cap notify;
|
|
|
|
struct virtio_pci_cap isr;
|
|
|
|
struct virtio_pci_cap device;
|
|
|
|
/* FIXME: Implement this! */
|
|
|
|
struct virtio_pci_cfg_cap cfg_access;
|
2015-02-11 04:45:11 +00:00
|
|
|
};
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* The device structure describes a single device. */
|
2009-07-30 22:03:46 +00:00
|
|
|
struct device {
|
2007-07-26 17:41:03 +00:00
|
|
|
/* The linked-list pointer. */
|
2007-07-19 08:49:29 +00:00
|
|
|
struct device *next;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2009-06-13 04:26:58 +00:00
|
|
|
/* The device's descriptor, as mapped into the Guest. */
|
2007-07-19 08:49:29 +00:00
|
|
|
struct lguest_device_desc *desc;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2009-06-13 04:26:58 +00:00
|
|
|
/* We can't trust desc values once Guest has booted: we use these. */
|
|
|
|
unsigned int feature_len;
|
|
|
|
unsigned int num_vq;
|
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* The name of this device, for --verbose. */
|
|
|
|
const char *name;
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* Any queues attached to this device */
|
|
|
|
struct virtqueue *vq;
|
2007-07-19 08:49:29 +00:00
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* Is it operational */
|
|
|
|
bool running;
|
2008-05-03 02:50:53 +00:00
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* PCI configuration */
|
|
|
|
union {
|
|
|
|
struct pci_config config;
|
|
|
|
u32 config_words[sizeof(struct pci_config) / sizeof(u32)];
|
|
|
|
};
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* Features we offer, and those accepted. */
|
|
|
|
u64 features, features_accepted;
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* Device-specific config hangs off the end of this. */
|
|
|
|
struct virtio_pci_mmio *mmio;
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* PCI MMIO resources (all in BAR0) */
|
|
|
|
size_t mmio_size;
|
|
|
|
u32 mmio_addr;
|
|
|
|
|
2007-07-19 08:49:29 +00:00
|
|
|
/* Device-specific data. */
|
|
|
|
void *priv;
|
|
|
|
};
|
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* The virtqueue structure describes a queue attached to a device. */
|
2009-07-30 22:03:46 +00:00
|
|
|
struct virtqueue {
|
2007-10-22 01:24:22 +00:00
|
|
|
struct virtqueue *next;
|
|
|
|
|
|
|
|
/* Which device owns me. */
|
|
|
|
struct device *dev;
|
|
|
|
|
|
|
|
/* The configuration for this queue. */
|
|
|
|
struct lguest_vqconfig config;
|
|
|
|
|
|
|
|
/* The actual ring of buffers. */
|
|
|
|
struct vring vring;
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* The information about this virtqueue (we only use queue_size on) */
|
|
|
|
struct virtio_pci_common_cfg pci_config;
|
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* Last available index we saw. */
|
|
|
|
u16 last_avail_idx;
|
|
|
|
|
2009-06-13 04:27:11 +00:00
|
|
|
/* How many are used since we sent last irq? */
|
|
|
|
unsigned int pending_used;
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* Eventfd where Guest notifications arrive. */
|
|
|
|
int eventfd;
|
2008-05-30 20:09:46 +00:00
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* Function for the thread which is servicing this virtqueue. */
|
|
|
|
void (*service)(struct virtqueue *vq);
|
|
|
|
pid_t thread;
|
2007-10-22 01:24:22 +00:00
|
|
|
};
|
|
|
|
|
2007-12-28 08:56:24 +00:00
|
|
|
/* Remember the arguments to the program so we can "reboot" */
|
|
|
|
static char **main_args;
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* The original tty settings to restore on exit. */
|
|
|
|
static struct termios orig_term;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We have to be careful with barriers: our devices are all run in separate
|
2009-06-13 04:27:00 +00:00
|
|
|
* threads and so we need to make sure that changes visible to the Guest happen
|
2009-07-30 22:03:45 +00:00
|
|
|
* in precise order.
|
|
|
|
*/
|
2009-06-13 04:27:00 +00:00
|
|
|
#define wmb() __asm__ __volatile__("" : : : "memory")
|
2013-07-02 06:05:14 +00:00
|
|
|
#define rmb() __asm__ __volatile__("lock; addl $0,0(%%esp)" : : : "memory")
|
|
|
|
#define mb() __asm__ __volatile__("lock; addl $0,0(%%esp)" : : : "memory")
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2008-07-29 14:58:34 +00:00
|
|
|
/* Wrapper for the last available index. Makes it easier to change. */
|
|
|
|
#define lg_last_avail(vq) ((vq)->last_avail_idx)
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* The virtio configuration space is defined to be little-endian. x86 is
|
|
|
|
* little-endian too, but it's nice to be explicit so we have these helpers.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
#define cpu_to_le16(v16) (v16)
|
|
|
|
#define cpu_to_le32(v32) (v32)
|
|
|
|
#define cpu_to_le64(v64) (v64)
|
|
|
|
#define le16_to_cpu(v16) (v16)
|
|
|
|
#define le32_to_cpu(v32) (v32)
|
2008-02-05 04:49:56 +00:00
|
|
|
#define le64_to_cpu(v64) (v64)
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2008-07-29 14:58:33 +00:00
|
|
|
/* Is this iovec empty? */
|
|
|
|
static bool iov_empty(const struct iovec iov[], unsigned int num_iov)
|
|
|
|
{
|
|
|
|
unsigned int i;
|
|
|
|
|
|
|
|
for (i = 0; i < num_iov; i++)
|
|
|
|
if (iov[i].iov_len)
|
|
|
|
return false;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Take len bytes from the front of this iovec. */
|
2012-10-16 13:26:13 +00:00
|
|
|
static void iov_consume(struct iovec iov[], unsigned num_iov,
|
|
|
|
void *dest, unsigned len)
|
2008-07-29 14:58:33 +00:00
|
|
|
{
|
|
|
|
unsigned int i;
|
|
|
|
|
|
|
|
for (i = 0; i < num_iov; i++) {
|
|
|
|
unsigned int used;
|
|
|
|
|
|
|
|
used = iov[i].iov_len < len ? iov[i].iov_len : len;
|
2012-10-16 13:26:13 +00:00
|
|
|
if (dest) {
|
|
|
|
memcpy(dest, iov[i].iov_base, used);
|
|
|
|
dest += used;
|
|
|
|
}
|
2008-07-29 14:58:33 +00:00
|
|
|
iov[i].iov_base += used;
|
|
|
|
iov[i].iov_len -= used;
|
|
|
|
len -= used;
|
|
|
|
}
|
2012-10-16 13:26:13 +00:00
|
|
|
if (len != 0)
|
|
|
|
errx(1, "iovec too short!");
|
2008-07-29 14:58:33 +00:00
|
|
|
}
|
|
|
|
|
2008-02-05 04:50:03 +00:00
|
|
|
/* The device virtqueue descriptors are followed by feature bitmasks. */
|
|
|
|
static u8 *get_feature_bits(struct device *dev)
|
|
|
|
{
|
|
|
|
return (u8 *)(dev->desc + 1)
|
2009-06-13 04:26:58 +00:00
|
|
|
+ dev->num_vq * sizeof(struct lguest_vqconfig);
|
2008-02-05 04:50:03 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:100
|
|
|
|
* The Launcher code itself takes us out into userspace, that scary place where
|
|
|
|
* pointers run wild and free! Unfortunately, like most userspace programs,
|
|
|
|
* it's quite boring (which is why everyone likes to hack on the kernel!).
|
|
|
|
* Perhaps if you make up an Lguest Drinking Game at this point, it will get
|
|
|
|
* you through this section. Or, maybe not.
|
2007-10-22 01:03:26 +00:00
|
|
|
*
|
|
|
|
* The Launcher sets up a big chunk of memory to be the Guest's "physical"
|
|
|
|
* memory and stores it in "guest_base". In other words, Guest physical ==
|
|
|
|
* Launcher virtual with an offset.
|
|
|
|
*
|
|
|
|
* This can be tough to get your head around, but usually it just means that we
|
2010-04-22 22:08:02 +00:00
|
|
|
* use these trivial conversion functions when the Guest gives us its
|
2009-07-30 22:03:45 +00:00
|
|
|
* "physical" addresses:
|
|
|
|
*/
|
2007-10-22 01:03:26 +00:00
|
|
|
static void *from_guest_phys(unsigned long addr)
|
|
|
|
{
|
|
|
|
return guest_base + addr;
|
|
|
|
}
|
|
|
|
|
|
|
|
static unsigned long to_guest_phys(const void *addr)
|
|
|
|
{
|
|
|
|
return (addr - guest_base);
|
|
|
|
}
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/*L:130
|
|
|
|
* Loading the Kernel.
|
|
|
|
*
|
|
|
|
* We start with couple of simple helper routines. open_or_die() avoids
|
2009-07-30 22:03:45 +00:00
|
|
|
* error-checking code cluttering the callers:
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
static int open_or_die(const char *name, int flags)
|
|
|
|
{
|
|
|
|
int fd = open(name, flags);
|
|
|
|
if (fd < 0)
|
|
|
|
err(1, "Failed to open %s", name);
|
|
|
|
return fd;
|
|
|
|
}
|
|
|
|
|
2007-10-22 01:03:26 +00:00
|
|
|
/* map_zeroed_pages() takes a number of pages. */
|
|
|
|
static void *map_zeroed_pages(unsigned int num)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
2007-10-22 01:03:26 +00:00
|
|
|
int fd = open_or_die("/dev/zero", O_RDONLY);
|
|
|
|
void *addr;
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We use a private mapping (ie. if we write to the page, it will be
|
2011-01-21 03:37:28 +00:00
|
|
|
* copied). We allocate an extra two pages PROT_NONE to act as guard
|
|
|
|
* pages against read/write attempts that exceed allocated space.
|
2009-07-30 22:03:45 +00:00
|
|
|
*/
|
2011-01-21 03:37:28 +00:00
|
|
|
addr = mmap(NULL, getpagesize() * (num+2),
|
|
|
|
PROT_NONE, MAP_PRIVATE, fd, 0);
|
|
|
|
|
2007-10-22 01:03:26 +00:00
|
|
|
if (addr == MAP_FAILED)
|
tree-wide: fix assorted typos all over the place
That is "success", "unknown", "through", "performance", "[re|un]mapping"
, "access", "default", "reasonable", "[con]currently", "temperature"
, "channel", "[un]used", "application", "example","hierarchy", "therefore"
, "[over|under]flow", "contiguous", "threshold", "enough" and others.
Signed-off-by: André Goddard Rosa <andre.goddard@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
2009-11-14 15:09:05 +00:00
|
|
|
err(1, "Mmapping %u pages of /dev/zero", num);
|
2009-07-30 22:03:45 +00:00
|
|
|
|
2011-01-21 03:37:28 +00:00
|
|
|
if (mprotect(addr + getpagesize(), getpagesize() * num,
|
|
|
|
PROT_READ|PROT_WRITE) == -1)
|
|
|
|
err(1, "mprotect rw %u pages failed", num);
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* One neat mmap feature is that you can close the fd, and it
|
|
|
|
* stays mapped.
|
|
|
|
*/
|
2008-06-13 13:04:58 +00:00
|
|
|
close(fd);
|
2007-10-22 01:03:26 +00:00
|
|
|
|
2011-01-21 03:37:28 +00:00
|
|
|
/* Return address after PROT_NONE page */
|
|
|
|
return addr + getpagesize();
|
2007-10-22 01:03:26 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Get some more pages for a device. */
|
|
|
|
static void *get_pages(unsigned int num)
|
|
|
|
{
|
|
|
|
void *addr = from_guest_phys(guest_limit);
|
|
|
|
|
|
|
|
guest_limit += num * getpagesize();
|
|
|
|
if (guest_limit > guest_max)
|
|
|
|
errx(1, "Not enough memory for devices");
|
|
|
|
return addr;
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* Get some bytes which won't be mapped into the guest. */
|
|
|
|
static unsigned long get_mmio_region(size_t size)
|
|
|
|
{
|
|
|
|
unsigned long addr = guest_mmio;
|
|
|
|
size_t i;
|
|
|
|
|
|
|
|
if (!size)
|
|
|
|
return addr;
|
|
|
|
|
|
|
|
/* Size has to be a power of 2 (and multiple of 16) */
|
|
|
|
for (i = 1; i < size; i <<= 1);
|
|
|
|
|
|
|
|
guest_mmio += i;
|
|
|
|
|
|
|
|
return addr;
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This routine is used to load the kernel or initrd. It tries mmap, but if
|
2007-08-28 21:35:59 +00:00
|
|
|
* that fails (Plan 9's kernel file isn't nicely aligned on page boundaries),
|
2009-07-30 22:03:45 +00:00
|
|
|
* it falls back to reading the memory in.
|
|
|
|
*/
|
2007-08-28 21:35:59 +00:00
|
|
|
static void map_at(int fd, void *addr, unsigned long offset, unsigned long len)
|
|
|
|
{
|
|
|
|
ssize_t r;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We map writable even though for some segments are marked read-only.
|
2007-08-28 21:35:59 +00:00
|
|
|
* The kernel really wants to be writable: it patches its own
|
|
|
|
* instructions.
|
|
|
|
*
|
|
|
|
* MAP_PRIVATE means that the page won't be copied until a write is
|
|
|
|
* done to it. This allows us to share untouched memory between
|
2009-07-30 22:03:45 +00:00
|
|
|
* Guests.
|
|
|
|
*/
|
2011-01-21 03:37:28 +00:00
|
|
|
if (mmap(addr, len, PROT_READ|PROT_WRITE,
|
2007-08-28 21:35:59 +00:00
|
|
|
MAP_FIXED|MAP_PRIVATE, fd, offset) != MAP_FAILED)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* pread does a seek and a read in one shot: saves a few lines. */
|
|
|
|
r = pread(fd, addr, len, offset);
|
|
|
|
if (r != len)
|
|
|
|
err(1, "Reading offset %lu len %lu gave %zi", offset, len, r);
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This routine takes an open vmlinux image, which is in ELF, and maps it into
|
2007-07-26 17:41:03 +00:00
|
|
|
* the Guest memory. ELF = Embedded Linking Format, which is the format used
|
|
|
|
* by all modern binaries on Linux including the kernel.
|
|
|
|
*
|
|
|
|
* The ELF headers give *two* addresses: a physical address, and a virtual
|
2007-10-22 01:03:36 +00:00
|
|
|
* address. We use the physical address; the Guest will map itself to the
|
|
|
|
* virtual address.
|
2007-07-26 17:41:03 +00:00
|
|
|
*
|
2009-07-30 22:03:45 +00:00
|
|
|
* We return the starting address.
|
|
|
|
*/
|
2007-10-22 01:03:36 +00:00
|
|
|
static unsigned long map_elf(int elf_fd, const Elf32_Ehdr *ehdr)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
Elf32_Phdr phdr[ehdr->e_phnum];
|
|
|
|
unsigned int i;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Sanity checks on the main ELF header: an x86 executable with a
|
|
|
|
* reasonable number of correctly-sized program headers.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
if (ehdr->e_type != ET_EXEC
|
|
|
|
|| ehdr->e_machine != EM_386
|
|
|
|
|| ehdr->e_phentsize != sizeof(Elf32_Phdr)
|
|
|
|
|| ehdr->e_phnum < 1 || ehdr->e_phnum > 65536U/sizeof(Elf32_Phdr))
|
|
|
|
errx(1, "Malformed elf header");
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* An ELF executable contains an ELF header and a number of "program"
|
2007-07-26 17:41:03 +00:00
|
|
|
* headers which indicate which parts ("segments") of the program to
|
2009-07-30 22:03:45 +00:00
|
|
|
* load where.
|
|
|
|
*/
|
2007-07-26 17:41:03 +00:00
|
|
|
|
|
|
|
/* We read in all the program headers at once: */
|
2007-07-19 08:49:29 +00:00
|
|
|
if (lseek(elf_fd, ehdr->e_phoff, SEEK_SET) < 0)
|
|
|
|
err(1, "Seeking to program headers");
|
|
|
|
if (read(elf_fd, phdr, sizeof(phdr)) != sizeof(phdr))
|
|
|
|
err(1, "Reading program headers");
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Try all the headers: there are usually only three. A read-only one,
|
|
|
|
* a read-write one, and a "note" section which we don't load.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
for (i = 0; i < ehdr->e_phnum; i++) {
|
2007-07-26 17:41:03 +00:00
|
|
|
/* If this isn't a loadable segment, we ignore it */
|
2007-07-19 08:49:29 +00:00
|
|
|
if (phdr[i].p_type != PT_LOAD)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
verbose("Section %i: size %i addr %p\n",
|
|
|
|
i, phdr[i].p_memsz, (void *)phdr[i].p_paddr);
|
|
|
|
|
2007-08-28 21:35:59 +00:00
|
|
|
/* We map this section of the file at its physical address. */
|
2007-10-22 01:03:26 +00:00
|
|
|
map_at(elf_fd, from_guest_phys(phdr[i].p_paddr),
|
2007-08-28 21:35:59 +00:00
|
|
|
phdr[i].p_offset, phdr[i].p_filesz);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2007-10-22 01:29:44 +00:00
|
|
|
/* The entry point is given in the ELF header. */
|
|
|
|
return ehdr->e_entry;
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:150
|
|
|
|
* A bzImage, unlike an ELF file, is not meant to be loaded. You're supposed
|
|
|
|
* to jump into it and it will unpack itself. We used to have to perform some
|
|
|
|
* hairy magic because the unpacking code scared me.
|
2007-07-26 17:41:03 +00:00
|
|
|
*
|
2007-10-22 01:29:56 +00:00
|
|
|
* Fortunately, Jeremy Fitzhardinge convinced me it wasn't that hard and wrote
|
|
|
|
* a small patch to jump over the tricky bits in the Guest, so now we just read
|
2009-07-30 22:03:45 +00:00
|
|
|
* the funky header so we know where in the file to load, and away we go!
|
|
|
|
*/
|
2007-10-22 01:03:36 +00:00
|
|
|
static unsigned long load_bzimage(int fd)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
2007-10-22 01:29:57 +00:00
|
|
|
struct boot_params boot;
|
2007-10-22 01:29:56 +00:00
|
|
|
int r;
|
|
|
|
/* Modern bzImages get loaded at 1M. */
|
|
|
|
void *p = from_guest_phys(0x100000);
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Go back to the start of the file and read the header. It should be
|
2011-08-15 00:02:26 +00:00
|
|
|
* a Linux boot header (see Documentation/x86/boot.txt)
|
2009-07-30 22:03:45 +00:00
|
|
|
*/
|
2007-10-22 01:29:56 +00:00
|
|
|
lseek(fd, 0, SEEK_SET);
|
2007-10-22 01:29:57 +00:00
|
|
|
read(fd, &boot, sizeof(boot));
|
2007-10-22 01:29:56 +00:00
|
|
|
|
2007-10-22 01:29:57 +00:00
|
|
|
/* Inside the setup_hdr, we expect the magic "HdrS" */
|
|
|
|
if (memcmp(&boot.hdr.header, "HdrS", 4) != 0)
|
2007-10-22 01:29:56 +00:00
|
|
|
errx(1, "This doesn't look like a bzImage to me");
|
|
|
|
|
2007-10-22 01:29:57 +00:00
|
|
|
/* Skip over the extra sectors of the header. */
|
|
|
|
lseek(fd, (boot.hdr.setup_sects+1) * 512, SEEK_SET);
|
2007-10-22 01:29:56 +00:00
|
|
|
|
|
|
|
/* Now read everything into memory. in nice big chunks. */
|
|
|
|
while ((r = read(fd, p, 65536)) > 0)
|
|
|
|
p += r;
|
|
|
|
|
2007-10-22 01:29:57 +00:00
|
|
|
/* Finally, code32_start tells us where to enter the kernel. */
|
|
|
|
return boot.hdr.code32_start;
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:140
|
|
|
|
* Loading the kernel is easy when it's a "vmlinux", but most kernels
|
2007-10-25 05:02:50 +00:00
|
|
|
* come wrapped up in the self-decompressing "bzImage" format. With a little
|
2009-07-30 22:03:45 +00:00
|
|
|
* work, we can load those, too.
|
|
|
|
*/
|
2007-10-22 01:03:36 +00:00
|
|
|
static unsigned long load_kernel(int fd)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
Elf32_Ehdr hdr;
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* Read in the first few bytes. */
|
2007-07-19 08:49:29 +00:00
|
|
|
if (read(fd, &hdr, sizeof(hdr)) != sizeof(hdr))
|
|
|
|
err(1, "Reading kernel");
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* If it's an ELF file, it starts with "\177ELF" */
|
2007-07-19 08:49:29 +00:00
|
|
|
if (memcmp(hdr.e_ident, ELFMAG, SELFMAG) == 0)
|
2007-10-22 01:03:36 +00:00
|
|
|
return map_elf(fd, &hdr);
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2008-03-28 16:05:53 +00:00
|
|
|
/* Otherwise we assume it's a bzImage, and try to load it. */
|
2007-10-22 01:03:36 +00:00
|
|
|
return load_bzimage(fd);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This is a trivial little helper to align pages. Andi Kleen hated it because
|
2007-07-26 17:41:03 +00:00
|
|
|
* it calls getpagesize() twice: "it's dumb code."
|
|
|
|
*
|
|
|
|
* Kernel guys get really het up about optimization, even when it's not
|
2009-07-30 22:03:45 +00:00
|
|
|
* necessary. I leave this code as a reaction against that.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
static inline unsigned long page_align(unsigned long addr)
|
|
|
|
{
|
2007-07-26 17:41:03 +00:00
|
|
|
/* Add upwards and truncate downwards. */
|
2007-07-19 08:49:29 +00:00
|
|
|
return ((addr + getpagesize()-1) & ~(getpagesize()-1));
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:180
|
|
|
|
* An "initial ram disk" is a disk image loaded into memory along with the
|
|
|
|
* kernel which the kernel can use to boot from without needing any drivers.
|
|
|
|
* Most distributions now use this as standard: the initrd contains the code to
|
|
|
|
* load the appropriate driver modules for the current machine.
|
2007-07-26 17:41:03 +00:00
|
|
|
*
|
|
|
|
* Importantly, James Morris works for RedHat, and Fedora uses initrds for its
|
2009-07-30 22:03:45 +00:00
|
|
|
* kernels. He sent me this (and tells me when I break it).
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
static unsigned long load_initrd(const char *name, unsigned long mem)
|
|
|
|
{
|
|
|
|
int ifd;
|
|
|
|
struct stat st;
|
|
|
|
unsigned long len;
|
|
|
|
|
|
|
|
ifd = open_or_die(name, O_RDONLY);
|
2007-07-26 17:41:03 +00:00
|
|
|
/* fstat() is needed to get the file size. */
|
2007-07-19 08:49:29 +00:00
|
|
|
if (fstat(ifd, &st) < 0)
|
|
|
|
err(1, "fstat() on initrd '%s'", name);
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We map the initrd at the top of memory, but mmap wants it to be
|
|
|
|
* page-aligned, so we round the size up for that.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
len = page_align(st.st_size);
|
2007-10-22 01:03:26 +00:00
|
|
|
map_at(ifd, from_guest_phys(mem - len), 0, st.st_size);
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Once a file is mapped, you can close the file descriptor. It's a
|
|
|
|
* little odd, but quite useful.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
close(ifd);
|
2007-08-28 21:35:59 +00:00
|
|
|
verbose("mapped initrd %s size=%lu @ %p\n", name, len, (void*)mem-len);
|
2007-07-26 17:41:03 +00:00
|
|
|
|
|
|
|
/* We return the initrd size. */
|
2007-07-19 08:49:29 +00:00
|
|
|
return len;
|
|
|
|
}
|
2007-10-25 05:02:50 +00:00
|
|
|
/*:*/
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Simple routine to roll all the commandline arguments together with spaces
|
|
|
|
* between them.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
static void concat(char *dst, char *args[])
|
|
|
|
{
|
|
|
|
unsigned int i, len = 0;
|
|
|
|
|
|
|
|
for (i = 0; args[i]; i++) {
|
2008-03-10 15:39:03 +00:00
|
|
|
if (i) {
|
|
|
|
strcat(dst+len, " ");
|
|
|
|
len++;
|
|
|
|
}
|
2007-07-19 08:49:29 +00:00
|
|
|
strcpy(dst+len, args[i]);
|
2008-03-10 15:39:03 +00:00
|
|
|
len += strlen(args[i]);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
/* In case it's empty. */
|
|
|
|
dst[len] = '\0';
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:185
|
|
|
|
* This is where we actually tell the kernel to initialize the Guest. We
|
2007-10-25 05:02:50 +00:00
|
|
|
* saw the arguments it expects when we looked at initialize() in lguest_user.c:
|
2008-09-29 04:40:07 +00:00
|
|
|
* the base of Guest "physical" memory, the top physical page to allow and the
|
2009-07-30 22:03:45 +00:00
|
|
|
* entry point for the Guest.
|
|
|
|
*/
|
2009-06-13 04:26:59 +00:00
|
|
|
static void tell_kernel(unsigned long start)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
2007-10-22 01:03:31 +00:00
|
|
|
unsigned long args[] = { LHREQ_INITIALIZE,
|
|
|
|
(unsigned long)guest_base,
|
2015-02-11 04:45:10 +00:00
|
|
|
guest_limit / getpagesize(), start,
|
2015-02-11 04:45:11 +00:00
|
|
|
(guest_mmio+getpagesize()-1) / getpagesize() };
|
|
|
|
verbose("Guest: %p - %p (%#lx, MMIO %#lx)\n",
|
|
|
|
guest_base, guest_base + guest_limit,
|
|
|
|
guest_limit, guest_mmio);
|
2009-06-13 04:26:59 +00:00
|
|
|
lguest_fd = open_or_die("/dev/lguest", O_RDWR);
|
|
|
|
if (write(lguest_fd, args, sizeof(args)) < 0)
|
2007-07-19 08:49:29 +00:00
|
|
|
err(1, "Writing to /dev/lguest");
|
|
|
|
}
|
2007-07-26 17:41:03 +00:00
|
|
|
/*:*/
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:200
|
2007-07-26 17:41:03 +00:00
|
|
|
* Device Handling.
|
|
|
|
*
|
2007-10-25 05:02:50 +00:00
|
|
|
* When the Guest gives us a buffer, it sends an array of addresses and sizes.
|
2007-07-26 17:41:03 +00:00
|
|
|
* We need to make sure it's not trying to reach into the Launcher itself, so
|
2007-10-25 05:02:50 +00:00
|
|
|
* we have a convenient routine which checks it and exits with an error message
|
2007-07-26 17:41:03 +00:00
|
|
|
* if something funny is going on:
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
static void *_check_pointer(unsigned long addr, unsigned int size,
|
|
|
|
unsigned int line)
|
|
|
|
{
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
2011-01-21 03:37:28 +00:00
|
|
|
* Check if the requested address and size exceeds the allocated memory,
|
|
|
|
* or addr + size wraps around.
|
2009-07-30 22:03:45 +00:00
|
|
|
*/
|
2011-01-21 03:37:28 +00:00
|
|
|
if ((addr + size) > guest_limit || (addr + size) < addr)
|
2007-10-22 01:24:22 +00:00
|
|
|
errx(1, "%s:%i: Invalid address %#lx", __FILE__, line, addr);
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We return a pointer for the caller's convenience, now we know it's
|
|
|
|
* safe to use.
|
|
|
|
*/
|
2007-10-22 01:03:26 +00:00
|
|
|
return from_guest_phys(addr);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
2007-07-26 17:41:03 +00:00
|
|
|
/* A macro which transparently hands the line number to the real function. */
|
2007-07-19 08:49:29 +00:00
|
|
|
#define check_pointer(addr,size) _check_pointer(addr, size, __LINE__)
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Each buffer in the virtqueues is actually a chain of descriptors. This
|
2007-10-25 05:02:50 +00:00
|
|
|
* function returns the next descriptor in the chain, or vq->vring.num if we're
|
2009-07-30 22:03:45 +00:00
|
|
|
* at the end.
|
|
|
|
*/
|
2009-05-11 17:11:46 +00:00
|
|
|
static unsigned next_desc(struct vring_desc *desc,
|
|
|
|
unsigned int i, unsigned int max)
|
2007-10-22 01:24:22 +00:00
|
|
|
{
|
|
|
|
unsigned int next;
|
|
|
|
|
|
|
|
/* If this descriptor says it doesn't chain, we're done. */
|
2009-05-11 17:11:46 +00:00
|
|
|
if (!(desc[i].flags & VRING_DESC_F_NEXT))
|
|
|
|
return max;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
|
|
|
/* Check they're not leading us off end of descriptors. */
|
2009-05-11 17:11:46 +00:00
|
|
|
next = desc[i].next;
|
2007-10-22 01:24:22 +00:00
|
|
|
/* Make sure compiler knows to grab that: we don't want it changing! */
|
|
|
|
wmb();
|
|
|
|
|
2009-05-11 17:11:46 +00:00
|
|
|
if (next >= max)
|
2007-10-22 01:24:22 +00:00
|
|
|
errx(1, "Desc next is %u", next);
|
|
|
|
|
|
|
|
return next;
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This actually sends the interrupt for this virtqueue, if we've used a
|
|
|
|
* buffer.
|
|
|
|
*/
|
2009-06-13 04:27:11 +00:00
|
|
|
static void trigger_irq(struct virtqueue *vq)
|
|
|
|
{
|
|
|
|
unsigned long buf[] = { LHREQ_IRQ, vq->config.irq };
|
|
|
|
|
2009-06-13 04:27:11 +00:00
|
|
|
/* Don't inform them if nothing used. */
|
|
|
|
if (!vq->pending_used)
|
|
|
|
return;
|
|
|
|
vq->pending_used = 0;
|
|
|
|
|
2009-09-24 04:26:47 +00:00
|
|
|
/* If they don't want an interrupt, don't send one... */
|
|
|
|
if (vq->vring.avail->flags & VRING_AVAIL_F_NO_INTERRUPT) {
|
2011-05-30 17:14:12 +00:00
|
|
|
return;
|
2009-09-24 04:26:47 +00:00
|
|
|
}
|
2009-06-13 04:27:11 +00:00
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* For a PCI device, set isr to 1 (queue interrupt pending) */
|
|
|
|
if (vq->dev->mmio)
|
|
|
|
vq->dev->mmio->isr = 0x1;
|
|
|
|
|
2009-06-13 04:27:11 +00:00
|
|
|
/* Send the Guest an interrupt tell them we used something up. */
|
|
|
|
if (write(lguest_fd, buf, sizeof(buf)) != 0)
|
|
|
|
err(1, "Triggering irq %i", vq->config.irq);
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
2009-07-30 22:03:45 +00:00
|
|
|
* This looks in the virtqueue for the first available buffer, and converts
|
2007-10-22 01:24:22 +00:00
|
|
|
* it to an iovec for convenient access. Since descriptors consist of some
|
|
|
|
* number of output then some number of input descriptors, it's actually two
|
|
|
|
* iovecs, but we pack them into one and note how many of each there were.
|
|
|
|
*
|
2009-07-30 22:03:45 +00:00
|
|
|
* This function waits if necessary, and returns the descriptor number found.
|
2009-07-30 22:03:45 +00:00
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static unsigned wait_for_vq_desc(struct virtqueue *vq,
|
|
|
|
struct iovec iov[],
|
|
|
|
unsigned int *out_num, unsigned int *in_num)
|
2007-10-22 01:24:22 +00:00
|
|
|
{
|
2009-05-11 17:11:46 +00:00
|
|
|
unsigned int i, head, max;
|
|
|
|
struct vring_desc *desc;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
u16 last_avail = lg_last_avail(vq);
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* There's nothing available? */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
while (last_avail == vq->vring.avail->idx) {
|
|
|
|
u64 event;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Since we're about to sleep, now is a good time to tell the
|
|
|
|
* Guest about what we've used up to now.
|
|
|
|
*/
|
2009-06-13 04:27:11 +00:00
|
|
|
trigger_irq(vq);
|
|
|
|
|
2009-06-13 04:27:12 +00:00
|
|
|
/* OK, now we need to know about added descriptors. */
|
|
|
|
vq->vring.used->flags &= ~VRING_USED_F_NO_NOTIFY;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* They could have slipped one in as we were doing that: make
|
|
|
|
* sure it's written, then check again.
|
|
|
|
*/
|
2009-06-13 04:27:12 +00:00
|
|
|
mb();
|
|
|
|
if (last_avail != vq->vring.avail->idx) {
|
|
|
|
vq->vring.used->flags |= VRING_USED_F_NO_NOTIFY;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* Nothing new? Wait for eventfd to tell us they refilled. */
|
|
|
|
if (read(vq->eventfd, &event, sizeof(event)) != sizeof(event))
|
|
|
|
errx(1, "Event read failed?");
|
2009-06-13 04:27:12 +00:00
|
|
|
|
|
|
|
/* We don't need to be notified again. */
|
|
|
|
vq->vring.used->flags |= VRING_USED_F_NO_NOTIFY;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
}
|
2007-10-22 01:24:22 +00:00
|
|
|
|
|
|
|
/* Check it isn't doing very strange things with descriptor numbers. */
|
2008-07-29 14:58:34 +00:00
|
|
|
if ((u16)(vq->vring.avail->idx - last_avail) > vq->vring.num)
|
2007-10-22 01:24:22 +00:00
|
|
|
errx(1, "Guest moved used index from %u to %u",
|
2008-07-29 14:58:34 +00:00
|
|
|
last_avail, vq->vring.avail->idx);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2013-07-02 06:05:13 +00:00
|
|
|
/*
|
|
|
|
* Make sure we read the descriptor number *after* we read the ring
|
|
|
|
* update; don't let the cpu or compiler change the order.
|
|
|
|
*/
|
|
|
|
rmb();
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Grab the next descriptor number they're advertising, and increment
|
|
|
|
* the index we've seen.
|
|
|
|
*/
|
2008-07-29 14:58:34 +00:00
|
|
|
head = vq->vring.avail->ring[last_avail % vq->vring.num];
|
|
|
|
lg_last_avail(vq)++;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
|
|
|
/* If their number is silly, that's a fatal mistake. */
|
|
|
|
if (head >= vq->vring.num)
|
|
|
|
errx(1, "Guest says index %u is available", head);
|
|
|
|
|
|
|
|
/* When we start there are none of either input nor output. */
|
|
|
|
*out_num = *in_num = 0;
|
|
|
|
|
2009-05-11 17:11:46 +00:00
|
|
|
max = vq->vring.num;
|
|
|
|
desc = vq->vring.desc;
|
2007-10-22 01:24:22 +00:00
|
|
|
i = head;
|
2009-05-11 17:11:46 +00:00
|
|
|
|
2013-07-02 06:05:13 +00:00
|
|
|
/*
|
|
|
|
* We have to read the descriptor after we read the descriptor number,
|
|
|
|
* but there's a data dependency there so the CPU shouldn't reorder
|
|
|
|
* that: no rmb() required.
|
|
|
|
*/
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* If this is an indirect entry, then this buffer contains a descriptor
|
|
|
|
* table which we handle as if it's any normal descriptor chain.
|
|
|
|
*/
|
2009-05-11 17:11:46 +00:00
|
|
|
if (desc[i].flags & VRING_DESC_F_INDIRECT) {
|
|
|
|
if (desc[i].len % sizeof(struct vring_desc))
|
|
|
|
errx(1, "Invalid size for indirect buffer table");
|
|
|
|
|
|
|
|
max = desc[i].len / sizeof(struct vring_desc);
|
|
|
|
desc = check_pointer(desc[i].addr, desc[i].len);
|
|
|
|
i = 0;
|
|
|
|
}
|
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
do {
|
|
|
|
/* Grab the first descriptor, and check it's OK. */
|
2009-05-11 17:11:46 +00:00
|
|
|
iov[*out_num + *in_num].iov_len = desc[i].len;
|
2007-10-22 01:24:22 +00:00
|
|
|
iov[*out_num + *in_num].iov_base
|
2009-05-11 17:11:46 +00:00
|
|
|
= check_pointer(desc[i].addr, desc[i].len);
|
2007-10-22 01:24:22 +00:00
|
|
|
/* If this is an input descriptor, increment that count. */
|
2009-05-11 17:11:46 +00:00
|
|
|
if (desc[i].flags & VRING_DESC_F_WRITE)
|
2007-10-22 01:24:22 +00:00
|
|
|
(*in_num)++;
|
|
|
|
else {
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* If it's an output descriptor, they're all supposed
|
|
|
|
* to come before any input descriptors.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
if (*in_num)
|
|
|
|
errx(1, "Descriptor has out after in");
|
|
|
|
(*out_num)++;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If we've got too many, that implies a descriptor loop. */
|
2009-05-11 17:11:46 +00:00
|
|
|
if (*out_num + *in_num > max)
|
2007-10-22 01:24:22 +00:00
|
|
|
errx(1, "Looped descriptor");
|
2009-05-11 17:11:46 +00:00
|
|
|
} while ((i = next_desc(desc, i, max)) != max);
|
2007-07-26 17:41:03 +00:00
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
return head;
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
2009-07-30 22:03:45 +00:00
|
|
|
* After we've used one of their buffers, we tell the Guest about it. Sometime
|
|
|
|
* later we'll want to send them an interrupt using trigger_irq(); note that
|
|
|
|
* wait_for_vq_desc() does that for us if it has to wait.
|
2009-07-30 22:03:45 +00:00
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
static void add_used(struct virtqueue *vq, unsigned int head, int len)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
2007-10-22 01:24:22 +00:00
|
|
|
struct vring_used_elem *used;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* The virtqueue contains a ring of used buffers. Get a pointer to the
|
|
|
|
* next entry in that used ring.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
used = &vq->vring.used->ring[vq->vring.used->idx % vq->vring.num];
|
|
|
|
used->id = head;
|
|
|
|
used->len = len;
|
|
|
|
/* Make sure buffer is written before we update index. */
|
|
|
|
wmb();
|
|
|
|
vq->vring.used->idx++;
|
2009-06-13 04:27:11 +00:00
|
|
|
vq->pending_used++;
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* And here's the combo meal deal. Supersize me! */
|
2009-06-13 04:26:59 +00:00
|
|
|
static void add_used_and_trigger(struct virtqueue *vq, unsigned head, int len)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
2007-10-22 01:24:22 +00:00
|
|
|
add_used(vq, head, len);
|
2009-06-13 04:26:59 +00:00
|
|
|
trigger_irq(vq);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2007-10-25 05:02:50 +00:00
|
|
|
/*
|
|
|
|
* The Console
|
|
|
|
*
|
2009-07-30 22:03:45 +00:00
|
|
|
* We associate some data with the console for our exit hack.
|
|
|
|
*/
|
2009-07-30 22:03:46 +00:00
|
|
|
struct console_abort {
|
2007-07-26 17:41:03 +00:00
|
|
|
/* How many times have they hit ^C? */
|
2007-07-19 08:49:29 +00:00
|
|
|
int count;
|
2007-07-26 17:41:03 +00:00
|
|
|
/* When did they start? */
|
2007-07-19 08:49:29 +00:00
|
|
|
struct timeval start;
|
|
|
|
};
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* This is the routine which handles console input (ie. stdin). */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static void console_input(struct virtqueue *vq)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
int len;
|
2007-10-22 01:24:22 +00:00
|
|
|
unsigned int head, in_num, out_num;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct console_abort *abort = vq->dev->priv;
|
|
|
|
struct iovec iov[vq->vring.num];
|
2007-10-22 01:24:23 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* Make sure there's a descriptor available. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
head = wait_for_vq_desc(vq, iov, &out_num, &in_num);
|
2007-10-22 01:24:23 +00:00
|
|
|
if (out_num)
|
2007-10-22 01:24:22 +00:00
|
|
|
errx(1, "Output buffers in console in queue?");
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* Read into it. This is where we usually wait. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
len = readv(STDIN_FILENO, iov, in_num);
|
2007-07-19 08:49:29 +00:00
|
|
|
if (len <= 0) {
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* Ran out of input? */
|
2007-07-19 08:49:29 +00:00
|
|
|
warnx("Failed to get console input, ignoring console.");
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* For simplicity, dying threads kill the whole Launcher. So
|
|
|
|
* just nap here.
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
for (;;)
|
|
|
|
pause();
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* Tell the Guest we used a buffer. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
add_used_and_trigger(vq, head, len);
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Three ^C within one second? Exit.
|
2007-07-26 17:41:03 +00:00
|
|
|
*
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
* This is such a hack, but works surprisingly well. Each ^C has to
|
|
|
|
* be in a buffer by itself, so they can't be too fast. But we check
|
|
|
|
* that we get three within about a second, so they can't be too
|
2009-07-30 22:03:45 +00:00
|
|
|
* slow.
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
if (len != 1 || ((char *)iov[0].iov_base)[0] != 3) {
|
2007-07-19 08:49:29 +00:00
|
|
|
abort->count = 0;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
return;
|
|
|
|
}
|
2007-07-19 08:49:29 +00:00
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
abort->count++;
|
|
|
|
if (abort->count == 1)
|
|
|
|
gettimeofday(&abort->start, NULL);
|
|
|
|
else if (abort->count == 3) {
|
|
|
|
struct timeval now;
|
|
|
|
gettimeofday(&now, NULL);
|
|
|
|
/* Kill all Launcher processes with SIGINT, like normal ^C */
|
|
|
|
if (now.tv_sec <= abort->start.tv_sec+1)
|
|
|
|
kill(0, SIGINT);
|
|
|
|
abort->count = 0;
|
|
|
|
}
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* This is the routine which handles console output (ie. stdout). */
|
|
|
|
static void console_output(struct virtqueue *vq)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
2007-10-22 01:24:22 +00:00
|
|
|
unsigned int head, out, in;
|
|
|
|
struct iovec iov[vq->vring.num];
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* We usually wait in here, for the Guest to give us something. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
head = wait_for_vq_desc(vq, iov, &out, &in);
|
|
|
|
if (in)
|
|
|
|
errx(1, "Input buffers in console output queue?");
|
2009-07-30 22:03:45 +00:00
|
|
|
|
|
|
|
/* writev can return a partial write, so we loop here. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
while (!iov_empty(iov, out)) {
|
|
|
|
int len = writev(STDOUT_FILENO, iov, out);
|
2011-06-26 16:36:46 +00:00
|
|
|
if (len <= 0) {
|
|
|
|
warn("Write to stdout gave %i (%d)", len, errno);
|
|
|
|
break;
|
|
|
|
}
|
2012-10-16 13:26:13 +00:00
|
|
|
iov_consume(iov, out, NULL, len);
|
2007-10-22 01:24:22 +00:00
|
|
|
}
|
2009-07-30 22:03:45 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* We're finished with that buffer: if we're going to sleep,
|
|
|
|
* wait_for_vq_desc() will prod the Guest with an interrupt.
|
|
|
|
*/
|
2009-06-13 04:27:11 +00:00
|
|
|
add_used(vq, head, 0);
|
2008-07-29 14:58:35 +00:00
|
|
|
}
|
|
|
|
|
2007-10-25 05:02:50 +00:00
|
|
|
/*
|
|
|
|
* The Network
|
|
|
|
*
|
|
|
|
* Handling output for network is also simple: we get all the output buffers
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
* and write them to /dev/net/tun.
|
2008-03-28 16:05:53 +00:00
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct net_info {
|
|
|
|
int tunfd;
|
|
|
|
};
|
|
|
|
|
|
|
|
static void net_output(struct virtqueue *vq)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct net_info *net_info = vq->dev->priv;
|
|
|
|
unsigned int head, out, in;
|
2007-10-22 01:24:22 +00:00
|
|
|
struct iovec iov[vq->vring.num];
|
2008-07-29 14:58:35 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* We usually wait in here for the Guest to give us a packet. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
head = wait_for_vq_desc(vq, iov, &out, &in);
|
|
|
|
if (in)
|
|
|
|
errx(1, "Input buffers in net output queue?");
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Send the whole thing through to /dev/net/tun. It expects the exact
|
|
|
|
* same format: what a coincidence!
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
if (writev(net_info->tunfd, iov, out) < 0)
|
2011-06-26 16:36:46 +00:00
|
|
|
warnx("Write to tun failed (%d)?", errno);
|
2009-07-30 22:03:45 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Done with that one; wait_for_vq_desc() will send the interrupt if
|
|
|
|
* all packets are processed.
|
|
|
|
*/
|
2009-06-13 04:27:11 +00:00
|
|
|
add_used(vq, head, 0);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Handling network input is a bit trickier, because I've tried to optimize it.
|
|
|
|
*
|
|
|
|
* First we have a helper routine which tells is if from this file descriptor
|
|
|
|
* (ie. the /dev/net/tun device) will block:
|
|
|
|
*/
|
2009-06-13 04:27:12 +00:00
|
|
|
static bool will_block(int fd)
|
|
|
|
{
|
|
|
|
fd_set fdset;
|
|
|
|
struct timeval zero = { 0, 0 };
|
|
|
|
FD_ZERO(&fdset);
|
|
|
|
FD_SET(fd, &fdset);
|
|
|
|
return select(fd+1, &fdset, NULL, NULL, &zero) != 1;
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This handles packets coming in from the tun device to our Guest. Like all
|
|
|
|
* service routines, it gets called again as soon as it returns, so you don't
|
|
|
|
* see a while(1) loop here.
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static void net_input(struct virtqueue *vq)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
int len;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
unsigned int head, out, in;
|
|
|
|
struct iovec iov[vq->vring.num];
|
|
|
|
struct net_info *net_info = vq->dev->priv;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Get a descriptor to write an incoming packet into. This will also
|
|
|
|
* send an interrupt if they're out of descriptors.
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
head = wait_for_vq_desc(vq, iov, &out, &in);
|
|
|
|
if (out)
|
|
|
|
errx(1, "Output buffers in net input queue?");
|
2009-06-13 04:27:12 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* If it looks like we'll block reading from the tun device, send them
|
|
|
|
* an interrupt.
|
|
|
|
*/
|
2009-06-13 04:27:12 +00:00
|
|
|
if (vq->pending_used && will_block(net_info->tunfd))
|
|
|
|
trigger_irq(vq);
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Read in the packet. This is where we normally wait (when there's no
|
|
|
|
* incoming network traffic).
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
len = readv(net_info->tunfd, iov, in);
|
2007-07-19 08:49:29 +00:00
|
|
|
if (len <= 0)
|
2011-06-26 16:36:46 +00:00
|
|
|
warn("Failed to read from tun (%d).", errno);
|
2009-07-30 22:03:45 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Mark that packet buffer as used, but don't interrupt here. We want
|
|
|
|
* to wait until we've done as much work as we can.
|
|
|
|
*/
|
2009-06-13 04:27:12 +00:00
|
|
|
add_used(vq, head, len);
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
}
|
2009-07-30 22:03:45 +00:00
|
|
|
/*:*/
|
2007-07-26 17:41:03 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* This is the helper to create threads: run the service routine in a loop. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static int do_thread(void *_vq)
|
|
|
|
{
|
|
|
|
struct virtqueue *vq = _vq;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
for (;;)
|
|
|
|
vq->service(vq);
|
|
|
|
return 0;
|
|
|
|
}
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* When a child dies, we kill our entire process group with SIGTERM. This
|
|
|
|
* also has the side effect that the shell restores the console for us!
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static void kill_launcher(int signal)
|
|
|
|
{
|
|
|
|
kill(0, SIGTERM);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static void reset_device(struct device *dev)
|
2007-10-22 01:24:23 +00:00
|
|
|
{
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct virtqueue *vq;
|
|
|
|
|
|
|
|
verbose("Resetting device %s\n", dev->name);
|
|
|
|
|
|
|
|
/* Clear any features they've acked. */
|
|
|
|
memset(get_feature_bits(dev) + dev->feature_len, 0, dev->feature_len);
|
|
|
|
|
|
|
|
/* We're going to be explicitly killing threads, so ignore them. */
|
|
|
|
signal(SIGCHLD, SIG_IGN);
|
|
|
|
|
|
|
|
/* Zero out the virtqueues, get rid of their threads */
|
|
|
|
for (vq = dev->vq; vq; vq = vq->next) {
|
|
|
|
if (vq->thread != (pid_t)-1) {
|
|
|
|
kill(vq->thread, SIGTERM);
|
|
|
|
waitpid(vq->thread, NULL, 0);
|
|
|
|
vq->thread = (pid_t)-1;
|
|
|
|
}
|
|
|
|
memset(vq->vring.desc, 0,
|
|
|
|
vring_size(vq->config.num, LGUEST_VRING_ALIGN));
|
|
|
|
lg_last_avail(vq) = 0;
|
|
|
|
}
|
|
|
|
dev->running = false;
|
|
|
|
|
|
|
|
/* Now we care if threads die. */
|
|
|
|
signal(SIGCHLD, (void *)kill_launcher);
|
2007-10-22 01:24:23 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:216
|
|
|
|
* This actually creates the thread which services the virtqueue for a device.
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static void create_thread(struct virtqueue *vq)
|
2008-07-29 14:58:35 +00:00
|
|
|
{
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
2009-07-30 22:03:45 +00:00
|
|
|
* Create stack for thread. Since the stack grows upwards, we point
|
|
|
|
* the stack pointer to the end of this region.
|
2009-07-30 22:03:45 +00:00
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
char *stack = malloc(32768);
|
|
|
|
unsigned long args[] = { LHREQ_EVENTFD,
|
|
|
|
vq->config.pfn*getpagesize(), 0 };
|
|
|
|
|
|
|
|
/* Create a zero-initialized eventfd. */
|
|
|
|
vq->eventfd = eventfd(0, 0);
|
|
|
|
if (vq->eventfd < 0)
|
|
|
|
err(1, "Creating eventfd");
|
|
|
|
args[2] = vq->eventfd;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Attach an eventfd to this virtqueue: it will go off when the Guest
|
|
|
|
* does an LHCALL_NOTIFY for this vq.
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
if (write(lguest_fd, &args, sizeof(args)) != 0)
|
|
|
|
err(1, "Attaching eventfd");
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* CLONE_VM: because it has to access the Guest memory, and SIGCHLD so
|
|
|
|
* we get a signal if it dies.
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
vq->thread = clone(do_thread, stack + 32768, CLONE_VM | SIGCHLD, vq);
|
|
|
|
if (vq->thread == (pid_t)-1)
|
|
|
|
err(1, "Creating clone");
|
2009-07-30 22:03:45 +00:00
|
|
|
|
|
|
|
/* We close our local copy now the child has it. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
close(vq->eventfd);
|
2008-07-29 14:58:35 +00:00
|
|
|
}
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static void start_device(struct device *dev)
|
2008-02-05 04:50:03 +00:00
|
|
|
{
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
unsigned int i;
|
2008-02-05 04:50:03 +00:00
|
|
|
struct virtqueue *vq;
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
verbose("Device %s OK: offered", dev->name);
|
|
|
|
for (i = 0; i < dev->feature_len; i++)
|
|
|
|
verbose(" %02x", get_feature_bits(dev)[i]);
|
|
|
|
verbose(", accepted");
|
|
|
|
for (i = 0; i < dev->feature_len; i++)
|
|
|
|
verbose(" %02x", get_feature_bits(dev)
|
|
|
|
[dev->feature_len+i]);
|
|
|
|
|
|
|
|
for (vq = dev->vq; vq; vq = vq->next) {
|
|
|
|
if (vq->service)
|
|
|
|
create_thread(vq);
|
|
|
|
}
|
|
|
|
dev->running = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void cleanup_devices(void)
|
|
|
|
{
|
|
|
|
struct device *dev;
|
|
|
|
|
|
|
|
for (dev = devices.dev; dev; dev = dev->next)
|
|
|
|
reset_device(dev);
|
2008-02-05 04:50:03 +00:00
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* If we saved off the original terminal settings, restore them now. */
|
|
|
|
if (orig_term.c_lflag & (ISIG|ICANON|ECHO))
|
|
|
|
tcsetattr(STDIN_FILENO, TCSANOW, &orig_term);
|
|
|
|
}
|
2008-02-05 04:50:03 +00:00
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* When the Guest tells us they updated the status field, we handle it. */
|
|
|
|
static void update_device_status(struct device *dev)
|
|
|
|
{
|
|
|
|
/* A zero status is a reset, otherwise it's a set of flags. */
|
|
|
|
if (dev->desc->status == 0)
|
|
|
|
reset_device(dev);
|
|
|
|
else if (dev->desc->status & VIRTIO_CONFIG_S_FAILED) {
|
2008-05-03 02:50:53 +00:00
|
|
|
warnx("Device %s configuration FAILED", dev->name);
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
if (dev->running)
|
|
|
|
reset_device(dev);
|
2011-07-22 05:09:49 +00:00
|
|
|
} else {
|
|
|
|
if (dev->running)
|
|
|
|
err(1, "Device %s features finalized twice", dev->name);
|
|
|
|
start_device(dev);
|
2008-02-05 04:50:03 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:215
|
|
|
|
* This is the generic routine we call when the Guest uses LHCALL_NOTIFY. In
|
|
|
|
* particular, it's used to notify us of device status changes during boot.
|
|
|
|
*/
|
2009-06-13 04:26:59 +00:00
|
|
|
static void handle_output(unsigned long addr)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
struct device *i;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* Check each device. */
|
2007-10-22 01:24:22 +00:00
|
|
|
for (i = devices.dev; i; i = i->next) {
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct virtqueue *vq;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Notifications to device descriptors mean they updated the
|
|
|
|
* device status.
|
|
|
|
*/
|
2008-02-05 04:50:03 +00:00
|
|
|
if (from_guest_phys(addr) == i->desc) {
|
2008-05-03 02:50:53 +00:00
|
|
|
update_device_status(i);
|
2008-02-05 04:50:03 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2011-07-22 05:09:49 +00:00
|
|
|
/* Devices should not be used before features are finalized. */
|
2007-10-22 01:24:22 +00:00
|
|
|
for (vq = i->vq; vq; vq = vq->next) {
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
if (addr != vq->config.pfn*getpagesize())
|
2008-02-05 04:50:03 +00:00
|
|
|
continue;
|
2011-07-22 05:09:49 +00:00
|
|
|
errx(1, "Notification on %s before setup!", i->name);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
}
|
2007-07-26 17:41:03 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Early console write is done using notify on a nul-terminated string
|
|
|
|
* in Guest memory. It's also great for hacking debugging messages
|
|
|
|
* into a Guest.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
if (addr >= guest_limit)
|
|
|
|
errx(1, "Bad NOTIFY %#lx", addr);
|
|
|
|
|
|
|
|
write(STDOUT_FILENO, from_guest_phys(addr),
|
|
|
|
strnlen(from_guest_phys(addr), guest_limit - addr));
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/*L:217
|
|
|
|
* We do PCI. This is mainly done to let us test the kernel virtio PCI
|
|
|
|
* code.
|
|
|
|
*/
|
|
|
|
|
2015-02-11 04:45:12 +00:00
|
|
|
/* Linux expects a PCI host bridge: ours is a dummy, and first on the bus. */
|
|
|
|
static struct device pci_host_bridge;
|
|
|
|
|
|
|
|
static void init_pci_host_bridge(void)
|
|
|
|
{
|
|
|
|
pci_host_bridge.name = "PCI Host Bridge";
|
|
|
|
pci_host_bridge.config.class = 0x06; /* bridge */
|
|
|
|
pci_host_bridge.config.subclass = 0; /* host bridge */
|
|
|
|
devices.pci[0] = &pci_host_bridge;
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* The IO ports used to read the PCI config space. */
|
|
|
|
#define PCI_CONFIG_ADDR 0xCF8
|
|
|
|
#define PCI_CONFIG_DATA 0xCFC
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Not really portable, but does help readability: this is what the Guest
|
|
|
|
* writes to the PCI_CONFIG_ADDR IO port.
|
|
|
|
*/
|
|
|
|
union pci_config_addr {
|
|
|
|
struct {
|
|
|
|
unsigned mbz: 2;
|
|
|
|
unsigned offset: 6;
|
|
|
|
unsigned funcnum: 3;
|
|
|
|
unsigned devnum: 5;
|
|
|
|
unsigned busnum: 8;
|
|
|
|
unsigned reserved: 7;
|
|
|
|
unsigned enabled : 1;
|
|
|
|
} bits;
|
|
|
|
u32 val;
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We cache what they wrote to the address port, so we know what they're
|
|
|
|
* talking about when they access the data port.
|
|
|
|
*/
|
|
|
|
static union pci_config_addr pci_config_addr;
|
|
|
|
|
|
|
|
static struct device *find_pci_device(unsigned int index)
|
|
|
|
{
|
|
|
|
return devices.pci[index];
|
|
|
|
}
|
|
|
|
|
|
|
|
/* PCI can do 1, 2 and 4 byte reads; we handle that here. */
|
|
|
|
static void ioread(u16 off, u32 v, u32 mask, u32 *val)
|
|
|
|
{
|
|
|
|
assert(off < 4);
|
|
|
|
assert(mask == 0xFF || mask == 0xFFFF || mask == 0xFFFFFFFF);
|
|
|
|
*val = (v >> (off * 8)) & mask;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* PCI can do 1, 2 and 4 byte writes; we handle that here. */
|
|
|
|
static void iowrite(u16 off, u32 v, u32 mask, u32 *dst)
|
|
|
|
{
|
|
|
|
assert(off < 4);
|
|
|
|
assert(mask == 0xFF || mask == 0xFFFF || mask == 0xFFFFFFFF);
|
|
|
|
*dst &= ~(mask << (off * 8));
|
|
|
|
*dst |= (v & mask) << (off * 8);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Where PCI_CONFIG_DATA accesses depends on the previous write to
|
|
|
|
* PCI_CONFIG_ADDR.
|
|
|
|
*/
|
|
|
|
static struct device *dev_and_reg(u32 *reg)
|
|
|
|
{
|
|
|
|
if (!pci_config_addr.bits.enabled)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
if (pci_config_addr.bits.funcnum != 0)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
if (pci_config_addr.bits.busnum != 0)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
if (pci_config_addr.bits.offset * 4 >= sizeof(struct pci_config))
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
*reg = pci_config_addr.bits.offset;
|
|
|
|
return find_pci_device(pci_config_addr.bits.devnum);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Is this accessing the PCI config address port?. */
|
|
|
|
static bool is_pci_addr_port(u16 port)
|
|
|
|
{
|
|
|
|
return port >= PCI_CONFIG_ADDR && port < PCI_CONFIG_ADDR + 4;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool pci_addr_iowrite(u16 port, u32 mask, u32 val)
|
|
|
|
{
|
|
|
|
iowrite(port - PCI_CONFIG_ADDR, val, mask,
|
|
|
|
&pci_config_addr.val);
|
|
|
|
verbose("PCI%s: %#x/%x: bus %u dev %u func %u reg %u\n",
|
|
|
|
pci_config_addr.bits.enabled ? "" : " DISABLED",
|
|
|
|
val, mask,
|
|
|
|
pci_config_addr.bits.busnum,
|
|
|
|
pci_config_addr.bits.devnum,
|
|
|
|
pci_config_addr.bits.funcnum,
|
|
|
|
pci_config_addr.bits.offset);
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pci_addr_ioread(u16 port, u32 mask, u32 *val)
|
|
|
|
{
|
|
|
|
ioread(port - PCI_CONFIG_ADDR, pci_config_addr.val, mask, val);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Is this accessing the PCI config data port?. */
|
|
|
|
static bool is_pci_data_port(u16 port)
|
|
|
|
{
|
|
|
|
return port >= PCI_CONFIG_DATA && port < PCI_CONFIG_DATA + 4;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool pci_data_iowrite(u16 port, u32 mask, u32 val)
|
|
|
|
{
|
|
|
|
u32 reg, portoff;
|
|
|
|
struct device *d = dev_and_reg(®);
|
|
|
|
|
|
|
|
/* Complain if they don't belong to a device. */
|
|
|
|
if (!d)
|
|
|
|
return false;
|
|
|
|
|
|
|
|
/* They can do 1 byte writes, etc. */
|
|
|
|
portoff = port - PCI_CONFIG_DATA;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* PCI uses a weird way to determine the BAR size: the OS
|
|
|
|
* writes all 1's, and sees which ones stick.
|
|
|
|
*/
|
|
|
|
if (&d->config_words[reg] == &d->config.bar[0]) {
|
|
|
|
int i;
|
|
|
|
|
|
|
|
iowrite(portoff, val, mask, &d->config.bar[0]);
|
|
|
|
for (i = 0; (1 << i) < d->mmio_size; i++)
|
|
|
|
d->config.bar[0] &= ~(1 << i);
|
|
|
|
return true;
|
|
|
|
} else if ((&d->config_words[reg] > &d->config.bar[0]
|
|
|
|
&& &d->config_words[reg] <= &d->config.bar[6])
|
|
|
|
|| &d->config_words[reg] == &d->config.expansion_rom_addr) {
|
|
|
|
/* Allow writing to any other BAR, or expansion ROM */
|
|
|
|
iowrite(portoff, val, mask, &d->config_words[reg]);
|
|
|
|
return true;
|
|
|
|
/* We let them overide latency timer and cacheline size */
|
|
|
|
} else if (&d->config_words[reg] == (void *)&d->config.cacheline_size) {
|
|
|
|
/* Only let them change the first two fields. */
|
|
|
|
if (mask == 0xFFFFFFFF)
|
|
|
|
mask = 0xFFFF;
|
|
|
|
iowrite(portoff, val, mask, &d->config_words[reg]);
|
|
|
|
return true;
|
|
|
|
} else if (&d->config_words[reg] == (void *)&d->config.command
|
|
|
|
&& mask == 0xFFFF) {
|
|
|
|
/* Ignore command writes. */
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Complain about other writes. */
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pci_data_ioread(u16 port, u32 mask, u32 *val)
|
|
|
|
{
|
|
|
|
u32 reg;
|
|
|
|
struct device *d = dev_and_reg(®);
|
|
|
|
|
|
|
|
if (!d)
|
|
|
|
return;
|
|
|
|
ioread(port - PCI_CONFIG_DATA, d->config_words[reg], mask, val);
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:10 +00:00
|
|
|
/*L:216
|
|
|
|
* This is where we emulate a handful of Guest instructions. It's ugly
|
|
|
|
* and we used to do it in the kernel but it grew over time.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We use the ptrace syscall's pt_regs struct to talk about registers
|
|
|
|
* to lguest: these macros convert the names to the offsets.
|
|
|
|
*/
|
|
|
|
#define getreg(name) getreg_off(offsetof(struct user_regs_struct, name))
|
|
|
|
#define setreg(name, val) \
|
|
|
|
setreg_off(offsetof(struct user_regs_struct, name), (val))
|
|
|
|
|
|
|
|
static u32 getreg_off(size_t offset)
|
|
|
|
{
|
|
|
|
u32 r;
|
|
|
|
unsigned long args[] = { LHREQ_GETREG, offset };
|
|
|
|
|
|
|
|
if (pwrite(lguest_fd, args, sizeof(args), cpu_id) < 0)
|
|
|
|
err(1, "Getting register %u", offset);
|
|
|
|
if (pread(lguest_fd, &r, sizeof(r), cpu_id) != sizeof(r))
|
|
|
|
err(1, "Reading register %u", offset);
|
|
|
|
|
|
|
|
return r;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void setreg_off(size_t offset, u32 val)
|
|
|
|
{
|
|
|
|
unsigned long args[] = { LHREQ_SETREG, offset, val };
|
|
|
|
|
|
|
|
if (pwrite(lguest_fd, args, sizeof(args), cpu_id) < 0)
|
|
|
|
err(1, "Setting register %u", offset);
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* Get register by instruction encoding */
|
|
|
|
static u32 getreg_num(unsigned regnum, u32 mask)
|
|
|
|
{
|
|
|
|
/* 8 bit ops use regnums 4-7 for high parts of word */
|
|
|
|
if (mask == 0xFF && (regnum & 0x4))
|
|
|
|
return getreg_num(regnum & 0x3, 0xFFFF) >> 8;
|
|
|
|
|
|
|
|
switch (regnum) {
|
|
|
|
case 0: return getreg(eax) & mask;
|
|
|
|
case 1: return getreg(ecx) & mask;
|
|
|
|
case 2: return getreg(edx) & mask;
|
|
|
|
case 3: return getreg(ebx) & mask;
|
|
|
|
case 4: return getreg(esp) & mask;
|
|
|
|
case 5: return getreg(ebp) & mask;
|
|
|
|
case 6: return getreg(esi) & mask;
|
|
|
|
case 7: return getreg(edi) & mask;
|
|
|
|
}
|
|
|
|
abort();
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Set register by instruction encoding */
|
|
|
|
static void setreg_num(unsigned regnum, u32 val, u32 mask)
|
|
|
|
{
|
|
|
|
/* Don't try to set bits out of range */
|
|
|
|
assert(~(val & ~mask));
|
|
|
|
|
|
|
|
/* 8 bit ops use regnums 4-7 for high parts of word */
|
|
|
|
if (mask == 0xFF && (regnum & 0x4)) {
|
|
|
|
/* Construct the 16 bits we want. */
|
|
|
|
val = (val << 8) | getreg_num(regnum & 0x3, 0xFF);
|
|
|
|
setreg_num(regnum & 0x3, val, 0xFFFF);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (regnum) {
|
|
|
|
case 0: setreg(eax, val | (getreg(eax) & ~mask)); return;
|
|
|
|
case 1: setreg(ecx, val | (getreg(ecx) & ~mask)); return;
|
|
|
|
case 2: setreg(edx, val | (getreg(edx) & ~mask)); return;
|
|
|
|
case 3: setreg(ebx, val | (getreg(ebx) & ~mask)); return;
|
|
|
|
case 4: setreg(esp, val | (getreg(esp) & ~mask)); return;
|
|
|
|
case 5: setreg(ebp, val | (getreg(ebp) & ~mask)); return;
|
|
|
|
case 6: setreg(esi, val | (getreg(esi) & ~mask)); return;
|
|
|
|
case 7: setreg(edi, val | (getreg(edi) & ~mask)); return;
|
|
|
|
}
|
|
|
|
abort();
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Get bytes of displacement appended to instruction, from r/m encoding */
|
|
|
|
static u32 insn_displacement_len(u8 mod_reg_rm)
|
|
|
|
{
|
|
|
|
/* Switch on the mod bits */
|
|
|
|
switch (mod_reg_rm >> 6) {
|
|
|
|
case 0:
|
|
|
|
/* If mod == 0, and r/m == 101, 16-bit displacement follows */
|
|
|
|
if ((mod_reg_rm & 0x7) == 0x5)
|
|
|
|
return 2;
|
|
|
|
/* Normally, mod == 0 means no literal displacement */
|
|
|
|
return 0;
|
|
|
|
case 1:
|
|
|
|
/* One byte displacement */
|
|
|
|
return 1;
|
|
|
|
case 2:
|
|
|
|
/* Four byte displacement */
|
|
|
|
return 4;
|
|
|
|
case 3:
|
|
|
|
/* Register mode */
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
abort();
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:10 +00:00
|
|
|
static void emulate_insn(const u8 insn[])
|
|
|
|
{
|
|
|
|
unsigned long args[] = { LHREQ_TRAP, 13 };
|
|
|
|
unsigned int insnlen = 0, in = 0, small_operand = 0, byte_access;
|
|
|
|
unsigned int eax, port, mask;
|
|
|
|
/*
|
2015-02-11 04:45:11 +00:00
|
|
|
* Default is to return all-ones on IO port reads, which traditionally
|
2015-02-11 04:45:10 +00:00
|
|
|
* means "there's nothing there".
|
|
|
|
*/
|
|
|
|
u32 val = 0xFFFFFFFF;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This must be the Guest kernel trying to do something, not userspace!
|
|
|
|
* The bottom two bits of the CS segment register are the privilege
|
|
|
|
* level.
|
|
|
|
*/
|
|
|
|
if ((getreg(xcs) & 3) != 0x1)
|
|
|
|
goto no_emulate;
|
|
|
|
|
|
|
|
/* Decoding x86 instructions is icky. */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Around 2.6.33, the kernel started using an emulation for the
|
|
|
|
* cmpxchg8b instruction in early boot on many configurations. This
|
|
|
|
* code isn't paravirtualized, and it tries to disable interrupts.
|
|
|
|
* Ignore it, which will Mostly Work.
|
|
|
|
*/
|
|
|
|
if (insn[insnlen] == 0xfa) {
|
|
|
|
/* "cli", or Clear Interrupt Enable instruction. Skip it. */
|
|
|
|
insnlen = 1;
|
|
|
|
goto skip_insn;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 0x66 is an "operand prefix". It means a 16, not 32 bit in/out.
|
|
|
|
*/
|
|
|
|
if (insn[insnlen] == 0x66) {
|
|
|
|
small_operand = 1;
|
|
|
|
/* The instruction is 1 byte so far, read the next byte. */
|
|
|
|
insnlen = 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If the lower bit isn't set, it's a single byte access */
|
|
|
|
byte_access = !(insn[insnlen] & 1);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Now we can ignore the lower bit and decode the 4 opcodes
|
|
|
|
* we need to emulate.
|
|
|
|
*/
|
|
|
|
switch (insn[insnlen] & 0xFE) {
|
|
|
|
case 0xE4: /* in <next byte>,%al */
|
|
|
|
port = insn[insnlen+1];
|
|
|
|
insnlen += 2;
|
|
|
|
in = 1;
|
|
|
|
break;
|
|
|
|
case 0xEC: /* in (%dx),%al */
|
|
|
|
port = getreg(edx) & 0xFFFF;
|
|
|
|
insnlen += 1;
|
|
|
|
in = 1;
|
|
|
|
break;
|
|
|
|
case 0xE6: /* out %al,<next byte> */
|
|
|
|
port = insn[insnlen+1];
|
|
|
|
insnlen += 2;
|
|
|
|
break;
|
|
|
|
case 0xEE: /* out %al,(%dx) */
|
|
|
|
port = getreg(edx) & 0xFFFF;
|
|
|
|
insnlen += 1;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
/* OK, we don't know what this is, can't emulate. */
|
|
|
|
goto no_emulate;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Set a mask of the 1, 2 or 4 bytes, depending on size of IO */
|
|
|
|
if (byte_access)
|
|
|
|
mask = 0xFF;
|
|
|
|
else if (small_operand)
|
|
|
|
mask = 0xFFFF;
|
|
|
|
else
|
|
|
|
mask = 0xFFFFFFFF;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If it was an "IN" instruction, they expect the result to be read
|
|
|
|
* into %eax, so we change %eax.
|
|
|
|
*/
|
|
|
|
eax = getreg(eax);
|
|
|
|
|
|
|
|
if (in) {
|
2015-02-11 04:45:11 +00:00
|
|
|
/* This is the PS/2 keyboard status; 1 means ready for output */
|
|
|
|
if (port == 0x64)
|
|
|
|
val = 1;
|
|
|
|
else if (is_pci_addr_port(port))
|
|
|
|
pci_addr_ioread(port, mask, &val);
|
|
|
|
else if (is_pci_data_port(port))
|
|
|
|
pci_data_ioread(port, mask, &val);
|
|
|
|
|
2015-02-11 04:45:10 +00:00
|
|
|
/* Clear the bits we're about to read */
|
|
|
|
eax &= ~mask;
|
|
|
|
/* Copy bits in from val. */
|
|
|
|
eax |= val & mask;
|
|
|
|
/* Now update the register. */
|
|
|
|
setreg(eax, eax);
|
2015-02-11 04:45:11 +00:00
|
|
|
} else {
|
|
|
|
if (is_pci_addr_port(port)) {
|
|
|
|
if (!pci_addr_iowrite(port, mask, eax))
|
|
|
|
goto bad_io;
|
|
|
|
} else if (is_pci_data_port(port)) {
|
|
|
|
if (!pci_data_iowrite(port, mask, eax))
|
|
|
|
goto bad_io;
|
|
|
|
}
|
|
|
|
/* There are many other ports, eg. CMOS clock, serial
|
|
|
|
* and parallel ports, so we ignore them all. */
|
2015-02-11 04:45:10 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
verbose("IO %s of %x to %u: %#08x\n",
|
|
|
|
in ? "IN" : "OUT", mask, port, eax);
|
|
|
|
skip_insn:
|
|
|
|
/* Finally, we've "done" the instruction, so move past it. */
|
|
|
|
setreg(eip, getreg(eip) + insnlen);
|
|
|
|
return;
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
bad_io:
|
|
|
|
warnx("Attempt to %s port %u (%#x mask)",
|
|
|
|
in ? "read from" : "write to", port, mask);
|
|
|
|
|
2015-02-11 04:45:10 +00:00
|
|
|
no_emulate:
|
|
|
|
/* Inject trap into Guest. */
|
|
|
|
if (write(lguest_fd, args, sizeof(args)) < 0)
|
|
|
|
err(1, "Reinjecting trap 13 for fault at %#x", getreg(eip));
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
static struct device *find_mmio_region(unsigned long paddr, u32 *off)
|
|
|
|
{
|
|
|
|
unsigned int i;
|
|
|
|
|
|
|
|
for (i = 1; i < MAX_PCI_DEVICES; i++) {
|
|
|
|
struct device *d = devices.pci[i];
|
|
|
|
|
|
|
|
if (!d)
|
|
|
|
continue;
|
|
|
|
if (paddr < d->mmio_addr)
|
|
|
|
continue;
|
|
|
|
if (paddr >= d->mmio_addr + d->mmio_size)
|
|
|
|
continue;
|
|
|
|
*off = paddr - d->mmio_addr;
|
|
|
|
return d;
|
|
|
|
}
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* FIXME: Use vq array. */
|
|
|
|
static struct virtqueue *vq_by_num(struct device *d, u32 num)
|
|
|
|
{
|
|
|
|
struct virtqueue *vq = d->vq;
|
|
|
|
|
|
|
|
while (num-- && vq)
|
|
|
|
vq = vq->next;
|
|
|
|
|
|
|
|
return vq;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void save_vq_config(const struct virtio_pci_common_cfg *cfg,
|
|
|
|
struct virtqueue *vq)
|
|
|
|
{
|
|
|
|
vq->pci_config = *cfg;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void restore_vq_config(struct virtio_pci_common_cfg *cfg,
|
|
|
|
struct virtqueue *vq)
|
|
|
|
{
|
|
|
|
/* Only restore the per-vq part */
|
|
|
|
size_t off = offsetof(struct virtio_pci_common_cfg, queue_size);
|
|
|
|
|
|
|
|
memcpy((void *)cfg + off, (void *)&vq->pci_config + off,
|
|
|
|
sizeof(*cfg) - off);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* When they enable the virtqueue, we check that their setup is valid.
|
|
|
|
*/
|
|
|
|
static void enable_virtqueue(struct device *d, struct virtqueue *vq)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* Create stack for thread. Since the stack grows upwards, we point
|
|
|
|
* the stack pointer to the end of this region.
|
|
|
|
*/
|
|
|
|
char *stack = malloc(32768);
|
|
|
|
|
|
|
|
/* Because lguest is 32 bit, all the descriptor high bits must be 0 */
|
|
|
|
if (vq->pci_config.queue_desc_hi
|
|
|
|
|| vq->pci_config.queue_avail_hi
|
|
|
|
|| vq->pci_config.queue_used_hi)
|
|
|
|
errx(1, "%s: invalid 64-bit queue address", d->name);
|
|
|
|
|
|
|
|
/* Initialize the virtqueue and check they're all in range. */
|
|
|
|
vq->vring.num = vq->pci_config.queue_size;
|
|
|
|
vq->vring.desc = check_pointer(vq->pci_config.queue_desc_lo,
|
|
|
|
sizeof(*vq->vring.desc) * vq->vring.num);
|
|
|
|
vq->vring.avail = check_pointer(vq->pci_config.queue_avail_lo,
|
|
|
|
sizeof(*vq->vring.avail)
|
|
|
|
+ (sizeof(vq->vring.avail->ring[0])
|
|
|
|
* vq->vring.num));
|
|
|
|
vq->vring.used = check_pointer(vq->pci_config.queue_used_lo,
|
|
|
|
sizeof(*vq->vring.used)
|
|
|
|
+ (sizeof(vq->vring.used->ring[0])
|
|
|
|
* vq->vring.num));
|
|
|
|
|
|
|
|
|
|
|
|
/* Create a zero-initialized eventfd. */
|
|
|
|
vq->eventfd = eventfd(0, 0);
|
|
|
|
if (vq->eventfd < 0)
|
|
|
|
err(1, "Creating eventfd");
|
|
|
|
|
|
|
|
/*
|
|
|
|
* CLONE_VM: because it has to access the Guest memory, and SIGCHLD so
|
|
|
|
* we get a signal if it dies.
|
|
|
|
*/
|
|
|
|
vq->thread = clone(do_thread, stack + 32768, CLONE_VM | SIGCHLD, vq);
|
|
|
|
if (vq->thread == (pid_t)-1)
|
|
|
|
err(1, "Creating clone");
|
|
|
|
}
|
|
|
|
|
|
|
|
static void reset_pci_device(struct device *dev)
|
|
|
|
{
|
|
|
|
/* FIXME */
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
static void emulate_mmio_write(struct device *d, u32 off, u32 val, u32 mask)
|
|
|
|
{
|
2015-02-11 04:45:11 +00:00
|
|
|
struct virtqueue *vq;
|
|
|
|
|
|
|
|
switch (off) {
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.device_feature_select):
|
|
|
|
if (val == 0)
|
|
|
|
d->mmio->cfg.device_feature = d->features;
|
|
|
|
else if (val == 1)
|
|
|
|
d->mmio->cfg.device_feature = (d->features >> 32);
|
|
|
|
else
|
|
|
|
d->mmio->cfg.device_feature = 0;
|
|
|
|
goto write_through32;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.guest_feature_select):
|
|
|
|
if (val > 1)
|
|
|
|
errx(1, "%s: Unexpected driver select %u",
|
|
|
|
d->name, val);
|
|
|
|
goto write_through32;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.guest_feature):
|
|
|
|
if (d->mmio->cfg.guest_feature_select == 0) {
|
|
|
|
d->features_accepted &= ~((u64)0xFFFFFFFF);
|
|
|
|
d->features_accepted |= val;
|
|
|
|
} else {
|
|
|
|
assert(d->mmio->cfg.guest_feature_select == 1);
|
|
|
|
d->features_accepted &= ((u64)0xFFFFFFFF << 32);
|
|
|
|
d->features_accepted |= ((u64)val) << 32;
|
|
|
|
}
|
|
|
|
if (d->features_accepted & ~d->features)
|
|
|
|
errx(1, "%s: over-accepted features %#llx of %#llx",
|
|
|
|
d->name, d->features_accepted, d->features);
|
|
|
|
goto write_through32;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.device_status):
|
|
|
|
verbose("%s: device status -> %#x\n", d->name, val);
|
|
|
|
if (val == 0)
|
|
|
|
reset_pci_device(d);
|
|
|
|
goto write_through8;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_select):
|
|
|
|
vq = vq_by_num(d, val);
|
|
|
|
/* Out of range? Return size 0 */
|
|
|
|
if (!vq) {
|
|
|
|
d->mmio->cfg.queue_size = 0;
|
|
|
|
goto write_through16;
|
|
|
|
}
|
|
|
|
/* Save registers for old vq, if it was a valid vq */
|
|
|
|
if (d->mmio->cfg.queue_size)
|
|
|
|
save_vq_config(&d->mmio->cfg,
|
|
|
|
vq_by_num(d, d->mmio->cfg.queue_select));
|
|
|
|
/* Restore the registers for the queue they asked for */
|
|
|
|
restore_vq_config(&d->mmio->cfg, vq);
|
|
|
|
goto write_through16;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_size):
|
|
|
|
if (val & (val-1))
|
|
|
|
errx(1, "%s: invalid queue size %u\n", d->name, val);
|
|
|
|
if (d->mmio->cfg.queue_enable)
|
|
|
|
errx(1, "%s: changing queue size on live device",
|
|
|
|
d->name);
|
|
|
|
goto write_through16;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_msix_vector):
|
|
|
|
errx(1, "%s: attempt to set MSIX vector to %u",
|
|
|
|
d->name, val);
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_enable):
|
|
|
|
if (val != 1)
|
|
|
|
errx(1, "%s: setting queue_enable to %u", d->name, val);
|
|
|
|
d->mmio->cfg.queue_enable = val;
|
|
|
|
save_vq_config(&d->mmio->cfg,
|
|
|
|
vq_by_num(d, d->mmio->cfg.queue_select));
|
|
|
|
enable_virtqueue(d, vq_by_num(d, d->mmio->cfg.queue_select));
|
|
|
|
goto write_through16;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_notify_off):
|
|
|
|
errx(1, "%s: attempt to write to queue_notify_off", d->name);
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_desc_lo):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_desc_hi):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_avail_lo):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_avail_hi):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_used_lo):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.queue_used_hi):
|
|
|
|
if (d->mmio->cfg.queue_enable)
|
|
|
|
errx(1, "%s: changing queue on live device",
|
|
|
|
d->name);
|
|
|
|
goto write_through32;
|
|
|
|
case offsetof(struct virtio_pci_mmio, notify):
|
|
|
|
vq = vq_by_num(d, val);
|
|
|
|
if (!vq)
|
|
|
|
errx(1, "Invalid vq notification on %u", val);
|
|
|
|
/* Notify the process handling this vq by adding 1 to eventfd */
|
|
|
|
write(vq->eventfd, "\1\0\0\0\0\0\0\0", 8);
|
|
|
|
goto write_through16;
|
|
|
|
case offsetof(struct virtio_pci_mmio, isr):
|
|
|
|
errx(1, "%s: Unexpected write to isr", d->name);
|
|
|
|
default:
|
|
|
|
errx(1, "%s: Unexpected write to offset %u", d->name, off);
|
|
|
|
}
|
|
|
|
|
|
|
|
write_through32:
|
|
|
|
if (mask != 0xFFFFFFFF) {
|
|
|
|
errx(1, "%s: non-32-bit write to offset %u (%#x)",
|
|
|
|
d->name, off, getreg(eip));
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
memcpy((char *)d->mmio + off, &val, 4);
|
|
|
|
return;
|
|
|
|
|
|
|
|
write_through16:
|
|
|
|
if (mask != 0xFFFF)
|
|
|
|
errx(1, "%s: non-16-bit (%#x) write to offset %u (%#x)",
|
|
|
|
d->name, mask, off, getreg(eip));
|
|
|
|
memcpy((char *)d->mmio + off, &val, 2);
|
|
|
|
return;
|
|
|
|
|
|
|
|
write_through8:
|
|
|
|
if (mask != 0xFF)
|
|
|
|
errx(1, "%s: non-8-bit write to offset %u (%#x)",
|
|
|
|
d->name, off, getreg(eip));
|
|
|
|
memcpy((char *)d->mmio + off, &val, 1);
|
|
|
|
return;
|
2015-02-11 04:45:11 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static u32 emulate_mmio_read(struct device *d, u32 off, u32 mask)
|
|
|
|
{
|
2015-02-11 04:45:11 +00:00
|
|
|
u8 isr;
|
|
|
|
u32 val = 0;
|
|
|
|
|
|
|
|
switch (off) {
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.device_feature_select):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.device_feature):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.guest_feature_select):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.guest_feature):
|
|
|
|
goto read_through32;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.msix_config):
|
|
|
|
errx(1, "%s: read of msix_config", d->name);
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.num_queues):
|
|
|
|
goto read_through16;
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.device_status):
|
|
|
|
case offsetof(struct virtio_pci_mmio, cfg.config_generation):
|
|
|
|
goto read_through8;
|
|
|
|
case offsetof(struct virtio_pci_mmio, notify):
|
|
|
|
goto read_through16;
|
|
|
|
case offsetof(struct virtio_pci_mmio, isr):
|
|
|
|
if (mask != 0xFF)
|
|
|
|
errx(1, "%s: non-8-bit read from offset %u (%#x)",
|
|
|
|
d->name, off, getreg(eip));
|
|
|
|
/* Read resets the isr */
|
|
|
|
isr = d->mmio->isr;
|
|
|
|
d->mmio->isr = 0;
|
|
|
|
return isr;
|
|
|
|
case offsetof(struct virtio_pci_mmio, padding):
|
|
|
|
errx(1, "%s: read from padding (%#x)",
|
|
|
|
d->name, getreg(eip));
|
|
|
|
default:
|
|
|
|
/* Read from device config space, beware unaligned overflow */
|
|
|
|
if (off > d->mmio_size - 4)
|
|
|
|
errx(1, "%s: read past end (%#x)",
|
|
|
|
d->name, getreg(eip));
|
|
|
|
if (mask == 0xFFFFFFFF)
|
|
|
|
goto read_through32;
|
|
|
|
else if (mask == 0xFFFF)
|
|
|
|
goto read_through16;
|
|
|
|
else
|
|
|
|
goto read_through8;
|
|
|
|
}
|
|
|
|
|
|
|
|
read_through32:
|
|
|
|
if (mask != 0xFFFFFFFF)
|
|
|
|
errx(1, "%s: non-32-bit read to offset %u (%#x)",
|
|
|
|
d->name, off, getreg(eip));
|
|
|
|
memcpy(&val, (char *)d->mmio + off, 4);
|
|
|
|
return val;
|
|
|
|
|
|
|
|
read_through16:
|
|
|
|
if (mask != 0xFFFF)
|
|
|
|
errx(1, "%s: non-16-bit read to offset %u (%#x)",
|
|
|
|
d->name, off, getreg(eip));
|
|
|
|
memcpy(&val, (char *)d->mmio + off, 2);
|
|
|
|
return val;
|
|
|
|
|
|
|
|
read_through8:
|
|
|
|
if (mask != 0xFF)
|
|
|
|
errx(1, "%s: non-8-bit read to offset %u (%#x)",
|
|
|
|
d->name, off, getreg(eip));
|
|
|
|
memcpy(&val, (char *)d->mmio + off, 1);
|
|
|
|
return val;
|
2015-02-11 04:45:11 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static void emulate_mmio(unsigned long paddr, const u8 *insn)
|
|
|
|
{
|
|
|
|
u32 val, off, mask = 0xFFFFFFFF, insnlen = 0;
|
|
|
|
struct device *d = find_mmio_region(paddr, &off);
|
|
|
|
unsigned long args[] = { LHREQ_TRAP, 14 };
|
|
|
|
|
|
|
|
if (!d) {
|
|
|
|
warnx("MMIO touching %#08lx (not a device)", paddr);
|
|
|
|
goto reinject;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Prefix makes it a 16 bit op */
|
|
|
|
if (insn[0] == 0x66) {
|
|
|
|
mask = 0xFFFF;
|
|
|
|
insnlen++;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* iowrite */
|
|
|
|
if (insn[insnlen] == 0x89) {
|
|
|
|
/* Next byte is r/m byte: bits 3-5 are register. */
|
|
|
|
val = getreg_num((insn[insnlen+1] >> 3) & 0x7, mask);
|
|
|
|
emulate_mmio_write(d, off, val, mask);
|
|
|
|
insnlen += 2 + insn_displacement_len(insn[insnlen+1]);
|
|
|
|
} else if (insn[insnlen] == 0x8b) { /* ioread */
|
|
|
|
/* Next byte is r/m byte: bits 3-5 are register. */
|
|
|
|
val = emulate_mmio_read(d, off, mask);
|
|
|
|
setreg_num((insn[insnlen+1] >> 3) & 0x7, val, mask);
|
|
|
|
insnlen += 2 + insn_displacement_len(insn[insnlen+1]);
|
|
|
|
} else if (insn[0] == 0x88) { /* 8-bit iowrite */
|
|
|
|
mask = 0xff;
|
|
|
|
/* Next byte is r/m byte: bits 3-5 are register. */
|
|
|
|
val = getreg_num((insn[1] >> 3) & 0x7, mask);
|
|
|
|
emulate_mmio_write(d, off, val, mask);
|
|
|
|
insnlen = 2 + insn_displacement_len(insn[1]);
|
|
|
|
} else if (insn[0] == 0x8a) { /* 8-bit ioread */
|
|
|
|
mask = 0xff;
|
|
|
|
val = emulate_mmio_read(d, off, mask);
|
|
|
|
setreg_num((insn[1] >> 3) & 0x7, val, mask);
|
|
|
|
insnlen = 2 + insn_displacement_len(insn[1]);
|
|
|
|
} else {
|
|
|
|
warnx("Unknown MMIO instruction touching %#08lx:"
|
|
|
|
" %02x %02x %02x %02x at %u",
|
|
|
|
paddr, insn[0], insn[1], insn[2], insn[3], getreg(eip));
|
|
|
|
reinject:
|
|
|
|
/* Inject trap into Guest. */
|
|
|
|
if (write(lguest_fd, args, sizeof(args)) < 0)
|
|
|
|
err(1, "Reinjecting trap 14 for fault at %#x",
|
|
|
|
getreg(eip));
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Finally, we've "done" the instruction, so move past it. */
|
|
|
|
setreg(eip, getreg(eip) + insnlen);
|
|
|
|
}
|
2015-02-11 04:45:10 +00:00
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/*L:190
|
|
|
|
* Device Setup
|
|
|
|
*
|
|
|
|
* All devices need a descriptor so the Guest knows it exists, and a "struct
|
|
|
|
* device" so the Launcher can keep track of it. We have common helper
|
2008-03-28 16:05:53 +00:00
|
|
|
* routines to allocate and manage them.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* The layout of the device page is a "struct lguest_device_desc" followed by a
|
2008-02-05 04:49:56 +00:00
|
|
|
* number of virtqueue descriptors, then two sets of feature bits, then an
|
|
|
|
* array of configuration bytes. This routine returns the configuration
|
2009-07-30 22:03:45 +00:00
|
|
|
* pointer.
|
|
|
|
*/
|
2008-02-05 04:49:56 +00:00
|
|
|
static u8 *device_config(const struct device *dev)
|
|
|
|
{
|
|
|
|
return (void *)(dev->desc + 1)
|
2009-06-13 04:26:58 +00:00
|
|
|
+ dev->num_vq * sizeof(struct lguest_vqconfig)
|
|
|
|
+ dev->feature_len * 2;
|
2007-10-22 01:24:22 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This routine allocates a new "struct lguest_device_desc" from descriptor
|
2008-02-05 04:49:56 +00:00
|
|
|
* table page just above the Guest's normal memory. It returns a pointer to
|
2009-07-30 22:03:45 +00:00
|
|
|
* that descriptor.
|
|
|
|
*/
|
2008-02-05 04:49:56 +00:00
|
|
|
static struct lguest_device_desc *new_dev_desc(u16 type)
|
2007-10-22 01:24:22 +00:00
|
|
|
{
|
2008-02-05 04:49:56 +00:00
|
|
|
struct lguest_device_desc d = { .type = type };
|
|
|
|
void *p;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2008-02-05 04:49:56 +00:00
|
|
|
/* Figure out where the next device config is, based on the last one. */
|
|
|
|
if (devices.lastdev)
|
|
|
|
p = device_config(devices.lastdev)
|
|
|
|
+ devices.lastdev->desc->config_len;
|
|
|
|
else
|
|
|
|
p = devices.descpage;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2008-02-05 04:49:56 +00:00
|
|
|
/* We only have one page for all the descriptors. */
|
|
|
|
if (p + sizeof(d) > (void *)devices.descpage + getpagesize())
|
|
|
|
errx(1, "Too many devices");
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2008-02-05 04:49:56 +00:00
|
|
|
/* p might not be aligned, so we memcpy in. */
|
|
|
|
return memcpy(p, &d, sizeof(d));
|
2007-10-22 01:24:22 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Each device descriptor is followed by the description of its virtqueues. We
|
|
|
|
* specify how many descriptors the virtqueue is to have.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
static void add_virtqueue(struct device *dev, unsigned int num_descs,
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
void (*service)(struct virtqueue *))
|
2007-10-22 01:24:22 +00:00
|
|
|
{
|
|
|
|
unsigned int pages;
|
|
|
|
struct virtqueue **i, *vq = malloc(sizeof(*vq));
|
|
|
|
void *p;
|
|
|
|
|
2008-03-28 16:05:53 +00:00
|
|
|
/* First we need some memory for this virtqueue. */
|
2008-12-30 15:25:58 +00:00
|
|
|
pages = (vring_size(num_descs, LGUEST_VRING_ALIGN) + getpagesize() - 1)
|
2007-11-12 02:39:18 +00:00
|
|
|
/ getpagesize();
|
2007-10-22 01:24:22 +00:00
|
|
|
p = get_pages(pages);
|
|
|
|
|
2007-11-19 16:20:40 +00:00
|
|
|
/* Initialize the virtqueue */
|
|
|
|
vq->next = NULL;
|
|
|
|
vq->last_avail_idx = 0;
|
|
|
|
vq->dev = dev;
|
2009-07-30 22:03:45 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* This is the routine the service thread will run, and its Process ID
|
|
|
|
* once it's running.
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
vq->service = service;
|
|
|
|
vq->thread = (pid_t)-1;
|
2007-11-19 16:20:40 +00:00
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* Initialize the configuration. */
|
|
|
|
vq->config.num = num_descs;
|
|
|
|
vq->config.irq = devices.next_irq++;
|
|
|
|
vq->config.pfn = to_guest_phys(p) / getpagesize();
|
|
|
|
|
|
|
|
/* Initialize the vring. */
|
2008-12-30 15:25:58 +00:00
|
|
|
vring_init(&vq->vring, num_descs, p, LGUEST_VRING_ALIGN);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Append virtqueue to this device's descriptor. We use
|
2008-02-05 04:49:56 +00:00
|
|
|
* device_config() to get the end of the device's current virtqueues;
|
|
|
|
* we check that we haven't added any config or feature information
|
2009-07-30 22:03:45 +00:00
|
|
|
* yet, otherwise we'd be overwriting them.
|
|
|
|
*/
|
2008-02-05 04:49:56 +00:00
|
|
|
assert(dev->desc->config_len == 0 && dev->desc->feature_len == 0);
|
|
|
|
memcpy(device_config(dev), &vq->config, sizeof(vq->config));
|
2009-06-13 04:26:58 +00:00
|
|
|
dev->num_vq++;
|
2008-02-05 04:49:56 +00:00
|
|
|
dev->desc->num_vq++;
|
|
|
|
|
|
|
|
verbose("Virtqueue page %#lx\n", to_guest_phys(p));
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Add to tail of list, so dev->vq is first vq, dev->vq->next is
|
|
|
|
* second.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
for (i = &dev->vq; *i; i = &(*i)->next);
|
|
|
|
*i = vq;
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
static void add_pci_virtqueue(struct device *dev,
|
|
|
|
void (*service)(struct virtqueue *))
|
|
|
|
{
|
|
|
|
struct virtqueue **i, *vq = malloc(sizeof(*vq));
|
|
|
|
|
|
|
|
/* Initialize the virtqueue */
|
|
|
|
vq->next = NULL;
|
|
|
|
vq->last_avail_idx = 0;
|
|
|
|
vq->dev = dev;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This is the routine the service thread will run, and its Process ID
|
|
|
|
* once it's running.
|
|
|
|
*/
|
|
|
|
vq->service = service;
|
|
|
|
vq->thread = (pid_t)-1;
|
|
|
|
|
|
|
|
/* Initialize the configuration. */
|
|
|
|
vq->pci_config.queue_size = VIRTQUEUE_NUM;
|
|
|
|
vq->pci_config.queue_enable = 0;
|
|
|
|
vq->pci_config.queue_notify_off = 0;
|
|
|
|
|
|
|
|
/* Add one to the number of queues */
|
|
|
|
vq->dev->mmio->cfg.num_queues++;
|
|
|
|
|
|
|
|
/* FIXME: Do irq per virtqueue, not per device. */
|
|
|
|
vq->config.irq = vq->dev->config.irq_line;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Add to tail of list, so dev->vq is first vq, dev->vq->next is
|
|
|
|
* second.
|
|
|
|
*/
|
|
|
|
for (i = &dev->vq; *i; i = &(*i)->next);
|
|
|
|
*i = vq;
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* The first half of the feature bitmask is for us to advertise features. The
|
|
|
|
* second half is for the Guest to accept features.
|
|
|
|
*/
|
2008-02-05 04:49:56 +00:00
|
|
|
static void add_feature(struct device *dev, unsigned bit)
|
|
|
|
{
|
2008-02-05 04:50:03 +00:00
|
|
|
u8 *features = get_feature_bits(dev);
|
2008-02-05 04:49:56 +00:00
|
|
|
|
|
|
|
/* We can't extend the feature bits once we've added config bytes */
|
|
|
|
if (dev->desc->feature_len <= bit / CHAR_BIT) {
|
|
|
|
assert(dev->desc->config_len == 0);
|
2009-06-13 04:26:58 +00:00
|
|
|
dev->feature_len = dev->desc->feature_len = (bit/CHAR_BIT) + 1;
|
2008-02-05 04:49:56 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
features[bit / CHAR_BIT] |= (1 << (bit % CHAR_BIT));
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
static void add_pci_feature(struct device *dev, unsigned bit)
|
|
|
|
{
|
|
|
|
dev->features |= (1ULL << bit);
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This routine sets the configuration fields for an existing device's
|
2008-02-05 04:49:56 +00:00
|
|
|
* descriptor. It only works for the last device, but that's OK because that's
|
2009-07-30 22:03:45 +00:00
|
|
|
* how we use it.
|
|
|
|
*/
|
2008-02-05 04:49:56 +00:00
|
|
|
static void set_config(struct device *dev, unsigned len, const void *conf)
|
|
|
|
{
|
|
|
|
/* Check we haven't overflowed our single page. */
|
|
|
|
if (device_config(dev) + len > devices.descpage + getpagesize())
|
|
|
|
errx(1, "Too many devices");
|
|
|
|
|
|
|
|
/* Copy in the config information, and store the length. */
|
|
|
|
memcpy(device_config(dev), conf, len);
|
|
|
|
dev->desc->config_len = len;
|
2009-07-30 22:03:43 +00:00
|
|
|
|
|
|
|
/* Size must fit in config_len field (8 bits)! */
|
|
|
|
assert(dev->desc->config_len == len);
|
2008-02-05 04:49:56 +00:00
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
/* For devices with no config. */
|
|
|
|
static void no_device_config(struct device *dev)
|
|
|
|
{
|
|
|
|
dev->mmio_addr = get_mmio_region(dev->mmio_size);
|
|
|
|
|
|
|
|
dev->config.bar[0] = dev->mmio_addr;
|
|
|
|
/* Bottom 4 bits must be zero */
|
|
|
|
assert(~(dev->config.bar[0] & 0xF));
|
|
|
|
}
|
|
|
|
|
|
|
|
/* This puts the device config into BAR0 */
|
|
|
|
static void set_device_config(struct device *dev, const void *conf, size_t len)
|
|
|
|
{
|
|
|
|
/* Set up BAR 0 */
|
|
|
|
dev->mmio_size += len;
|
|
|
|
dev->mmio = realloc(dev->mmio, dev->mmio_size);
|
|
|
|
memcpy(dev->mmio + 1, conf, len);
|
|
|
|
|
|
|
|
/* Hook up device cfg */
|
|
|
|
dev->config.cfg_access.cap.cap_next
|
|
|
|
= offsetof(struct pci_config, device);
|
|
|
|
|
|
|
|
/* Fix up device cfg field length. */
|
|
|
|
dev->config.device.length = len;
|
|
|
|
|
|
|
|
/* The rest is the same as the no-config case */
|
|
|
|
no_device_config(dev);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void init_cap(struct virtio_pci_cap *cap, size_t caplen, int type,
|
|
|
|
size_t bar_offset, size_t bar_bytes, u8 next)
|
|
|
|
{
|
|
|
|
cap->cap_vndr = PCI_CAP_ID_VNDR;
|
|
|
|
cap->cap_next = next;
|
|
|
|
cap->cap_len = caplen;
|
|
|
|
cap->cfg_type = type;
|
|
|
|
cap->bar = 0;
|
|
|
|
memset(cap->padding, 0, sizeof(cap->padding));
|
|
|
|
cap->offset = bar_offset;
|
|
|
|
cap->length = bar_bytes;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This sets up the pci_config structure, as defined in the virtio 1.0
|
|
|
|
* standard (and PCI standard).
|
|
|
|
*/
|
|
|
|
static void init_pci_config(struct pci_config *pci, u16 type,
|
|
|
|
u8 class, u8 subclass)
|
|
|
|
{
|
|
|
|
size_t bar_offset, bar_len;
|
|
|
|
|
|
|
|
/* Save typing: most thing are happy being zero. */
|
|
|
|
memset(pci, 0, sizeof(*pci));
|
|
|
|
|
|
|
|
/* 4.1.2.1: Devices MUST have the PCI Vendor ID 0x1AF4 */
|
|
|
|
pci->vendor_id = 0x1AF4;
|
|
|
|
/* 4.1.2.1: ... PCI Device ID calculated by adding 0x1040 ... */
|
|
|
|
pci->device_id = 0x1040 + type;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* PCI have specific codes for different types of devices.
|
|
|
|
* Linux doesn't care, but it's a good clue for people looking
|
|
|
|
* at the device.
|
|
|
|
*/
|
|
|
|
pci->class = class;
|
|
|
|
pci->subclass = subclass;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 4.1.2.1 Non-transitional devices SHOULD have a PCI Revision
|
|
|
|
* ID of 1 or higher
|
|
|
|
*/
|
|
|
|
pci->revid = 1;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 4.1.2.1 Non-transitional devices SHOULD have a PCI
|
|
|
|
* Subsystem Device ID of 0x40 or higher.
|
|
|
|
*/
|
|
|
|
pci->subsystem_device_id = 0x40;
|
|
|
|
|
|
|
|
/* We use our dummy interrupt controller, and irq_line is the irq */
|
|
|
|
pci->irq_line = devices.next_irq++;
|
|
|
|
pci->irq_pin = 0;
|
|
|
|
|
|
|
|
/* Support for extended capabilities. */
|
|
|
|
pci->status = (1 << 4);
|
|
|
|
|
|
|
|
/* Link them in. */
|
|
|
|
pci->capabilities = offsetof(struct pci_config, common);
|
|
|
|
|
|
|
|
bar_offset = offsetof(struct virtio_pci_mmio, cfg);
|
|
|
|
bar_len = sizeof(((struct virtio_pci_mmio *)0)->cfg);
|
|
|
|
init_cap(&pci->common, sizeof(pci->common), VIRTIO_PCI_CAP_COMMON_CFG,
|
|
|
|
bar_offset, bar_len,
|
|
|
|
offsetof(struct pci_config, notify));
|
|
|
|
|
|
|
|
bar_offset += bar_len;
|
|
|
|
bar_len = sizeof(((struct virtio_pci_mmio *)0)->notify);
|
|
|
|
/* FIXME: Use a non-zero notify_off, for per-queue notification? */
|
|
|
|
init_cap(&pci->notify.cap, sizeof(pci->notify),
|
|
|
|
VIRTIO_PCI_CAP_NOTIFY_CFG,
|
|
|
|
bar_offset, bar_len,
|
|
|
|
offsetof(struct pci_config, isr));
|
|
|
|
|
|
|
|
bar_offset += bar_len;
|
|
|
|
bar_len = sizeof(((struct virtio_pci_mmio *)0)->isr);
|
|
|
|
init_cap(&pci->isr, sizeof(pci->isr),
|
|
|
|
VIRTIO_PCI_CAP_ISR_CFG,
|
|
|
|
bar_offset, bar_len,
|
|
|
|
offsetof(struct pci_config, cfg_access));
|
|
|
|
|
|
|
|
/* This doesn't have any presence in the BAR */
|
|
|
|
init_cap(&pci->cfg_access.cap, sizeof(pci->cfg_access),
|
|
|
|
VIRTIO_PCI_CAP_PCI_CFG,
|
|
|
|
0, 0, 0);
|
|
|
|
|
|
|
|
bar_offset += bar_len + sizeof(((struct virtio_pci_mmio *)0)->padding);
|
|
|
|
assert(bar_offset == sizeof(struct virtio_pci_mmio));
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This gets sewn in and length set in set_device_config().
|
|
|
|
* Some devices don't have a device configuration interface, so
|
|
|
|
* we never expose this if we don't call set_device_config().
|
|
|
|
*/
|
|
|
|
init_cap(&pci->device, sizeof(pci->device), VIRTIO_PCI_CAP_DEVICE_CFG,
|
|
|
|
bar_offset, 0, 0);
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This routine does all the creation and setup of a new device, including
|
2009-07-30 22:03:45 +00:00
|
|
|
* calling new_dev_desc() to allocate the descriptor and device memory. We
|
|
|
|
* don't actually start the service threads until later.
|
2008-03-28 16:05:53 +00:00
|
|
|
*
|
2009-07-30 22:03:45 +00:00
|
|
|
* See what I mean about userspace being boring?
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static struct device *new_device(const char *name, u16 type)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
struct device *dev = malloc(sizeof(*dev));
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* Now we populate the fields one at a time. */
|
2007-10-22 01:24:22 +00:00
|
|
|
dev->desc = new_dev_desc(type);
|
|
|
|
dev->name = name;
|
2007-11-19 16:20:40 +00:00
|
|
|
dev->vq = NULL;
|
2009-06-13 04:26:58 +00:00
|
|
|
dev->feature_len = 0;
|
|
|
|
dev->num_vq = 0;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
dev->running = false;
|
2012-10-04 02:33:25 +00:00
|
|
|
dev->next = NULL;
|
2008-02-05 04:49:56 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Append to device list. Prepending to a single-linked list is
|
2008-02-05 04:49:56 +00:00
|
|
|
* easier, but the user expects the devices to be arranged on the bus
|
|
|
|
* in command-line order. The first network device on the command line
|
2009-07-30 22:03:45 +00:00
|
|
|
* is eth0, the first block device /dev/vda, etc.
|
|
|
|
*/
|
2008-02-05 04:49:56 +00:00
|
|
|
if (devices.lastdev)
|
|
|
|
devices.lastdev->next = dev;
|
|
|
|
else
|
|
|
|
devices.dev = dev;
|
|
|
|
devices.lastdev = dev;
|
|
|
|
|
2007-07-19 08:49:29 +00:00
|
|
|
return dev;
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:45:11 +00:00
|
|
|
static struct device *new_pci_device(const char *name, u16 type,
|
|
|
|
u8 class, u8 subclass)
|
|
|
|
{
|
|
|
|
struct device *dev = malloc(sizeof(*dev));
|
|
|
|
|
|
|
|
/* Now we populate the fields one at a time. */
|
|
|
|
dev->desc = NULL;
|
|
|
|
dev->name = name;
|
|
|
|
dev->vq = NULL;
|
|
|
|
dev->feature_len = 0;
|
|
|
|
dev->num_vq = 0;
|
|
|
|
dev->running = false;
|
|
|
|
dev->next = NULL;
|
|
|
|
dev->mmio_size = sizeof(struct virtio_pci_mmio);
|
|
|
|
dev->mmio = calloc(1, dev->mmio_size);
|
|
|
|
dev->features = (u64)1 << VIRTIO_F_VERSION_1;
|
|
|
|
dev->features_accepted = 0;
|
|
|
|
|
|
|
|
if (devices.device_num + 1 >= 32)
|
|
|
|
errx(1, "Can only handle 31 PCI devices");
|
|
|
|
|
|
|
|
init_pci_config(&dev->config, type, class, subclass);
|
|
|
|
assert(!devices.pci[devices.device_num+1]);
|
|
|
|
devices.pci[++devices.device_num] = dev;
|
|
|
|
|
|
|
|
return dev;
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Our first setup routine is the console. It's a fairly simple device, but
|
|
|
|
* UNIX tty handling makes it uglier than it could be.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
static void setup_console(void)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
struct device *dev;
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* If we can save the initial standard input settings... */
|
2007-07-19 08:49:29 +00:00
|
|
|
if (tcgetattr(STDIN_FILENO, &orig_term) == 0) {
|
|
|
|
struct termios term = orig_term;
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Then we turn off echo, line buffering and ^C etc: We want a
|
|
|
|
* raw input stream to the Guest.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
term.c_lflag &= ~(ISIG|ICANON|ECHO);
|
|
|
|
tcsetattr(STDIN_FILENO, TCSANOW, &term);
|
|
|
|
}
|
|
|
|
|
2015-02-11 04:48:01 +00:00
|
|
|
dev = new_pci_device("console", VIRTIO_ID_CONSOLE, 0x07, 0x00);
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* We store the console state in dev->priv, and initialize it. */
|
2007-07-19 08:49:29 +00:00
|
|
|
dev->priv = malloc(sizeof(struct console_abort));
|
|
|
|
((struct console_abort *)dev->priv)->count = 0;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* The console needs two virtqueues: the input then the output. When
|
2007-10-22 01:24:23 +00:00
|
|
|
* they put something the input queue, we make sure we're listening to
|
|
|
|
* stdin. When they put something in the output queue, we write it to
|
2009-07-30 22:03:45 +00:00
|
|
|
* stdout.
|
|
|
|
*/
|
2015-02-11 04:48:01 +00:00
|
|
|
add_pci_virtqueue(dev, console_input);
|
|
|
|
add_pci_virtqueue(dev, console_output);
|
|
|
|
|
|
|
|
/* There's no configuration area for this device. */
|
|
|
|
no_device_config(dev);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2015-02-11 04:48:01 +00:00
|
|
|
verbose("device %u: console\n", devices.device_num);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
2007-10-22 01:24:22 +00:00
|
|
|
/*:*/
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*M:010
|
|
|
|
* Inter-guest networking is an interesting area. Simplest is to have a
|
2007-10-22 01:24:22 +00:00
|
|
|
* --sharenet=<name> option which opens or creates a named pipe. This can be
|
|
|
|
* used to send packets to another guest in a 1:1 manner.
|
2007-07-26 17:41:03 +00:00
|
|
|
*
|
2011-07-22 05:09:50 +00:00
|
|
|
* More sophisticated is to use one of the tools developed for project like UML
|
2007-10-22 01:24:22 +00:00
|
|
|
* to do networking.
|
2007-07-26 17:41:03 +00:00
|
|
|
*
|
2007-10-22 01:24:22 +00:00
|
|
|
* Faster is to do virtio bonding in kernel. Doing this 1:1 would be
|
|
|
|
* completely generic ("here's my vring, attach to your vring") and would work
|
|
|
|
* for any traffic. Of course, namespace and permissions issues need to be
|
|
|
|
* dealt with. A more sophisticated "multi-channel" virtio_net.c could hide
|
|
|
|
* multiple inter-guest channels behind one interface, although it would
|
|
|
|
* require some manner of hotplugging new virtio channels.
|
|
|
|
*
|
2011-07-22 05:09:50 +00:00
|
|
|
* Finally, we could use a virtio network switch in the kernel, ie. vhost.
|
2009-07-30 22:03:45 +00:00
|
|
|
:*/
|
2007-07-19 08:49:29 +00:00
|
|
|
|
|
|
|
static u32 str2ip(const char *ipaddr)
|
|
|
|
{
|
2008-07-29 14:58:33 +00:00
|
|
|
unsigned int b[4];
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2008-07-29 14:58:33 +00:00
|
|
|
if (sscanf(ipaddr, "%u.%u.%u.%u", &b[0], &b[1], &b[2], &b[3]) != 4)
|
|
|
|
errx(1, "Failed to parse IP address '%s'", ipaddr);
|
|
|
|
return (b[0] << 24) | (b[1] << 16) | (b[2] << 8) | b[3];
|
|
|
|
}
|
|
|
|
|
|
|
|
static void str2mac(const char *macaddr, unsigned char mac[6])
|
|
|
|
{
|
|
|
|
unsigned int m[6];
|
|
|
|
if (sscanf(macaddr, "%02x:%02x:%02x:%02x:%02x:%02x",
|
|
|
|
&m[0], &m[1], &m[2], &m[3], &m[4], &m[5]) != 6)
|
|
|
|
errx(1, "Failed to parse mac address '%s'", macaddr);
|
|
|
|
mac[0] = m[0];
|
|
|
|
mac[1] = m[1];
|
|
|
|
mac[2] = m[2];
|
|
|
|
mac[3] = m[3];
|
|
|
|
mac[4] = m[4];
|
|
|
|
mac[5] = m[5];
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This code is "adapted" from libbridge: it attaches the Host end of the
|
2007-07-26 17:41:03 +00:00
|
|
|
* network device to the bridge device specified by the command line.
|
|
|
|
*
|
|
|
|
* This is yet another James Morris contribution (I'm an IP-level guy, so I
|
2009-07-30 22:03:45 +00:00
|
|
|
* dislike bridging), and I just try not to break it.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
static void add_to_bridge(int fd, const char *if_name, const char *br_name)
|
|
|
|
{
|
|
|
|
int ifidx;
|
|
|
|
struct ifreq ifr;
|
|
|
|
|
|
|
|
if (!*br_name)
|
|
|
|
errx(1, "must specify bridge name");
|
|
|
|
|
|
|
|
ifidx = if_nametoindex(if_name);
|
|
|
|
if (!ifidx)
|
|
|
|
errx(1, "interface %s does not exist!", if_name);
|
|
|
|
|
|
|
|
strncpy(ifr.ifr_name, br_name, IFNAMSIZ);
|
2008-07-29 14:58:33 +00:00
|
|
|
ifr.ifr_name[IFNAMSIZ-1] = '\0';
|
2007-07-19 08:49:29 +00:00
|
|
|
ifr.ifr_ifindex = ifidx;
|
|
|
|
if (ioctl(fd, SIOCBRADDIF, &ifr) < 0)
|
|
|
|
err(1, "can't add %s to bridge %s", if_name, br_name);
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* This sets up the Host end of the network device with an IP address, brings
|
2007-07-26 17:41:03 +00:00
|
|
|
* it up so packets will flow, the copies the MAC address into the hwaddr
|
2009-07-30 22:03:45 +00:00
|
|
|
* pointer.
|
|
|
|
*/
|
2008-07-29 14:58:33 +00:00
|
|
|
static void configure_device(int fd, const char *tapif, u32 ipaddr)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
struct ifreq ifr;
|
2010-08-27 14:39:48 +00:00
|
|
|
struct sockaddr_in sin;
|
2007-07-19 08:49:29 +00:00
|
|
|
|
|
|
|
memset(&ifr, 0, sizeof(ifr));
|
2008-07-29 14:58:33 +00:00
|
|
|
strcpy(ifr.ifr_name, tapif);
|
|
|
|
|
|
|
|
/* Don't read these incantations. Just cut & paste them like I did! */
|
2010-08-27 14:39:48 +00:00
|
|
|
sin.sin_family = AF_INET;
|
|
|
|
sin.sin_addr.s_addr = htonl(ipaddr);
|
|
|
|
memcpy(&ifr.ifr_addr, &sin, sizeof(sin));
|
2007-07-19 08:49:29 +00:00
|
|
|
if (ioctl(fd, SIOCSIFADDR, &ifr) != 0)
|
2008-07-29 14:58:33 +00:00
|
|
|
err(1, "Setting %s interface address", tapif);
|
2007-07-19 08:49:29 +00:00
|
|
|
ifr.ifr_flags = IFF_UP;
|
|
|
|
if (ioctl(fd, SIOCSIFFLAGS, &ifr) != 0)
|
2008-07-29 14:58:33 +00:00
|
|
|
err(1, "Bringing interface %s up", tapif);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int get_tun_device(char tapif[IFNAMSIZ])
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
struct ifreq ifr;
|
2015-02-11 04:46:01 +00:00
|
|
|
int vnet_hdr_sz;
|
2008-07-29 14:58:33 +00:00
|
|
|
int netfd;
|
|
|
|
|
|
|
|
/* Start with this zeroed. Messy but sure. */
|
|
|
|
memset(&ifr, 0, sizeof(ifr));
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We open the /dev/net/tun device and tell it we want a tap device. A
|
2007-07-26 17:41:03 +00:00
|
|
|
* tap device is like a tun device, only somehow different. To tell
|
|
|
|
* the truth, I completely blundered my way through this code, but it
|
2009-07-30 22:03:45 +00:00
|
|
|
* works now!
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
netfd = open_or_die("/dev/net/tun", O_RDWR);
|
2008-07-29 14:58:37 +00:00
|
|
|
ifr.ifr_flags = IFF_TAP | IFF_NO_PI | IFF_VNET_HDR;
|
2007-07-19 08:49:29 +00:00
|
|
|
strcpy(ifr.ifr_name, "tap%d");
|
|
|
|
if (ioctl(netfd, TUNSETIFF, &ifr) != 0)
|
|
|
|
err(1, "configuring /dev/net/tun");
|
2008-07-29 14:58:33 +00:00
|
|
|
|
2008-07-29 14:58:37 +00:00
|
|
|
if (ioctl(netfd, TUNSETOFFLOAD,
|
|
|
|
TUN_F_CSUM|TUN_F_TSO4|TUN_F_TSO6|TUN_F_TSO_ECN) != 0)
|
|
|
|
err(1, "Could not set features for tun device");
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We don't need checksums calculated for packets coming in this
|
|
|
|
* device: trust us!
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
ioctl(netfd, TUNSETNOCSUM, 1);
|
|
|
|
|
2015-02-11 04:46:01 +00:00
|
|
|
/*
|
|
|
|
* In virtio before 1.0 (aka legacy virtio), we added a 16-bit
|
|
|
|
* field at the end of the network header iff
|
|
|
|
* VIRTIO_NET_F_MRG_RXBUF was negotiated. For virtio 1.0,
|
|
|
|
* that became the norm, but we need to tell the tun device
|
|
|
|
* about our expanded header (which is called
|
|
|
|
* virtio_net_hdr_mrg_rxbuf in the legacy system).
|
|
|
|
*/
|
|
|
|
vnet_hdr_sz = sizeof(struct virtio_net_hdr_mrg_rxbuf);
|
|
|
|
if (ioctl(netfd, TUNSETVNETHDRSZ, &vnet_hdr_sz) != 0)
|
|
|
|
err(1, "Setting tun header size to %u", vnet_hdr_sz);
|
|
|
|
|
2008-07-29 14:58:33 +00:00
|
|
|
memcpy(tapif, ifr.ifr_name, IFNAMSIZ);
|
|
|
|
return netfd;
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:195
|
|
|
|
* Our network is a Host<->Guest network. This can either use bridging or
|
2008-07-29 14:58:33 +00:00
|
|
|
* routing, but the principle is the same: it uses the "tun" device to inject
|
|
|
|
* packets into the Host as if they came in from a normal network card. We
|
2009-07-30 22:03:45 +00:00
|
|
|
* just shunt packets between the Guest and the tun device.
|
|
|
|
*/
|
2008-07-29 14:58:33 +00:00
|
|
|
static void setup_tun_net(char *arg)
|
|
|
|
{
|
|
|
|
struct device *dev;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct net_info *net_info = malloc(sizeof(*net_info));
|
|
|
|
int ipfd;
|
2008-07-29 14:58:33 +00:00
|
|
|
u32 ip = INADDR_ANY;
|
|
|
|
bool bridging = false;
|
|
|
|
char tapif[IFNAMSIZ], *p;
|
|
|
|
struct virtio_net_config conf;
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
net_info->tunfd = get_tun_device(tapif);
|
2008-07-29 14:58:33 +00:00
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* First we create a new network device. */
|
2015-02-11 04:46:01 +00:00
|
|
|
dev = new_pci_device("net", VIRTIO_ID_NET, 0x02, 0x00);
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
dev->priv = net_info;
|
2007-07-26 17:41:03 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* Network devices need a recv and a send queue, just like console. */
|
2015-02-11 04:46:01 +00:00
|
|
|
add_pci_virtqueue(dev, net_input);
|
|
|
|
add_pci_virtqueue(dev, net_output);
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We need a socket to perform the magic network ioctls to bring up the
|
|
|
|
* tap interface, connect to the bridge etc. Any socket will do!
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
ipfd = socket(PF_INET, SOCK_DGRAM, IPPROTO_IP);
|
|
|
|
if (ipfd < 0)
|
|
|
|
err(1, "opening IP socket");
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* If the command line was --tunnet=bridge:<name> do bridging. */
|
2007-07-19 08:49:29 +00:00
|
|
|
if (!strncmp(BRIDGE_PFX, arg, strlen(BRIDGE_PFX))) {
|
2008-07-29 14:58:33 +00:00
|
|
|
arg += strlen(BRIDGE_PFX);
|
|
|
|
bridging = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* A mac address may follow the bridge name or IP address */
|
|
|
|
p = strchr(arg, ':');
|
|
|
|
if (p) {
|
|
|
|
str2mac(p+1, conf.mac);
|
2015-02-11 04:46:01 +00:00
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_MAC);
|
2008-07-29 14:58:33 +00:00
|
|
|
*p = '\0';
|
|
|
|
}
|
|
|
|
|
|
|
|
/* arg is now either an IP address or a bridge name */
|
|
|
|
if (bridging)
|
|
|
|
add_to_bridge(ipfd, tapif, arg);
|
|
|
|
else
|
2007-07-19 08:49:29 +00:00
|
|
|
ip = str2ip(arg);
|
|
|
|
|
2008-07-29 14:58:33 +00:00
|
|
|
/* Set up the tun device. */
|
|
|
|
configure_device(ipfd, tapif, ip);
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2008-07-29 14:58:37 +00:00
|
|
|
/* Expect Guest to handle everything except UFO */
|
2015-02-11 04:46:01 +00:00
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_CSUM);
|
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_GUEST_CSUM);
|
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_GUEST_TSO4);
|
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_GUEST_TSO6);
|
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_GUEST_ECN);
|
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_HOST_TSO4);
|
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_HOST_TSO6);
|
|
|
|
add_pci_feature(dev, VIRTIO_NET_F_HOST_ECN);
|
2009-05-11 17:11:46 +00:00
|
|
|
/* We handle indirect ring entries */
|
2015-02-11 04:46:01 +00:00
|
|
|
add_pci_feature(dev, VIRTIO_RING_F_INDIRECT_DESC);
|
|
|
|
set_device_config(dev, &conf, sizeof(conf));
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2008-02-05 04:49:56 +00:00
|
|
|
/* We don't need the socket any more; setup is done. */
|
2007-07-19 08:49:29 +00:00
|
|
|
close(ipfd);
|
|
|
|
|
2008-07-29 14:58:33 +00:00
|
|
|
if (bridging)
|
|
|
|
verbose("device %u: tun %s attached to bridge: %s\n",
|
|
|
|
devices.device_num, tapif, arg);
|
|
|
|
else
|
|
|
|
verbose("device %u: tun %s: %s\n",
|
|
|
|
devices.device_num, tapif, arg);
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
2009-07-30 22:03:45 +00:00
|
|
|
/*:*/
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2007-10-25 05:02:50 +00:00
|
|
|
/* This hangs off device->priv. */
|
2009-07-30 22:03:46 +00:00
|
|
|
struct vblk_info {
|
2007-10-22 01:24:22 +00:00
|
|
|
/* The size of the file. */
|
|
|
|
off64_t len;
|
|
|
|
|
|
|
|
/* The file descriptor for the file. */
|
|
|
|
int fd;
|
|
|
|
|
|
|
|
};
|
|
|
|
|
2007-10-25 05:02:50 +00:00
|
|
|
/*L:210
|
|
|
|
* The Disk
|
|
|
|
*
|
2009-07-30 22:03:45 +00:00
|
|
|
* The disk only has one virtqueue, so it only has one thread. It is really
|
|
|
|
* simple: the Guest asks for a block number and we read or write that position
|
|
|
|
* in the file.
|
|
|
|
*
|
|
|
|
* Before we serviced each virtqueue in a separate thread, that was unacceptably
|
|
|
|
* slow: the Guest waits until the read is finished before running anything
|
|
|
|
* else, even if it could have been doing useful work.
|
|
|
|
*
|
|
|
|
* We could have used async I/O, except it's reputed to suck so hard that
|
|
|
|
* characters actually go missing from your code when you try to use it.
|
2007-10-25 05:02:50 +00:00
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static void blk_request(struct virtqueue *vq)
|
2007-10-22 01:24:22 +00:00
|
|
|
{
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct vblk_info *vblk = vq->dev->priv;
|
2007-10-22 01:24:22 +00:00
|
|
|
unsigned int head, out_num, in_num, wlen;
|
2012-10-16 13:26:13 +00:00
|
|
|
int ret, i;
|
2008-05-03 02:50:45 +00:00
|
|
|
u8 *in;
|
2012-10-16 13:26:13 +00:00
|
|
|
struct virtio_blk_outhdr out;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct iovec iov[vq->vring.num];
|
2007-10-22 01:24:22 +00:00
|
|
|
off64_t off;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Get the next request, where we normally wait. It triggers the
|
|
|
|
* interrupt to acknowledge previously serviced requests (if any).
|
|
|
|
*/
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
head = wait_for_vq_desc(vq, iov, &out_num, &in_num);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2012-10-16 13:26:13 +00:00
|
|
|
/* Copy the output header from the front of the iov (adjusts iov) */
|
|
|
|
iov_consume(iov, out_num, &out, sizeof(out));
|
|
|
|
|
|
|
|
/* Find and trim end of iov input array, for our status byte. */
|
|
|
|
in = NULL;
|
|
|
|
for (i = out_num + in_num - 1; i >= out_num; i--) {
|
|
|
|
if (iov[i].iov_len > 0) {
|
|
|
|
in = iov[i].iov_base + iov[i].iov_len - 1;
|
|
|
|
iov[i].iov_len--;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (!in)
|
|
|
|
errx(1, "Bad virtblk cmd with no room for status");
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* For historical reasons, block operations are expressed in 512 byte
|
|
|
|
* "sectors".
|
|
|
|
*/
|
2012-10-16 13:26:13 +00:00
|
|
|
off = out.sector * 512;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2015-02-11 04:45:12 +00:00
|
|
|
if (out.type & VIRTIO_BLK_T_OUT) {
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Write
|
|
|
|
*
|
|
|
|
* Move to the right location in the block file. This can fail
|
|
|
|
* if they try to write past end.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
if (lseek64(vblk->fd, off, SEEK_SET) != off)
|
2012-10-16 13:26:13 +00:00
|
|
|
err(1, "Bad seek to sector %llu", out.sector);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2012-10-16 13:26:13 +00:00
|
|
|
ret = writev(vblk->fd, iov, out_num);
|
|
|
|
verbose("WRITE to sector %llu: %i\n", out.sector, ret);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Grr... Now we know how long the descriptor they sent was, we
|
2007-10-22 01:24:22 +00:00
|
|
|
* make sure they didn't try to write over the end of the block
|
2009-07-30 22:03:45 +00:00
|
|
|
* file (possibly extending it).
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
if (ret > 0 && off + ret > vblk->len) {
|
|
|
|
/* Trim it back to the correct length */
|
|
|
|
ftruncate64(vblk->fd, vblk->len);
|
|
|
|
/* Die, bad Guest, die. */
|
|
|
|
errx(1, "Write past end %llu+%u", off, ret);
|
|
|
|
}
|
2010-09-03 09:56:18 +00:00
|
|
|
|
|
|
|
wlen = sizeof(*in);
|
|
|
|
*in = (ret >= 0 ? VIRTIO_BLK_S_OK : VIRTIO_BLK_S_IOERR);
|
2012-10-16 13:26:13 +00:00
|
|
|
} else if (out.type & VIRTIO_BLK_T_FLUSH) {
|
2010-09-03 09:56:18 +00:00
|
|
|
/* Flush */
|
|
|
|
ret = fdatasync(vblk->fd);
|
|
|
|
verbose("FLUSH fdatasync: %i\n", ret);
|
2007-11-09 03:13:44 +00:00
|
|
|
wlen = sizeof(*in);
|
2008-05-03 02:50:45 +00:00
|
|
|
*in = (ret >= 0 ? VIRTIO_BLK_S_OK : VIRTIO_BLK_S_IOERR);
|
2007-10-22 01:24:22 +00:00
|
|
|
} else {
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Read
|
|
|
|
*
|
|
|
|
* Move to the right location in the block file. This can fail
|
|
|
|
* if they try to read past end.
|
|
|
|
*/
|
2007-10-22 01:24:22 +00:00
|
|
|
if (lseek64(vblk->fd, off, SEEK_SET) != off)
|
2012-10-16 13:26:13 +00:00
|
|
|
err(1, "Bad seek to sector %llu", out.sector);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2012-10-16 13:26:13 +00:00
|
|
|
ret = readv(vblk->fd, iov + out_num, in_num);
|
2007-10-22 01:24:22 +00:00
|
|
|
if (ret >= 0) {
|
2007-11-09 03:13:44 +00:00
|
|
|
wlen = sizeof(*in) + ret;
|
2008-05-03 02:50:45 +00:00
|
|
|
*in = VIRTIO_BLK_S_OK;
|
2007-10-22 01:24:22 +00:00
|
|
|
} else {
|
2007-11-09 03:13:44 +00:00
|
|
|
wlen = sizeof(*in);
|
2008-05-03 02:50:45 +00:00
|
|
|
*in = VIRTIO_BLK_S_IOERR;
|
2007-10-22 01:24:22 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* Finished that request. */
|
2009-06-13 04:27:11 +00:00
|
|
|
add_used(vq, head, wlen);
|
2007-10-22 01:24:22 +00:00
|
|
|
}
|
|
|
|
|
2007-10-25 05:02:50 +00:00
|
|
|
/*L:198 This actually sets up a virtual block device. */
|
2007-10-22 01:24:22 +00:00
|
|
|
static void setup_block_file(const char *filename)
|
|
|
|
{
|
|
|
|
struct device *dev;
|
|
|
|
struct vblk_info *vblk;
|
2008-02-05 04:49:56 +00:00
|
|
|
struct virtio_blk_config conf;
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2015-02-11 04:45:12 +00:00
|
|
|
/* Create the device. */
|
|
|
|
dev = new_pci_device("block", VIRTIO_ID_BLOCK, 0x01, 0x80);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2007-10-25 05:02:50 +00:00
|
|
|
/* The device has one virtqueue, where the Guest places requests. */
|
2015-02-11 04:45:12 +00:00
|
|
|
add_pci_virtqueue(dev, blk_request);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
|
|
|
/* Allocate the room for our own bookkeeping */
|
|
|
|
vblk = dev->priv = malloc(sizeof(*vblk));
|
|
|
|
|
|
|
|
/* First we open the file and store the length. */
|
|
|
|
vblk->fd = open_or_die(filename, O_RDWR|O_LARGEFILE);
|
|
|
|
vblk->len = lseek64(vblk->fd, 0, SEEK_END);
|
|
|
|
|
|
|
|
/* Tell Guest how many sectors this device has. */
|
2008-02-05 04:49:56 +00:00
|
|
|
conf.capacity = cpu_to_le64(vblk->len / 512);
|
2007-10-22 01:24:22 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Tell Guest not to put in too many descriptors at once: two are used
|
|
|
|
* for the in and out elements.
|
|
|
|
*/
|
2015-02-11 04:45:12 +00:00
|
|
|
add_pci_feature(dev, VIRTIO_BLK_F_SEG_MAX);
|
2008-02-05 04:49:56 +00:00
|
|
|
conf.seg_max = cpu_to_le32(VIRTQUEUE_NUM - 2);
|
|
|
|
|
2015-02-11 04:45:12 +00:00
|
|
|
set_device_config(dev, &conf, sizeof(struct virtio_blk_config));
|
2007-10-22 01:24:22 +00:00
|
|
|
|
|
|
|
verbose("device %u: virtblock %llu sectors\n",
|
2015-02-11 04:45:12 +00:00
|
|
|
devices.device_num, le64_to_cpu(conf.capacity));
|
2007-10-22 01:24:22 +00:00
|
|
|
}
|
2008-07-29 14:58:33 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:211
|
2015-02-11 04:45:09 +00:00
|
|
|
* Our random number generator device reads from /dev/urandom into the Guest's
|
2008-07-29 14:58:33 +00:00
|
|
|
* input buffers. The usual case is that the Guest doesn't want random numbers
|
2015-02-11 04:45:09 +00:00
|
|
|
* and so has no buffers although /dev/urandom is still readable, whereas
|
2008-07-29 14:58:33 +00:00
|
|
|
* console is the reverse.
|
|
|
|
*
|
2009-07-30 22:03:45 +00:00
|
|
|
* The same logic applies, however.
|
|
|
|
*/
|
|
|
|
struct rng_info {
|
|
|
|
int rfd;
|
|
|
|
};
|
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
static void rng_input(struct virtqueue *vq)
|
2008-07-29 14:58:33 +00:00
|
|
|
{
|
|
|
|
int len;
|
|
|
|
unsigned int head, in_num, out_num, totlen = 0;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct rng_info *rng_info = vq->dev->priv;
|
|
|
|
struct iovec iov[vq->vring.num];
|
2008-07-29 14:58:33 +00:00
|
|
|
|
|
|
|
/* First we need a buffer from the Guests's virtqueue. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
head = wait_for_vq_desc(vq, iov, &out_num, &in_num);
|
2008-07-29 14:58:33 +00:00
|
|
|
if (out_num)
|
|
|
|
errx(1, "Output buffers in rng?");
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
2009-07-30 22:03:45 +00:00
|
|
|
* Just like the console write, we loop to cover the whole iovec.
|
|
|
|
* In this case, short reads actually happen quite a bit.
|
2009-07-30 22:03:45 +00:00
|
|
|
*/
|
2008-07-29 14:58:33 +00:00
|
|
|
while (!iov_empty(iov, in_num)) {
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
len = readv(rng_info->rfd, iov, in_num);
|
2008-07-29 14:58:33 +00:00
|
|
|
if (len <= 0)
|
2015-02-11 04:45:09 +00:00
|
|
|
err(1, "Read from /dev/urandom gave %i", len);
|
2012-10-16 13:26:13 +00:00
|
|
|
iov_consume(iov, in_num, NULL, len);
|
2008-07-29 14:58:33 +00:00
|
|
|
totlen += len;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Tell the Guest about the new input. */
|
2009-06-13 04:27:11 +00:00
|
|
|
add_used(vq, head, totlen);
|
2008-07-29 14:58:33 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:199
|
|
|
|
* This creates a "hardware" random number device for the Guest.
|
|
|
|
*/
|
2008-07-29 14:58:33 +00:00
|
|
|
static void setup_rng(void)
|
|
|
|
{
|
|
|
|
struct device *dev;
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
struct rng_info *rng_info = malloc(sizeof(*rng_info));
|
2008-07-29 14:58:33 +00:00
|
|
|
|
2015-02-11 04:45:09 +00:00
|
|
|
/* Our device's private info simply contains the /dev/urandom fd. */
|
|
|
|
rng_info->rfd = open_or_die("/dev/urandom", O_RDONLY);
|
2008-07-29 14:58:33 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* Create the new device. */
|
2015-02-11 04:47:01 +00:00
|
|
|
dev = new_pci_device("rng", VIRTIO_ID_RNG, 0xff, 0);
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
dev->priv = rng_info;
|
2008-07-29 14:58:33 +00:00
|
|
|
|
|
|
|
/* The device has one virtqueue, where the Guest places inbufs. */
|
2015-02-11 04:47:01 +00:00
|
|
|
add_pci_virtqueue(dev, rng_input);
|
2008-07-29 14:58:33 +00:00
|
|
|
|
2015-02-11 04:47:01 +00:00
|
|
|
/* We don't have any configuration space */
|
|
|
|
no_device_config(dev);
|
|
|
|
|
|
|
|
verbose("device %u: rng\n", devices.device_num);
|
2008-07-29 14:58:33 +00:00
|
|
|
}
|
2008-03-28 16:05:53 +00:00
|
|
|
/* That's the end of device setup. */
|
2007-12-28 08:56:24 +00:00
|
|
|
|
2008-03-28 16:05:53 +00:00
|
|
|
/*L:230 Reboot is pretty easy: clean up and exec() the Launcher afresh. */
|
2007-12-28 08:56:24 +00:00
|
|
|
static void __attribute__((noreturn)) restart_guest(void)
|
|
|
|
{
|
|
|
|
unsigned int i;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* Since we don't track all open fds, we simply close everything beyond
|
|
|
|
* stderr.
|
|
|
|
*/
|
2007-12-28 08:56:24 +00:00
|
|
|
for (i = 3; i < FD_SETSIZE; i++)
|
|
|
|
close(i);
|
2008-07-29 14:58:38 +00:00
|
|
|
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* Reset all the devices (kills all threads). */
|
|
|
|
cleanup_devices();
|
|
|
|
|
2007-12-28 08:56:24 +00:00
|
|
|
execv(main_args[0], main_args);
|
|
|
|
err(1, "Could not exec %s", main_args[0]);
|
|
|
|
}
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*L:220
|
|
|
|
* Finally we reach the core of the Launcher which runs the Guest, serves
|
|
|
|
* its input and output, and finally, lays it to rest.
|
|
|
|
*/
|
2009-06-13 04:26:59 +00:00
|
|
|
static void __attribute__((noreturn)) run_guest(void)
|
2007-07-19 08:49:29 +00:00
|
|
|
{
|
|
|
|
for (;;) {
|
2015-02-11 04:45:09 +00:00
|
|
|
struct lguest_pending notify;
|
2007-07-19 08:49:29 +00:00
|
|
|
int readval;
|
|
|
|
|
|
|
|
/* We read from the /dev/lguest device to run the Guest. */
|
2015-02-11 04:45:09 +00:00
|
|
|
readval = pread(lguest_fd, ¬ify, sizeof(notify), cpu_id);
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2007-10-22 01:24:22 +00:00
|
|
|
/* One unsigned long means the Guest did HCALL_NOTIFY */
|
2015-02-11 04:45:09 +00:00
|
|
|
if (readval == sizeof(notify)) {
|
|
|
|
if (notify.trap == 0x1F) {
|
|
|
|
verbose("Notify on address %#08x\n",
|
|
|
|
notify.addr);
|
|
|
|
handle_output(notify.addr);
|
2015-02-11 04:45:10 +00:00
|
|
|
} else if (notify.trap == 13) {
|
|
|
|
verbose("Emulating instruction at %#x\n",
|
|
|
|
getreg(eip));
|
|
|
|
emulate_insn(notify.insn);
|
2015-02-11 04:45:11 +00:00
|
|
|
} else if (notify.trap == 14) {
|
|
|
|
verbose("Emulating MMIO at %#x\n",
|
|
|
|
getreg(eip));
|
|
|
|
emulate_mmio(notify.addr, notify.insn);
|
2015-02-11 04:45:09 +00:00
|
|
|
} else
|
|
|
|
errx(1, "Unknown trap %i addr %#08x\n",
|
|
|
|
notify.trap, notify.addr);
|
2007-07-26 17:41:03 +00:00
|
|
|
/* ENOENT means the Guest died. Reading tells us why. */
|
2007-07-19 08:49:29 +00:00
|
|
|
} else if (errno == ENOENT) {
|
|
|
|
char reason[1024] = { 0 };
|
2008-01-07 13:05:23 +00:00
|
|
|
pread(lguest_fd, reason, sizeof(reason)-1, cpu_id);
|
2007-07-19 08:49:29 +00:00
|
|
|
errx(1, "%s", reason);
|
2007-12-28 08:56:24 +00:00
|
|
|
/* ERESTART means that we need to reboot the guest */
|
|
|
|
} else if (errno == ERESTART) {
|
|
|
|
restart_guest();
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
/* Anything else means a bug or incompatible change. */
|
|
|
|
} else
|
2007-07-19 08:49:29 +00:00
|
|
|
err(1, "Running guest failed");
|
|
|
|
}
|
|
|
|
}
|
2008-03-28 16:05:53 +00:00
|
|
|
/*L:240
|
2007-10-25 05:02:50 +00:00
|
|
|
* This is the end of the Launcher. The good news: we are over halfway
|
|
|
|
* through! The bad news: the most fiendish part of the code still lies ahead
|
|
|
|
* of us.
|
2007-07-26 17:41:03 +00:00
|
|
|
*
|
2007-10-25 05:02:50 +00:00
|
|
|
* Are you ready? Take a deep breath and join me in the core of the Host, in
|
|
|
|
* "make Host".
|
2009-07-30 22:03:45 +00:00
|
|
|
:*/
|
2007-07-19 08:49:29 +00:00
|
|
|
|
|
|
|
static struct option opts[] = {
|
|
|
|
{ "verbose", 0, NULL, 'v' },
|
|
|
|
{ "tunnet", 1, NULL, 't' },
|
|
|
|
{ "block", 1, NULL, 'b' },
|
2008-07-29 14:58:33 +00:00
|
|
|
{ "rng", 0, NULL, 'r' },
|
2007-07-19 08:49:29 +00:00
|
|
|
{ "initrd", 1, NULL, 'i' },
|
2011-01-21 03:37:28 +00:00
|
|
|
{ "username", 1, NULL, 'u' },
|
|
|
|
{ "chroot", 1, NULL, 'c' },
|
2007-07-19 08:49:29 +00:00
|
|
|
{ NULL },
|
|
|
|
};
|
|
|
|
static void usage(void)
|
|
|
|
{
|
|
|
|
errx(1, "Usage: lguest [--verbose] "
|
2008-07-29 14:58:33 +00:00
|
|
|
"[--tunnet=(<ipaddr>:<macaddr>|bridge:<bridgename>:<macaddr>)\n"
|
2007-07-19 08:49:29 +00:00
|
|
|
"|--block=<filename>|--initrd=<filename>]...\n"
|
|
|
|
"<mem-in-mb> vmlinux [args...]");
|
|
|
|
}
|
|
|
|
|
2007-10-22 01:03:26 +00:00
|
|
|
/*L:105 The main routine is where the real work begins: */
|
2007-07-19 08:49:29 +00:00
|
|
|
int main(int argc, char *argv[])
|
|
|
|
{
|
2009-07-30 22:03:45 +00:00
|
|
|
/* Memory, code startpoint and size of the (optional) initrd. */
|
2008-09-29 04:40:07 +00:00
|
|
|
unsigned long mem = 0, start, initrd_size = 0;
|
2009-06-13 04:26:59 +00:00
|
|
|
/* Two temporaries. */
|
|
|
|
int i, c;
|
2007-10-22 01:03:26 +00:00
|
|
|
/* The boot information for the Guest. */
|
2007-10-22 01:29:57 +00:00
|
|
|
struct boot_params *boot;
|
2007-07-26 17:41:03 +00:00
|
|
|
/* If they specify an initrd file to load. */
|
2007-07-19 08:49:29 +00:00
|
|
|
const char *initrd_name = NULL;
|
|
|
|
|
2011-01-21 03:37:28 +00:00
|
|
|
/* Password structure for initgroups/setres[gu]id */
|
|
|
|
struct passwd *user_details = NULL;
|
|
|
|
|
|
|
|
/* Directory to chroot to */
|
|
|
|
char *chroot_path = NULL;
|
|
|
|
|
2007-12-28 08:56:24 +00:00
|
|
|
/* Save the args: we "reboot" by execing ourselves again. */
|
|
|
|
main_args = argv;
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* First we initialize the device list. We keep a pointer to the last
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
* device, and the next interrupt number to use for devices (1:
|
2009-07-30 22:03:45 +00:00
|
|
|
* remember that 0 is used by the timer).
|
|
|
|
*/
|
2008-02-05 04:49:56 +00:00
|
|
|
devices.lastdev = NULL;
|
2007-10-22 01:24:22 +00:00
|
|
|
devices.next_irq = 1;
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* We're CPU 0. In fact, that's the only CPU possible right now. */
|
2008-01-07 13:05:23 +00:00
|
|
|
cpu_id = 0;
|
2009-07-30 22:03:45 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We need to know how much memory so we can set up the device
|
2007-07-26 17:41:03 +00:00
|
|
|
* descriptor and memory pages for the devices as we parse the command
|
|
|
|
* line. So we quickly look through the arguments to find the amount
|
2009-07-30 22:03:45 +00:00
|
|
|
* of memory now.
|
|
|
|
*/
|
2007-07-24 01:43:56 +00:00
|
|
|
for (i = 1; i < argc; i++) {
|
|
|
|
if (argv[i][0] != '-') {
|
2007-10-22 01:03:26 +00:00
|
|
|
mem = atoi(argv[i]) * 1024 * 1024;
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* We start by mapping anonymous pages over all of
|
2007-10-22 01:03:26 +00:00
|
|
|
* guest-physical memory range. This fills it with 0,
|
|
|
|
* and ensures that the Guest won't be killed when it
|
2009-07-30 22:03:45 +00:00
|
|
|
* tries to access it.
|
|
|
|
*/
|
2007-10-22 01:03:26 +00:00
|
|
|
guest_base = map_zeroed_pages(mem / getpagesize()
|
|
|
|
+ DEVICE_PAGES);
|
|
|
|
guest_limit = mem;
|
2015-02-11 04:45:11 +00:00
|
|
|
guest_max = guest_mmio = mem + DEVICE_PAGES*getpagesize();
|
2007-10-22 01:24:22 +00:00
|
|
|
devices.descpage = get_pages(1);
|
2007-07-24 01:43:56 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2007-07-26 17:41:03 +00:00
|
|
|
|
|
|
|
/* The options are fairly straight-forward */
|
2007-07-19 08:49:29 +00:00
|
|
|
while ((c = getopt_long(argc, argv, "v", opts, NULL)) != EOF) {
|
|
|
|
switch (c) {
|
|
|
|
case 'v':
|
|
|
|
verbose = true;
|
|
|
|
break;
|
|
|
|
case 't':
|
2007-10-22 01:24:22 +00:00
|
|
|
setup_tun_net(optarg);
|
2007-07-19 08:49:29 +00:00
|
|
|
break;
|
|
|
|
case 'b':
|
2007-10-22 01:24:22 +00:00
|
|
|
setup_block_file(optarg);
|
2007-07-19 08:49:29 +00:00
|
|
|
break;
|
2008-07-29 14:58:33 +00:00
|
|
|
case 'r':
|
|
|
|
setup_rng();
|
|
|
|
break;
|
2007-07-19 08:49:29 +00:00
|
|
|
case 'i':
|
|
|
|
initrd_name = optarg;
|
|
|
|
break;
|
2011-01-21 03:37:28 +00:00
|
|
|
case 'u':
|
|
|
|
user_details = getpwnam(optarg);
|
|
|
|
if (!user_details)
|
|
|
|
err(1, "getpwnam failed, incorrect username?");
|
|
|
|
break;
|
|
|
|
case 'c':
|
|
|
|
chroot_path = optarg;
|
|
|
|
break;
|
2007-07-19 08:49:29 +00:00
|
|
|
default:
|
|
|
|
warnx("Unknown argument %s", argv[optind]);
|
|
|
|
usage();
|
|
|
|
}
|
|
|
|
}
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* After the other arguments we expect memory and kernel image name,
|
|
|
|
* followed by command line arguments for the kernel.
|
|
|
|
*/
|
2007-07-19 08:49:29 +00:00
|
|
|
if (optind + 2 > argc)
|
|
|
|
usage();
|
|
|
|
|
2007-10-22 01:03:26 +00:00
|
|
|
verbose("Guest base is at %p\n", guest_base);
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* We always have a console device */
|
2007-10-22 01:24:22 +00:00
|
|
|
setup_console();
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2015-02-11 04:45:12 +00:00
|
|
|
/* Initialize the (fake) PCI host bridge device. */
|
|
|
|
init_pci_host_bridge();
|
|
|
|
|
2007-07-19 08:49:29 +00:00
|
|
|
/* Now we load the kernel */
|
2007-10-22 01:03:36 +00:00
|
|
|
start = load_kernel(open_or_die(argv[optind+1], O_RDONLY));
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2007-10-22 01:03:26 +00:00
|
|
|
/* Boot information is stashed at physical address 0 */
|
|
|
|
boot = from_guest_phys(0);
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* Map the initrd image if requested (at top of physical memory) */
|
2007-07-19 08:49:29 +00:00
|
|
|
if (initrd_name) {
|
|
|
|
initrd_size = load_initrd(initrd_name, mem);
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* These are the location in the Linux boot header where the
|
|
|
|
* start and size of the initrd are expected to be found.
|
|
|
|
*/
|
2007-10-22 01:29:57 +00:00
|
|
|
boot->hdr.ramdisk_image = mem - initrd_size;
|
|
|
|
boot->hdr.ramdisk_size = initrd_size;
|
2007-07-26 17:41:03 +00:00
|
|
|
/* The bootloader type 0xFF means "unknown"; that's OK. */
|
2007-10-22 01:29:57 +00:00
|
|
|
boot->hdr.type_of_loader = 0xFF;
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* The Linux boot header contains an "E820" memory map: ours is a
|
|
|
|
* simple, single region.
|
|
|
|
*/
|
2007-10-22 01:29:57 +00:00
|
|
|
boot->e820_entries = 1;
|
|
|
|
boot->e820_map[0] = ((struct e820entry) { 0, mem, E820_RAM });
|
2009-07-30 22:03:45 +00:00
|
|
|
/*
|
|
|
|
* The boot header contains a command line pointer: we put the command
|
|
|
|
* line after the boot header.
|
|
|
|
*/
|
2007-10-22 01:29:57 +00:00
|
|
|
boot->hdr.cmd_line_ptr = to_guest_phys(boot + 1);
|
2007-10-25 05:02:50 +00:00
|
|
|
/* We use a simple helper to copy the arguments separated by spaces. */
|
2007-10-22 01:29:57 +00:00
|
|
|
concat((char *)(boot + 1), argv+optind+2);
|
2007-07-26 17:41:03 +00:00
|
|
|
|
2011-08-15 00:45:10 +00:00
|
|
|
/* Set kernel alignment to 16M (CONFIG_PHYSICAL_ALIGN) */
|
|
|
|
boot->hdr.kernel_alignment = 0x1000000;
|
|
|
|
|
2007-10-22 01:29:44 +00:00
|
|
|
/* Boot protocol version: 2.07 supports the fields for lguest. */
|
2007-10-22 01:29:57 +00:00
|
|
|
boot->hdr.version = 0x207;
|
2007-10-22 01:29:44 +00:00
|
|
|
|
|
|
|
/* The hardware_subarch value of "1" tells the Guest it's an lguest. */
|
2007-10-22 01:29:57 +00:00
|
|
|
boot->hdr.hardware_subarch = 1;
|
2007-10-22 01:29:44 +00:00
|
|
|
|
2007-10-22 01:29:57 +00:00
|
|
|
/* Tell the entry path not to try to reload segment registers. */
|
|
|
|
boot->hdr.loadflags |= KEEP_SEGMENTS;
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2011-07-22 05:09:50 +00:00
|
|
|
/* We tell the kernel to initialize the Guest. */
|
2009-06-13 04:26:59 +00:00
|
|
|
tell_kernel(start);
|
2007-07-26 17:41:03 +00:00
|
|
|
|
2009-07-30 22:03:45 +00:00
|
|
|
/* Ensure that we terminate if a device-servicing child dies. */
|
lguest: have example Launcher service all devices in separate threads
Currently lguest has three threads: the main Launcher thread, a Waker
thread, and a thread for the block device (because synchronous block
was simply too painful to bear).
The Waker selects() on all the input file descriptors (eg. stdin, net
devices, pipe to the block thread) and when one becomes readable it calls
into the kernel to kick the Launcher thread out into userspace, which
repeats the poll, services the device(s), and then tells the kernel to
release the Waker before re-entering the kernel to run the Guest.
Also, to make a slightly-decent network transmit routine, the Launcher
would suppress further network interrupts while it set a timer: that
signal handler would write to a pipe, which would rouse the Waker
which would prod the Launcher out of the kernel to check the network
device again.
Now we can convert all our virtqueues to separate threads: each one has
a separate eventfd for when the Guest pokes the device, and can trigger
interrupts in the Guest directly.
The linecount shows how much this simplifies, but to really bring it
home, here's an strace analysis of single Guest->Host ping before:
* Guest sends packet, notifies xmit vq, return control to Launcher
* Launcher clears notification flag on xmit ring
* Launcher writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\366\r\224`\2058\272m\224vf\274\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Launcher sets up interrupt for Guest (xmit ring is empty)
write(10, "\2\0\0\0\3\0\0\0", 8) = 0
* Launcher sets up timer for interrupt mitigation
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 505}}, NULL) = 0
* Launcher re-runs guest
pread64(10, 0xbfa5f4d4, 4, 0) ...
* Waker notices reply packet in tun device (it was in select)
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [4])
* Waker kicks Launcher out of guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher returns from running guest:
... = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks at input fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [4], left {0, 0})
* Launcher reads pong from tun device:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"\272m\224vf\274\366\r\224`\2058\10\0E\0\0T\364\26\0\0@"..., 1518}], 2) = 108
* Launcher injects guest notification:
write(10, "\2\0\0\0\2\0\0\0", 8) = 0
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher reruns Guest:
pread64(10, 0xbfa5f4d4, 4, 0) = ? ERESTARTSYS (To be restarted)
* Signal comes in, uses pipe to wake up Launcher:
--- SIGALRM (Alarm clock) @ 0 (0) ---
write(8, "\0", 1) = 1
sigreturn() = ? (mask now [])
* Waker sees write on pipe:
select(12, [0 3 4 6 11], NULL, NULL, NULL) = 1 (in [6])
* Waker kicks Launcher out of Guest:
pwrite64(10, "\3\0\0\0\1\0\0\0", 8, 0) = 0
* Launcher exits from kernel:
pread64(10, 0xbfa5f4d4, 4, 0) = -1 EAGAIN (Resource temporarily unavailable)
* Launcher looks to see what fd woke it:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 1 (in [6], left {0, 0})
* Launcher reads timeout fd, sets notification flag on xmit ring
read(6, "\0", 32) = 1
* Launcher rechecks fds:
select(7, [0 3 4 6], NULL, NULL, {0, 0}) = 0 (Timeout)
* Launcher clears Waker:
pwrite64(10, "\3\0\0\0\0\0\0\0", 8, 0) = 0
* Launcher resumes Guest:
pread64(10, "\0p\0\4", 4, 0) ....
strace analysis of single Guest->Host ping after:
* Guest sends packet, notifies xmit vq, creates event on eventfd.
* Network xmit thread wakes from read on eventfd:
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
* Network xmit thread writes packet to TUN device
writev(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"J\217\232FI\37j\27\375\276\0\304\10\0E\0\0T\0\0@\0@\1\265"..., 98}], 2) = 108
* Network recv thread wakes up from read on tunfd:
readv(4, [{"\0\0\0\0\0\0\0\0\0\0", 10}, {"j\27\375\276\0\304J\217\232FI\37\10\0E\0\0TiO\0\0@\1\214"..., 1518}], 2) = 108
* Network recv thread sets up interrupt for the Guest
write(6, "\2\0\0\0\2\0\0\0", 8) = 0
* Network recv thread goes back to reading tunfd
13:39:42.460285 readv(4, <unfinished ...>
* Network xmit thread sets up interrupt for Guest (xmit ring is empty)
write(6, "\2\0\0\0\3\0\0\0", 8) = 0
* Network xmit thread goes back to reading from eventfd
read(7, <unfinished ...>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2009-06-13 04:27:10 +00:00
|
|
|
signal(SIGCHLD, kill_launcher);
|
|
|
|
|
|
|
|
/* If we exit via err(), this kills all the threads, restores tty. */
|
|
|
|
atexit(cleanup_devices);
|
2007-07-19 08:49:29 +00:00
|
|
|
|
2011-01-21 03:37:28 +00:00
|
|
|
/* If requested, chroot to a directory */
|
|
|
|
if (chroot_path) {
|
|
|
|
if (chroot(chroot_path) != 0)
|
|
|
|
err(1, "chroot(\"%s\") failed", chroot_path);
|
|
|
|
|
|
|
|
if (chdir("/") != 0)
|
|
|
|
err(1, "chdir(\"/\") failed");
|
|
|
|
|
|
|
|
verbose("chroot done\n");
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If requested, drop privileges */
|
|
|
|
if (user_details) {
|
|
|
|
uid_t u;
|
|
|
|
gid_t g;
|
|
|
|
|
|
|
|
u = user_details->pw_uid;
|
|
|
|
g = user_details->pw_gid;
|
|
|
|
|
|
|
|
if (initgroups(user_details->pw_name, g) != 0)
|
|
|
|
err(1, "initgroups failed");
|
|
|
|
|
|
|
|
if (setresgid(g, g, g) != 0)
|
|
|
|
err(1, "setresgid failed");
|
|
|
|
|
|
|
|
if (setresuid(u, u, u) != 0)
|
|
|
|
err(1, "setresuid failed");
|
|
|
|
|
|
|
|
verbose("Dropping privileges completed\n");
|
|
|
|
}
|
|
|
|
|
2007-07-26 17:41:03 +00:00
|
|
|
/* Finally, run the Guest. This doesn't return. */
|
2009-06-13 04:26:59 +00:00
|
|
|
run_guest();
|
2007-07-19 08:49:29 +00:00
|
|
|
}
|
2007-07-26 17:41:05 +00:00
|
|
|
/*:*/
|
|
|
|
|
|
|
|
/*M:999
|
|
|
|
* Mastery is done: you now know everything I do.
|
|
|
|
*
|
|
|
|
* But surely you have seen code, features and bugs in your wanderings which
|
|
|
|
* you now yearn to attack? That is the real game, and I look forward to you
|
|
|
|
* patching and forking lguest into the Your-Name-Here-visor.
|
|
|
|
*
|
|
|
|
* Farewell, and good coding!
|
|
|
|
* Rusty Russell.
|
|
|
|
*/
|