* [RFC/GIT PULL] Linux KVM tool for v3.2
@ 2011-11-04 8:38 Pekka Enberg
2011-11-04 12:16 ` Christoph Hellwig
` (3 more replies)
0 siblings, 4 replies; 38+ messages in thread
From: Pekka Enberg @ 2011-11-04 8:38 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Avi Kivity, Andrew Morton, Ingo Molnar, linux-kernel, kvm
Hi Linus,
Please consider pulling the latest KVM tool tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git kvmtool/for-linus
We now support shared host rootfs in the guests. The simplest way to
boot up a KVM guest is to:
- Turn your current kernel .config into a KVM bootable one and build it:
make kvmconfig
yes "" | make oldconfig
make
- Compile the KVM tool:
cd tools/kvm/
make
- Launch to a guest '/bin/sh' using your host rootfs binaries with
networking enabled:
./kvm run
We also support booting both raw images and QCOW2 images in read-only
mode:
./kvm run -d debian_squeeze_amd64_standard.qcow2 -p "root=/dev/vda1"
New features since the 3.1 pull request:
- Shared rootfs support
- 9p/virtio improvements
- AIO support for virtio block devices
- SDL UI improvements
- QCOW2 compressed images read support
- Virtio PCI cleanups
- Guest memory sharing via PCI device
- MSI-X support
- KGDB support for guest kernels
Finally, I discovered one interesting (and esoteric) use case at LinuxCon
Europe for the KVM tool:
https://events.linuxfoundation.org/events/linuxcon-europe/sweeney
It turns out they use KVM tool in some parts of their simulation clusters
because its startup memory footprint is much smaller than Qemu's.
Pekka
------------------>
The following changes since commit c3b92c8787367a8bb53d57d9789b558f1295cc96:
Linux 3.1 (2011-10-24 09:10:05 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git kvmtool/for-linus
Alessandro Guido (2):
kvm tools, ui: Add some missing key codes
kvm tools, sdl: Fix "5" key
Amerigo Wang (2):
kvm tools: build rbtree.o from source
kvm tools: implement "help xxx" command
Amos Kong (4):
kvm tools: Make virt_queue__available return false if queue is not initialized
kvm tools: Add a script to setup private bridge
kvm tools: Add a script to setup tap device
kvm tools: Setup bridged network by a script
Andy Shevchenko (1):
kvm tools: don't use custom strtoul for hex numbers
Aneesh Kumar K.V (21):
tools/kvm/9p: Add support for multiple 9p export dirs
tools/kvm/9p: Always include system header before kernel headers
tools/kvm/9p: Use the same #define as the kernel
tools/kvm/virtio: Add new iov helper
tools/kvm/9p: Don't follow symlink on server
tools/kvm/9p: Fix the pdu len.
tools/kvm/9p: Simplify the handler
tools/kvm/9p: check the iov count with the read/write count
tools/kvm/9p: Add error protocol reply
tools/kvm/9p: Make the 9p handler void return
tools/kvm/9p: Add error handling
tools/kvm/9p: Add encode/decode routines for protocol data
tools/kvm/9p: return EOPNOTSUPP if the handler is not implemented
kvm tools, 9p: Add error handling to protocol handlers
kvm tools, 9p: WSTAT don't use open fid
net/9p: Remove structure not used in the code
tools/kvm: Use kernel header version of net/9p/9p.h
kvm tools, 9p: handler should be called in case of not supported operation
kvm tools: Save and restore the iovec related values in read and write
kvm tools, 9p: Implement 9p2000.L extensions
kvm tools, 9p: Fix walk to prepare correct path name
Anton Vorontsov (1):
kvm tools: Fix broken terminal when kvm exits because of a signal
Asias He (127):
bios: No new line at EOF nit fix
kvm: remove unneccessary iotcl parameter
kvm__init: the kernel should support irq and pit
kvm: reimplement kvm__setup_sregs
kvm: kvm__setup_sregs initialize more registers
early_printk.c: add rep/outsb support
kvm__setup_sregs: fix indentation
kvm, test: add PIT 8254 and PIC 8259 test code
kvm, test: add a counter to tick test in ISR
kvm: Check vmx capability using cpuid
kvm__setup_cpuid: use KVM_GET_SUPPORTED_CPUID to simplify cpuid setup
kvm, pci: fill up virtio device configuration header
kvm: Add cscope target to Makefile
virtio: capacity should be in 512-byte sectors
kvm,virtio: move SECTOR_SHIFT and SECTOR_SIZE to disk-image.h
kvm,virtio: do not publish read only feature to guest
kvm: Add rw to default kernel command line parameters
kvm,virtio: add scatter-gather support
kvm,virtio: add scatter-gather support v2
kvm tools: add README
kvm tools: remove KVM_EXIT_INTERNAL_ERROR
kvm tools: Cleanup IO space and PCI magic numbers
kvm tools: Add helper functions for virtqueue code
kvm tools: Move terminal related code to a new file term.c
kvm tools: Make 8250 serial use infrastructure provided by term.c
kvm tools: Virtio console support
kvm tools: Introduce --enable-virtio-console option
kvm tools: Rename struct device to struct blk_device for block devices
kvm tools: Introduce virtio.c and virtio.h
kvm tools: Unify virtio code file names
kvm tools: Drop virt_queue__get_used_elem virtio helper
kvm tools: Use virt_queue__get_iov to simpify virtio blk IO handler
kvm tools: Make virtio console device code thread-safe
kvm tools: Remove unnecessary goto label out_unlock
kvm tools: Exit KVM session on Ctrl+a and 'x'
kvm tools: Replace option --enable-virtio-console with --console
kvm tools: Fix virtio console PCI class number and device ID number
kvm tools: Fix lock imbalance in virtio_console_pci_io_out()
kvm tools: Use IRQ pin 2 for virtio console
kvm tools: Implement virtio network device
kvm tools: Fix virtio console input problem
kvm tools: Implement virtio net TSO/UFO support
kvm tools: Respect ISR status in virtio header
kvm tools: Respect VRING_AVAIL_F_NO_INTERRUPT
kvm tools: Use virt_queue__trigger_irq() to trigger IRQ for virtio console
kvm tools: Use virt_queue__trigger_irq() to trigger IRQ for virtio blk
kvm tools: Use virt_queue__trigger_irq() to trigger IRQ for virtio rng
kvm tools: Fix virtio console hangs by removing IRQ injection for tx path
kvm tools: Bring VIRTIO_BLK_F_SEG_MAX feature back to virtio blk
kvm tools: Tune the command-line option
kvm tools: Move disk image related code under disk directory
kvm tools: Rename disk-image.c to core.c
kvm tools: Split raw image and blk device code from disk/core.c
kvm tools: Rename disk_image__{read, write}_sector_iov
kvm tools: Remove dead coe disk_image__{read, write}_sector
kvm tools: Consolidate disk_image__{new, new_readonly}
kvm tools: Split blk device code from raw.c to blk.c
kvm tools: Tune up ops in 'struct disk_image_operations'
kvm tools: Rename struct disk_image_operations ops name for raw image
kvm tools: Rename raw_image_ops to blk_dev_ops
kvm tools: Remove unnecessary S_ISBLK check
kvm tools: Do not use 'inline' for disk_image__flush
kvm tools: Add debug info for disk_image__{read, write}
kvm tools: Print debug info for qcow1_nowrite_sector
kvm tools: Update README
kvm tools: Introduce ethernet frame buffer system for uip
kvm tools: Add ARP support for uip
kvm tools: Add IPV4 support for uip
kvm tools: Implement IP checksum for uip
kvm tools: Add ICMP support for uip
kvm tools: Introduce struct uip_udp to present UDP package
kvm tools: Introduce struct uip_pseudo_hdr to present UDP pseudo header
kvm tools: Introduce struct uip_udp_socket
kvm tools: Add two helpers to return UDP {header, total} length
kvm tools: Add helper to return ethernet header length
kvm tools: Implement uip_csum_udp() to calculate UDP checksum
kvm tools: Add UDP support for uip
kvm tools: Introduce struct uip_tcp to present TCP package.
kvm tools: Introduce struct uip_tcp_socket
kvm tools: Add helpers to return TCP {header, total, payload} length
kvm tools: Add helper to return start address of TCP payload
kvm tools: Add helpers to test whether SYN or FIN bit is set.
kvm tools: Add helper to allocate and get TCP initial sequence number
kvm tools: Implement uip_csum_tcp() to calculate TCP checksum
kvm tools: Add TCP support for uip
kvm tools: Introduce uip_init() for uip
kvm tools: Introduce uip_tx() for uip
kvm tools: Introduce uip_rx() for uip
kvm tools: Add MACRO for user and tap mode for virtio net
kvm tools: Reanme net_device to net_dev
kvm tools: Introduce -net {user, tap, none} options for virtio net
kvm tools: Change default guest MAC address to 00:15:15:15:15:15
kvm tools: Make virtio net work with user mode network
kvm tools: Make default network mode to user mode
kvm tools: Make default host ip address to 192.168.33.1
kvm tools: Introduce struct net_dev_operations
kvm tools: Make virtio net work on older kernels
kvm tools: Move uip to net directory
kvm tools: Introduce uip_udp_make_pkg()
kvm tools: Introduce struct uip_dhcp
kvm tools: Add helper to tell if a UDP package is a DHCP package
kvm tools: Add helpers to tell the type of a DHCP message
kvm tools: Get domain name and nameserver from host
kvm tools: Fill DHCP options with domain name and DNS server IP
kvm tools: Fill all DHCP options
kvm tools: Introduce uip_dhcp_make_pkg()
kvm tools: Introduce uip_tx_do_ipv4_udp_dhcp()
kvm tools: Get DNS information from host in uip_init()
kvm tools: Handle DHCP package in gernal UDP processing path
kvm tools: Introduce --guest-ip option
kvm tools: Introduce --host-mac option
kvm tools: Rename --host-ip-addr to --host-ip
kvm tools: Initialize MAC address for virtio net properly
kvm tools: Initialize MAC and IP address for uip properly
kvm tools: Add '-Wunused-result' to WARNINGS
kvm tools: Tune 'kvm balloon' option
kvm tools: Make --kvm-dev option shorter
kvm tools: Make --virtio-9p option shorter
kvm tools: Sort options of kvm run command
kvm tools: Tune --disk option usage information
kvm tools: Set correct virtio pci device class code
kvm tools: Fix MSI-X table size set up
kvm tools: Drop unused variable in struct uip_buf
kvm tools: Use macro in uip_tx_do_ipv4()
kvm tools: Fix a vertical indentation for net/uip/udp.c
kvm tools: Fix ndev mutex and condition variable initialization
kvm tools: Remove dead code virt_queue__trigger_irq()
Cyrill Gorcunov (113):
Add utility functions
Don't die on old kernels without single-step debug support
Makefile: Add CPPFLAGS handling
Add info() helper
kvm: load_bzimage: Proper check for number of setup sectors
kvm: Use 64 bit names when showing registers
kvm: Fixup boot selector
kvm: Add --kernel parameter handling
kvm: Add --params option
kvm: Introduce IVT handling
kvm: Setup fake IVT table
kvm: Fill up fake IVT
kvm: Rename ivt_ prefixed entities
kvm: Put fake bios interrupt handlers into known memory area
bios: Add simple bin2c converter
interrupt: Add interrupt_table__set helper
kvm: Introduce kvm__dump_mem helper
interrupt: Move bios related constants to kvm/bios.h
bios: Add bios stubs generated from assembly files
kvm: Add copying of kernel command line into guest memory
kvm: Update command line related enitites in boot parameters
kvm: Reference to undefined variable
kvm: Make command line to be placed at predefined address
ioport: Make all PIT channels being dummy
kvm: Add more default kernel command line parameters
kvm: Kill the bin2c helper
Makefile: Add cpu specific definition
kvm: Command line update must honor ABI
kvm: Set more fields in boot protocol
kvm: Don't touch 64 bit specific MSR registers on 32 bit
Change __x86_x__ to CONFIG_X86_X
kvm: Print error code on unknown error
kvm: Use PRIx qualificator for printf
kvm: Use strlcat helper for copying cmdline params
kvm: Check for required KVM extensions in one place
kvm: Append missing ending space for built-in command line
kvm: The command line storage should not be too short
early_printk: Simplify the code
tests/pit: Issue cli on ISR handling
test/pit: Fill up IDT with noop handler
kvm: Check for HTL extension granted
tests/pit: Increase PIT frequency up to 1KHz
kvm: Add force exit from tests
kvm, tests: Use motherboard specific ports for testing
kvm, cpuid: Fix XSTOR and VMX compatibility in cpuid
kvm: KVM_CAP_EXT_CPUID is required
kvm, cpuid: Fill up func 0 and 4
kvm, cpuid: Use logical AND on bit ops
kvm: Check for SVM extension being supported for AMD cpus
kvm, bios: Get rid of buggy int10 handler
Exclude .cscope from .gitignore
kvm, bios: Rework BIOS setup
bios: Don't clobber 32bit registers
bios: No need for sti at int15 irq exit
kvm: Add --mem= option
kvm, bios: BIOS code redesign
kvm, bios: Make e820 map to look similar the real one
bios: clean predefined bios area early
pci: Use proper PCI port names
pci: Fix typo in previous commit
kvm, pci: Return "no device" by default
kvm, pci: Add dummy virtio device for probing
kvm, pci: Add bus forwarding register
kvm, pci: Fix offset for pci CONFIG_DATA ioport
kvm, pci: Claim virtio device ioport in pci header
kvm: Support loading initrd image
kvm: Add virtio_ring.h to tree
kvm: Add virtio_blk.h to tree
kvm: Don't forget to close initrd file
bios: Get rid of redundant ops
bios: Use proper grep syntax
kvm: Setup disk geometry if needed
virtio-blk: Leave disk geometry to compute in kernel
make: Add TAGS, tags targets and tune cscope
kvm: save/restore std ttys
8250-serial: Simplify is_readable function
8250-serial: Use linux/serial-reg.h with predefined constants
8250-serial: Make transmitter being always ready to send data
8250-serial: Emulate 8250 behaviour on autoprobing
virtio, block: Rename IOPORT_VIRTIO to IOPORT_VIRTIO_BLK
kvm tools: Setup BIOS for both bzImage and flat image
kvm tools: Remove useless empty lines for a call series in kvm__reset_vcpu
kvm tools: Separate BIOS specifics into own file
kvm tools, bios: Introduce bioscall specificator
kvm tools: Use static assignment for default RAM size
kvm tools: Add --cpus parameter
kvm tools: Update documentation
kvm tools: Add missing space before root= option
kvm tools: Use non shared pin/irqs for virtio devices
kvm tools: Add MP tables support
kvm tools: Use system wide msr-index.h instead of own definitions
kvm tools: Add NR_CPUS definition in case of non-configured kernel sources
kvm tools: Gather Virtio-PCI constants into one place
kvm tools: Fix up PCI pin assignment to conform specification
kvm tools: Fix up mtable srcbusirq assignment for PCI devices
kvm tools: Add debug() helper
kvm tools: Prefix error() and friends helpers with pr_
kvm tools: Add conditional compilation of symbol resolving
kvm tools: Fix alignment for mpf_intel table
kvm tools, 9p: Test for tuncation result
kvm tools: Print out a warning on io-port re-registration
kvm tools: Drop unused vars from int10.c code
kvm tools: Options parser to handle hex numbers
kvm tools: Introduce vidmode parmeter
kvm tools: Delete dangling cursor from int10
kvm tools: Get rid of spaces in ld script
kvm tools: Reform bios make rules
kvm tools, bios: Make sure IRQ handlers segment is properly set
kvm tools: Fix absence of notrace definition
kvm tools: Support xAPIC
kvm tools: Clear presence of performance-energy bias bit
kvm tools: Use ARRAY_SIZE helper to count serial devices
kvm tools: Fix VESA BIOS mode info
David Ahern (1):
kvm tools: do not append root=/dev/vda if passed via command line
Emil Renner Berthing (1):
kvm tools: Update README with instructions for Arch Linux
Giuseppe Calderaro (2):
kvm tools: Fix compilation issue in virtio-blk.c
kvm tools: Remove unused handle_sigint() function
Hagen Paul Pfeifer (2):
kvm tools, setup: Create private directory
kvm tools: remove addr_type - unused but set variable
Ingo Molnar (11):
kvm tools: Emit a more informative error message when /dev/kvm does not open
kvm tools: Fix segfault when running 'kvm' without a disk image
kvm tools: Indicate the end of a KVM session
kvm tools: Fix 64-bit assumptions and type uglinesses
kvm tools: Fix 32-bit build of the asm/system.h include
kvm tools: Enable earlyprintk=serial by default
kvm tools: Fix and improve the CPU register dump debug output code
kvm tools: Dump vCPUs in order
kvm tools: Use standardized style for the virtio/net.c driver
kvm tools: Fix type mismatches on GCC 4.4 on 32-bit systems
kvm tools: Fix virtio net build breakage on 32-bit
John Floren (6):
kvm tools: Add BIOS INT10 handler
kvm tools: Add video mode to kernel initialization
kvm tools: Add VESA device
kvm tools: Update makefile and feature tests
kvm tools: Initialize and use VESA and VNC
kvm tools: Add support for PS/2 keyboard system
Konstantin Khlebnikov (1):
kvm tools: fix instances enumeration
Lan Tianyu (1):
kvm tools: Add support for the read operation of qcow and qcow2 compressed image
Liming Wang (9):
kvm tools: remove unused options
kvm tools: convert callback to int and deal with the return value
kvm tools: handle failure of command
kvm tools: ignore balloon signals by default to avoid balloon crash
kvm tools: enable keyboard press repeat for sdl
kvm tools: check negative value of num_pages
kvm tools: unify all serials' registers with the first serial
kvm tools: fix wrong virtio id for balloon
kvm tools: change option type of RNG from increment to boolean
Osier Yang (1):
kvm tools: Beautify kvm list output
Paul Bolle (1):
kvm tools: Fix compilation on x86_64
Pekka Enberg (345):
Initial commit
Check for KVM_API_VERSION at init
Add .gitignore file
Create a VM using ioctl(KVM_CREATE_VM)
Move KVM fds into 'struct kvm'
Check for KVM_CAP_USER_MEMORY
Clean up KVM initialization
Initialize KVM some more
Set up TSS address to make vcpu creation work
Clean up struct kvm file descriptor names
Mmap the kvm_run structure
Move CPU emulation code to cpu.c
Load kernel image to the VM
Initial version of kernel image loading
Initialize guest memory region properly
Load bzImage to guest RAM
Update .gitignore to include object files
Dump registers after KVM_RUN returns
Initialize RIP before starting to run the guest
Print out constant names for KVM exit reasons
Show dump of executed code at KVM exit
Fix guest code printout
Setup rflags properly to fix EXIT_UNKNOWN
Fix up rflags printing
Dump KVM_EXIT_IO details
Move KVM_SET_REGS to kvm__reset_vcpu()
Enable KVM guest single-stepping
Separate KVM code from the main loop
Setup segmentation for the guest
Fix LDT descriptor type for KVM_SET_SREG
Improve KVM register dump output
Fix up 'ip' in kvm__reset_vcpu() to take real mode into account
Print 'avl' bits of a segment
Add a simple "kernel" binary that can be used for testing
Add support for loading flat binaries
kvm: Load bzImage real-mode boot sector and setup code
kvm: Fix bzImage setup sector default count
kvm: Read the whole bzImage to memory
kvm: Hardcode a "reset vector" at f000:fff0
kvm: Add some single-step debugging and don't stop running
kvm: Clean up reset vector setup code
kvm: Document the 'reset vector' hack
kvm: Enable 'interrupt request window'
Revert "kvm: Enable 'interrupt request window'"
kvm: Fix setup size calculation
kvm: Remove 'reset vector' hack
kvm: Fix kernel boot IP
kvm: Load kernel at 0x1000
kvm: Setup stack for the kernel
kvm: Introduce host_real_to_guest() helper function
kvm: Rename interrupt emulation source files
kvm: Clean up kvm/interrupt.h a bit
kvm: Remove unnecessary includes from interrupt.c
kvm: Move interrupt table to struct kvm
kvm: Clean up interrupt_table__setup()
kvm: Move util.h to include/kvm directory
kvm: Introduce --single-step command line option
kvm: Setup CPUID for the guest
kvm: Enable GCC debugging information
kvm: Extract CPUID code into its own file
kvm: Extract ioport emulation code to its own file
kvm: Don't abort guest on KVM_EXIT_IO
kvm: Add simple NMI enable/disable support
kvm: Remove unused cpu.c file
kvm: Setup guest FPU state
kvm: Ignore math co-processor reset I/O writes
kvm: Ignore PIC init during boot
kvm: Fix protected mode code dump
kvm: Free memory on exit
kvm: Clean up Makefile output
kvm: Add test binaries to .gitignore
kvm: Clean up kvm__reset_vcpu() function
kvm: Setup VCPU MSRs
kvm: Add .gitignore for bios build files
kvm: Show gdt and idt registers
kvm: Dump stack on KVM oops
kvm: Dump page tables at exit
kvm: Set up MAXPHYADDR guest CPUID
kvm: Don't crash debug dump if address isn't in guest memory
kvm: Ignore PCI config space accesses
kvm: Ignore MMIO accesses
kvm: Ignore PIC accesses
kvm: Ignore CMOS RAM/RTC ioports
kvm: Ignore CRT control ioports
kvm: Ignore dummy delay ioport
kvm: Ignore PIT ioports
kvm: Ignore keyboard controller ioports
kvm: Fix off-by-one bugs in kvm__setup_cpuid()
kvm: Fix minor formatting glitch in cpuid.c
kvm: Add support for early serial printk
kvm: Force 'notsc' and 'earlyprintk' kernel parameters
kvm: Clean up early serial code
Merge branch 'master' of git://github.com/cyrillos/vm
kvm: Dump state on SIGQUIT
kvm: Flush stdout for early printk
kvm: Fix .gitignore patterns
kvm, test: Move PIT tests to separate directory
kvm: Add Makefile for compiling all test cases
kvm: Add .gitignore for tests
kvm, test: Improve PIT test output
kvm: Add 'check' target to Makefile
kvm: Use 'nopci pci=off' kernel parameters by default
kvm: Cleanup command line parsing
kvm: Cleanup ioport_ops table
kvm: Add proper 00E0 ioport handling
kvm: Add '--params' to usage
kvm: Don't stop on ioport errors by default
kvm: Fix compilation warning
kvm: Introduce 'make devices' target
kvm: Introduce '--kvm-dev' command line option
kvm: Cleanup kvm__cpu_supports_vm()
kvm: Cleanup struct boot_params setup
kvm: BIOS E820 memory map emulation
kvm: Use -Os optimization for GCC
kvm: Fix VM support check for unrecognized CPUs
kvm: Check for read() return value in load_bzimage()
kvm: Fix usage command line format
kvm: Fix load_bzimage for flat binaries
kvm: Use 32-bit operand size prefix for rdfs8()
kvm: Use -Werror for building the thing
kvm: Remove unused outb() function from e820.c
kvm: Cleanup BIOS setup code
kvm: Use sizeof instead of magic number
kvm: Clear performance monitoring CPUID flags
kvm: Update bios .gitignore list
kvm: Fix Makefile header dependencies
kvm: Clean header dependency files
kvm: Exclude BIOS object files from header deps
kvm: Use proper segment + offset in e820 bios
kvm: Add some more ioport emulation
kvm: Enable Linux kernel PCI probing
kvm: Force PCI Configuration Mechanism 1
kvm: Initial PCI probe emulation
kvm: Add PCI CONFIG_ADDRESS register layout
kvm, pci: Fix device probe accesses
kvm: Fix PCI config space emulation
kvm, pci: Don't calculate offset twice
kvm, pci: Fix unaligned PCI accesses
kvm: Kill virtio debugging code
kvm: Add KVM ABI headers
Merge branch 'master' of git://github.com/cyrillos/vm
kvm: Fix unaligned PCI_CONFIG_ADDRESS accesses
kvm: Extract virtio-blk driver to separate file
kvm: Update .gitignore to ignore tags
kvm: Add port range to ioport__register()
kvm: Add virtio PCI ioport handler stubs
kvm: Fail virtio blk ioports by default
kvm: Virtio block device emulation
kvm: Fix kernel loading error messages
kvm: Fix virtio block PCI device IRQ configuration
kvm: Implement "host features" for virtio blk device
kvm: Cleanup virtio block device I/O functions
kvm: Don't use VIRTIO_BLK_F_SEG_MAX in the hypervisor
kvm: Remove bogus #include directive
Revert "kvm: Fix virtio block PCI device IRQ configuration"
kvm: Implement virtio blk device config space
kvm: Make virtio block device read-only
kvm: Add ->queue_selector and ->queue_pfn to struct device
kvm: Implement virtqueues for virtio block device
kvm: Implement virtio blk device vring lookup
kvm: Kill stale interrupt configuration comment
kvm: Add support for disk images
kvm: Use disk image API from virtio block device
kvm: Cleanup disk geometry setup code
kvm: Introduce a list of known BUGS
Merge branch 'master' of git://github.com/cyrillos/vm
kvm: Enable virtio block device if disk image specified
kvm: Improve kvm__init() error message
kvm: Fail if user specifies a QCOW disk image
kvm: Fix virtqueue ring index check
kvm: Fix virtio block device support some more
kvm: Support MSR register for serial console
kvm: Kill debug logging from blk-virtio.c
kvm: Implement virtio block device write support
kvm: Redirect serial console to stdout, not stderr
kvm: Improve 8250 serial console support
kvm: Fix magic numbers in 8250 support
kvm,serial: Enable THRI bit in IIR register
kvm: Implement support interrupt injection
kvm: Rename early_printk.c to 8250-serial.c
kvm,8250: Inject interrupts to guest
kvm: Use serial console by default
kvm,8250: Implement serial input support
kvm: Put terminal in canonical mode
Merge branch 'master' of /home/penberg/kvm into kvm/core
kvm: Use disk name for mounting root
kvm: Improve 8250 serial console interrupt handling
kvm: Support for more than one serial ttys
kvm,8250: Make ttyS1 and ttyS2 disabled
kvm,8250: Fix "too much work for irq4" problems
kvm,8250: Fix ->counter clearing
kvm,8250: Cleanup receive emulation
kvm,8250: Implement missing register emulation
kvm,serial: Implement 16550A FIFO support
kvm: Cleanup interrupt timer logic
Revert "kvm,virtio: add scatter-gather support"
kvm: Remove duplicate headers
kvm tools: Cleanup termios handling
kvm,8250: Fix device initial state
kvm tools: Cleanup virtqueue handling
tools/kvm: Exit gracefully upon KVM_EXIT_SHUTDOWN
kvm tools, 8250: Don't set the UART_LSR_OE bit
kvm tools: Fix large disk images on 32-bit
kvm tools: Fix E820 map on x86-64
kvm tools: Fix required boot protocol version
tools kvm: Fix missing ARCH define on 32-bit in Makefile
kvm tools: Cleanup strstr() in expression
kvm tools: Cleanup virtio block device configuration
kvm tools: Cleanup disk image code
kvm tools: Drop hard-coded 'nosmp' kernel parameter
kvm tools: Use STDIN_FILENO instead of fileno(stdin)
kvm tools: Use pread() and pwrite() in disk-image.c
kvm tools: Don't exit() on SIGQUIT
kvm tools: Send SysRq-P to guest kernel on SIGQUIT
Merge branch 'kvm/gitish' into kvm/core
kvm tools: Fix .gitignore after Gitification merge
kvm tools: Cleanup virtio_blk_do_io_request I/O error handling
kvm tools: Make code mostly checkpatch clean
kvm tools: Introduce KVM VCPU data structure
kvm tools: Make 8250 code thread-safe
kvm tools: Make virtio block device code thread-safe
kvm tools: Extract kvm_cpu__start() function
kvm tools: Move CPU initialization to kvm_cpu__start()
kvm tools: Fix pthread mutex error checks
kvm tools: Use per-VCPU threads for execution
kvm tools: Fix 'kill -3' to send SysRq-P to the guest
kvm tools: Use mutex_lock() and mutex_unlock() wrappers
kvm tools: Remove the BUGS file
kvm tools: Use ioport__register() for legacy devices
Revert "kvm tools: Use mmap by default for disk images"
kvm tools: Use host kernel image by default
kvm tools: Don't override kernel image passed by user
kvm tools: Add read-only support for block devices
kvm tools: Cleanup qcow1_read_sector() function
kvm tools: Untangle qcow1_read_sector() function
kvm tools: Kill redundant assignment in qcow1_read_cluster()
kvm tools: Fix qcow1_read_cluster() return value on error
kvm tools: Add read-only support for QCOW2 images
kvm tools: Show KVM state on SIGQUIT
kvm tools: Fix disk image double-free on KVM panic
kvm tools: Emulate RTC to fix system time in guests
Revert "kvm tools: Use threadpool for virtio-net"
kvm tools: Fix virtio rng build breakage
kvm tools: Move virtio drivers under virtio directory
kvm tools: Cleanup virtio code some more
kvm tools: Scale guest RAM size by CPU count
kvm tools: Limit CPU count by KVM_CAP_NR_VCPUS
kvm tools: Don't use all of host RAM for guests by default
kvm tools: Warn if guest RAM size exceeds host RAM size
kvm tools: Fix 'kill -3' hangs
kvm tools: QCOW code cleanups
kvm tools: Use '-c' for '--cpus', not '--console'
kvm tools: Print out important command line options at startup
kvm tools: Fix read-only support in QCOW
kvm tools: Fix typo in converting bytes to MBs
kvm tools: Lookup symbol based on RIP for 'kill -3'
kvm tools: Fix includes for preadv/pwritev
kvm tools: Make host_ram_size() more robust
kvm tools: Fail if passed initrd is not really an initrd
kvm tools: Move hardware drivers to hw directory
kvm tools, serial: Register 0x2e8 ioport
kvm tools: Don't register dummy ops for serial ports
kvm tools: Drop dummy PCI ioport registrations
kvm tools: Code cleanups to hw/vesa.c
kvm tools: Use more readable name for ioport mutex
kvm tools: Fix up common QCOW function names
kvm tools: Add 'kvm debug' command
kvm tools: Use constants for i8042 register numbers
kvm tools, i8042: Sort status register bits
kmv tools, i8042: Use kernel status register bit names
kvm tools, i8042: Use kernel command names
kvm tools, i8042: Fix device init failure
kvm tools, ui: Add framebuffer infrastructure
kvm tools, ui: Move VNC specific framebuffer code to ui/vnc.c
kvm tools, ui: Add support for SDL framebuffer output target
kvm tools, vesa: Cleanup code in bios/int10.c
kvm tools, vesa: Fix 'ah' access in int10_vesa()
kvm tools, vesa: Use guest-mapped memory for framebuffer
kvm tools: Kill libvnc dependency from hw/i8042.c
kvm tools, ui: Add simple keyboard support to SDL UI
kvm, ui: Kill fb_write() function
kvm tools: Makefile cleanups
kvm tools: Add WERROR to Makefile for disabling -Werror
kvm tools: Fix 'kvm run' on 32-bit machines with >2 GB of RAM
kvm tools, qcow: Use fdatasync() instead of sync_file_range()
kvm run: Add 'panic=1' to default kernel options
Merge commit 'v3.0-rc5' into kvm/core
kvm tools: Fix guest single-stepping setup
kvm tools: Don't sort command-list.txt for help text
kvm tools: Add KVMTOOLS-VERSION-FILE to .gitignore
kvm tools, qcow: Rename struct qcow_l2_cache to struct qcow_l2_table
kvm tools, qcow: Use 'struct qcow_l2_table' instead of untyped array
kvm tools, qcow: Fix locking issues
kvm tools, qcow: Introduce qcow_disk_flush()
kvm tools, qcow: Delayed L1 table writeout
kvm tools, qcow: Don't fdatasync() L2 table writeout
kvm tools, qcow: Use big endian order for L2 table entries
kvm tools, qcow: Delayed L2 table writeout
kvm tools, qcow: Flush only dirty L2 tables
kvm tools, qcow: I/O error on compressed sectors
kvm tools: Use writev() in xwritev()
kvm tools, qcow: Fix copy-on-write image corruption
kvm tools: Rename 'struct qcow_table' to 'struct qcow_l1_table'
kvm tools, qcow: Unify L1 and L2 variable names
kvm tools: Fix formatting in include/kvm/qcow.h
kvm tools, qcow: Move L2 cache to 'struct qcow_l1_table'
kvm tools, qcow: Rename L2 table lookup functions
kvm tools, qcow: Force read-only mode for QCOW images
kvm tools, 9p: Fix init error handling
kvm tools, qcow: Add support for writing to zero refcount clusters
kvm tools: Boot to host /bin/sh via 9p by default
kvm tools: Enable kernel DHCP autoconf by default
Revert "kvm tools: Enable kernel DHCP autoconf by default"
kvm tools: Improve 'kvm list' output
kvm tool: Fix builtin command usage printouts
kvm tools: Improve 'kvm version' output
kvm tools: Stop guest if SDL window is closed
kvm tools: Organize includes in builtin-run.c
kvm tools, bios: Setup CF after returning from interrupt handler
kvm tools, bios: Rename struct int10_args to struct biosregs
kvm tools, bios: Add macros for BIOS registers
kvm tools, bios: Add EIP and EFLAGS to 'struct biosregs'
kvm tools, bios: Use struct biosregs in E820 code
kvm tools, bios: Move CF clearing to e820_query_map()
kvm tools, bios: Convert int15 code to C
kvm tools, bios: Set CF for non-supported services
kvm tools, bios: Rename bios.S to entry.S
Merge branch 'kvm/bios' into kvm/core
kvm tool, sdl: Set window caption
kvm tools: Add entry to MAINTAINERS file
kvm tools: Introduce 'kvm setup' command
kvm tools, setup: Create /tmp in guest filesystems
kvm tools: Fix up build instructions on Fedora
kvm tools: NULL-terminate init env
kvm tools: Move segment_to_flat() to kvm/segment.h
kvm tools: Use HOME_DIR and KVM_PID_FILE_PATH from <kvm/kvm.h>
kvm tools: Use kvm__get_dir() helper function
kvm tools, bios: Fix BIOS to kernel memory copy
kvm tools: Disable stack protector for BIOS code
kvm tools, bios: Don't include glibc headers
kvm tools: Kill double slash from kvm__get_dir()
kvm tools: Improve "kvm setup" info and error messages
kvm tools: Improve "kvm list" default output
kvm tools: Fix 'kvm run' when run the first time
kvm tools: Fix kvm__set_dir() to include trailing slash
Prasad Joshi (29):
kvm tools: Fix KVM problem on SuSe 2.6.37 kernel
kvm tools: Generate list of common kvm tool commands
kvm tools: Use code from perf for argument processing
kvm tools: Provide the basic Gitish framework
kvm tools: Use the Gitish freamwork to run the virtual machine
kvm tools: Fix a possible segfault if raw_image__probe returns NULL
kvm tools: Avoid using disk_image->priv member in disk_image__new()
kvm tools: add a close method for raw_image_ro_mmap_ops
kvm tools: Add QCOW version 1 read-only support
kvm tools: Use the readily built kernel with 'kvm run' if not specified explicitly
kvm tools: Fix function names in qcow.c
kvm tools: Avoid byte-order conversion during each read operation
kvm tools: Free l1_table in qcow1_disk_close() and in error path of qcow1_probe()
kvm tool: Remove the __stringify*() definition from util.h
kvm tool: Change the type of QCOW table index and offset variables to u64
kvm tools: check the cluster boundary in the qcow read code
kvm tools: Correct a variable naming spelling mistake
kvm tools: Use the root partition of the host to boot the guest machine
kvm tools: check read permission before using the root partition of the host to boot VM
kvm tools: display appropriate error message when default kernel image could not be found
kvm tools: fix a memory leak in qcow2_read_header
kvm tools: Add QCOW write support
kvm tools: Add VIRTIO_BLK_T_FLUSH feature to handle flush operation from VM
kvm tools: Add a wrapper function to open disk images
kvm tools: Close the disk images after the guest shuts down
kvm tools: Add a wrapper function to initialize all virtio block devices
kvm tools: Release memory allocated during virtio block initialization
kvm tools: Add QCOW level2 caching support
kvm tools: Add IO delay option
Sasha Levin (221):
kvm tools: Free memory and FDs on exit
kvm tools: Fix input hang when compiling without optimization
kvm tools: Close kernel FD after loading it into memory
kvm tools: Use mmap by default for disk images
kvm tools: Add option to load disk image read only
kvm tools: Add OPT_GROUP to cmdline parser
kvm tools: Arrange cmdline help menu
kvm tools: Set up tun interface using ioctls
kvm tools: Make host side IP configurable
kvm tools: Organize net parameters into struct
kvm tools: Enable network by default
kvm tools: Add option to specify guest MAC
kvm tools: Rename raw_image__close_sector_ro_mmap
kvm tools: Fix leak in QCOW
kvm tools: Add scatter-gather variants of IO functions
kvm tools: Add scatter-gather support for disk images
kvm tools: Rename _sg to _iov and remove dead code
kvm tools: Fix iov shifting
kvm tools: Fix possible leak in disk_image
kvm tools: Use threading for virtio block devices
kvm tools: Use mmap to allocate guest RAM
kvm tools: Fix possible leak in qcow
kvm tools: Prevent duplicate definitions of ALIGN
kvm tools: Add kernel headers required for using list
kvm tools: Introduce generic I/O thread pool
kvm tools: Use threadpool for virtio-blk
kvm tools: Use threadpool for virtio-console
kvm tools: Use threadpool for virtio-net
kvm tools: Modify thread pool API
kvm tools: Lock job_mutex before signalling
kvm tools: Introduce virtio-rng
kvm tools: Add cmdline switch to enable virtio-rng
kvm tools: Drop ALIGN from bios.h
kvm tools: Fix virt_queue__set_used_elem
kvm tools: Move disk_image into virtio-blk
kvm tools: Add support for multiple virtio-blk
kvm tools: Add cmdline options for loading multiple images
kvm tools: Abolishment of uint*_t types
kvm tools: virtio-blk code cleanup
kvm tools: virtio-console code cleanup
kvm tools: virtio-net code cleanup
kvm tools: virtio-rng code cleanup
kvm tools: Fix loading root device as image
kvm tools: Enable SMP support
kvm tools: Simplify search for root device
kvm tools: Introduce IRQ registry
kvm tools: Dynamically add devices when creating mptable
kvm tools: Convert virtio devices to use IRQ registry
kvm tools: Rename pci_device to pci_hdr for clarity
kvm tools: Add missing space after kernel params
kvm tools: Add memory gap for larger RAM sizes
kvm tools: Prevent PFN wraparound
kvm tools: Use definitions from kernel headers
kvm tools: Rename 'self' variables
kvm tools: Use constants for commonly used mmap flags
kvm tools: Add boot test to checks
kvm tools: Return correct values from disk IOV functions
kvm tools: Add interval red-black tree helper
kvm tools: Add MMIO address mapper
kvm tools: Use virtio IDs from <linux/virtio_ids.h>
kvm tools: Exit properly on SMP guests
kvm tools: Default guest cpu count to host cpu count
kvm tools: Copy net/9p/9p.h
kvm tools: Add virtio-9p
kvm tools: Cleanup e820 code
kvm tools: Fix rbtree-interval balancing
kvm tools: Modify ioport to use interval rbtree
kvm tools: Add optional parameter used in ioport callbacks
kvm tools: Add basic ioport dynamic allocation
kvm tools: Use ioport context to control blk devices
kvm tools: Add support for multiple virtio-rng devices
kvm tools: Use dynamic IO port allocation in vesa driver
kvm tools: Use dynamic IO port allocation in 9p driver
kvm tools: Use dynamic IO port allocation in virtio-console
kvm tools: Use dynamic IO port allocation in virtio-net
kvm tools: Prevent double assignment of guest memory info
kvm tools: Exit VCPU thread only when SIGKVMEXIT is received
kvm tools: Add ioeventfd support
kvm tools: Use ioeventfd in virtio-blk
kvm tools: Use ioeventfd in virtio-net
kvm tools: Use ioeventfd in virtio-rng
kvm tools: Use correct value for user signal base
kvm tools: Remove wrong global definition of kvm
kvm tools: Add APIs to allow pausing guests
kvm tools: Pause/resume guest using SIGUSR2
kvm tools: Add a brlock
kvm tools: Add rwlock wrapper
kvm tools: Add debug mode to brlock
kvm tools: Use brlock in MMIO and IOPORT
kvm tools: Use vesa reserved space for strings and modes
kvm tools: Add MMIO coalescing support
kvm tools: Fix some SDL keyboard translations
kvm tools: Use double buffering with SDL
kvm tools: Add 'kvm pause' command
kvm tools: Signal only one thread when injecting console interrupts
kvm tools: Fix attempt to free mmaped memory
kvm tools: Implement keyboard reset method
kvm tools: Use ioeventfd in virtio-9p
kvm tools: Don't dynamically allocate threadpool jobs
kvm tools: Process virtio-blk requests in parallel
kvm tools: Allow giving instance names
kvm tools: Provide instance name when running 'kvm debug'
kvm tools: Provide instance name when running 'kvm pause'
kvm tools: Add virtio-balloon device
kvm tools: Advise memory allocated for guest RAM as KSM mergable
kvm tools: Add 'kvm balloon' command
kvm tools: Stop VCPUs before freeing struct kvm
kvm tools: Fix home dir resolution
kvm tools: Give guest instances default name
kvm tools: Add instance enumerator
kvm tools: Add 'kvm list' command
kvm tools: Allow pausing and debugging all running instances
kvm tools: Export kvm__remove_pidfile
kvm tools: Clean ghost pid files in 'kvm list'
kvm tools: Add 'kvm version' command
kvm tools: Properly add 'kvm list' to command list
kvm tools: Properly add 'kvm debug' to command list
kvm tools: Update 'kvm pause' documentation
kvm tools: Properly add 'kvm balloon' to command list
kvm tools: Rename command source files
kvm tools: Rename debug options under 'kvm run'
kvm tools: Fix leaked descriptors
kvm tools: Update README
kvm tools: Implement VIRTIO_BLK_T_GET_ID
kvm tools: Update max VCPU limit
kvm tools: Fix warning on 32bit
kvm tools: Set hardcoded MAC to local administered
kvm tools: Use GSI routing
kvm tools: Fix PCI probing
kvm tools: Add a void ptr to be passed to mmio callback
kvm tools: Implement MSI-X for virtio-rng
kvm tools: Add support for 9p2000.u
kvm tools: Use '-d' to boot a directory as a rootfs
kvm tools: Add 'kvm stop'
kvm tools: Remove version file on 'make clean'
kvm tools: Fix PCI masking on probes
kvm tools: Split 'kvm pause' and add 'kvm resume'
kvm tools: Change method of retrieving process name
kvm tools: Use correct size for VESA memory bar
kvm tools: Add kvm__trigger_irq()
kvm tools: Add MSI-X support to virtio-net
kvm tools: Make keyboard termination go through regular termination path
kvm tools: Fix IRQ mapping
kvm tools: Speed up PS/2 mouse detection
kvm tools: Use correct offset for virtio-net config space
kvm tools: Missing braces in BAR index calculation
kvm tools: Print version when running 'kvm --version'
kvm tools: Connect existing command helpers to 'kvm help'
kvm tools: Improve 'kvm stop' parameters
kvm tools: Improve 'kvm resume' parameters
kvm tools: Improve 'kvm pause' parameters
kvm tools: Improve 'kvm debug' parameters
kvm tools: Improve 'kvm balloon' parameters
kvm tools: Fix wrong kill() PID in commands
kvm tools: Add 'kvm stat' command
kvm tools: Use correct data type for pid
kvm tools: Guest kernel compatability
kvm tools: Add guest compatability warning to virtio-rng
kvm tools: Add guest compatability warning to virtio-blk
kvm tools: Add guest compatability warning to virtio-9p
kvm tools: Add guest compatability warning to virtio-net
kvm tools: Add guest compatability warning to virtio-console
kvm tools: Add guest compatability warning to virtio-balloon
kvm tools: Add helper to retrieve the field used in virtio config space
kvm tools: Fix offset calculation for config space and MSI-X
kvm tools: Separate virtio-pci layer
kvm tools: Separate virtio-pci layer out of virtio-rng
kvm tools: Separate virtio-pci layer out of virtio-net
kvm tools: Separate virtio-pci layer out of virtio-balloon
kvm tools: Separate virtio-pci layer out of virtio-9p
kvm tools: Separate virtio-pci layer out of virtio-blk
kvm tools: Move ioeventfd registration to virtio-pci
kvm tools: Separate pci layer out of virtio-console
kvm tools: MSI-X fixes
kvm tools: Add ivshmem device
kvm tools: Remove unconditional warning in ivshmem
kvm tools: Fix 32bit warnings
kvm tools: Attach default 'root=' only if required
kvm tools: Teach 'run' to handle guestfs
kvm tools: Add guestfs network autoconfiguration
kvm tools: Modify 'kvm run' to use virt fs
kvm tools: Fix compat message formatting
kvm tools: Fix 32bit build errors
kvm tools: Use kernel dhcp for network autoconfiguration
kvm tools: Don't use i8042 AUX port
kvm tools: Allow remapping guest TTY into host PTS
kvm tools: Don't copy network autoconfiguration script
kvm tools: Use host's resolv.conf within the guest
kvm tools: Use correct subsys id in virtio-pci
kvm tools: Fix INTx handling
kvm tools: Document steps to debug kernel using KGDB
kvm tools: Set active console before running /bin/sh
kvm tools: Support multiple net devices
kvm tools: Fix spelling mistake
kvm tools: Use compat message per device instead of per instance
kvm tools: Improve compat message
kvm tools: Add basic help when starting 'kvm' without args
kvm tools: Add help and info messages to 'kvm setup'
kvm tools: Modify 'kvm setup' parameters
kvm tools: Add option to list rootfs in 'kvm list'
kvm tools: Enable fast string operations
kvm tools: Switch to using UNIX sockets instead of signals
kvm tools: Move memory stat print to client
kvm tools: Allow piping debug output to file descriptor
kvm tools: Simplify msi message handling
kvm tools: Add method to stop ipc thread
kvm tools: Fix SDL exit on window close
kvm tools: Avoid overwriting socket files with same name
kvm tools: Handle only relevant events in epoll
kvm tools: Cleanup ghost socket files
kvm tools: Switch to using an enum for disk image types
kvm tools: Remove the non-iov interface from disk image ops
kvm tools: Modify disk ops usage
kvm tools: Modify behaviour on missing ops ptr
kvm tools: Add optional callback on disk op completion
kvm tools: Remove qcow nowrite function
kvm tools: Split io request from completion
kvm tools: Hook virtio-blk completion to disk op completion
kvm tools: Add aio read write functions
kvm tools: Use native vectored AIO in virtio-blk
config: Add 'make kvmconfig'
Xiao Guangrong (2):
kvm tools: fix repeated io emulation
kvm tools: remove count in io emulation callbacks
MAINTAINERS | 8 +
arch/x86/Kconfig | 27 +
include/net/9p/9p.h | 183 +----
scripts/kconfig/Makefile | 6 +-
tools/kvm/.gitignore | 10 +
tools/kvm/CREDITS-Git | 30 +
tools/kvm/Documentation/kernel-debugging.txt | 15 +
tools/kvm/Documentation/kvm-balloon.txt | 24 +
tools/kvm/Documentation/kvm-debug.txt | 16 +
tools/kvm/Documentation/kvm-list.txt | 16 +
tools/kvm/Documentation/kvm-pause.txt | 16 +
tools/kvm/Documentation/kvm-resume.txt | 16 +
tools/kvm/Documentation/kvm-run.txt | 62 ++
tools/kvm/Documentation/kvm-setup.txt | 15 +
tools/kvm/Documentation/kvm-stat.txt | 19 +
tools/kvm/Documentation/kvm-stop.txt | 16 +
tools/kvm/Documentation/kvm-version.txt | 21 +
tools/kvm/Makefile | 306 ++++++
tools/kvm/README | 109 +++
tools/kvm/bios.c | 174 ++++
tools/kvm/bios/.gitignore | 3 +
tools/kvm/bios/bios-rom.S | 12 +
tools/kvm/bios/e820.c | 72 ++
tools/kvm/bios/entry.S | 92 ++
tools/kvm/bios/gen-offsets.sh | 14 +
tools/kvm/bios/int10.c | 110 +++
tools/kvm/bios/int15.c | 18 +
tools/kvm/bios/local.S | 7 +
tools/kvm/bios/macro.S | 25 +
tools/kvm/bios/memcpy.c | 23 +
tools/kvm/bios/rom.ld.S | 17 +
tools/kvm/builtin-balloon.c | 90 ++
tools/kvm/builtin-debug.c | 89 ++
tools/kvm/builtin-help.c | 62 ++
tools/kvm/builtin-list.c | 156 +++
tools/kvm/builtin-pause.c | 78 ++
tools/kvm/builtin-resume.c | 78 ++
tools/kvm/builtin-run.c | 995 +++++++++++++++++++
tools/kvm/builtin-setup.c | 228 +++++
tools/kvm/builtin-stat.c | 131 +++
tools/kvm/builtin-stop.c | 78 ++
tools/kvm/builtin-version.c | 15 +
tools/kvm/code16gcc.h | 15 +
tools/kvm/command-list.txt | 14 +
tools/kvm/config/feature-tests.mak | 168 ++++
tools/kvm/config/utilities.mak | 188 ++++
tools/kvm/cpuid.c | 55 ++
tools/kvm/disk/blk.c | 39 +
tools/kvm/disk/core.c | 241 +++++
tools/kvm/disk/qcow.c | 1334 ++++++++++++++++++++++++++
tools/kvm/disk/raw.c | 142 +++
tools/kvm/framebuffer.c | 68 ++
tools/kvm/guest/init.c | 46 +
tools/kvm/guest_compat.c | 104 ++
tools/kvm/hw/i8042.c | 348 +++++++
tools/kvm/hw/pci-shmem.c | 261 +++++
tools/kvm/hw/rtc.c | 87 ++
tools/kvm/hw/serial.c | 364 +++++++
tools/kvm/hw/vesa.c | 77 ++
tools/kvm/include/asm/hweight.h | 8 +
tools/kvm/include/bios/memcpy.h | 9 +
tools/kvm/include/kvm/8250-serial.h | 10 +
tools/kvm/include/kvm/apic.h | 17 +
tools/kvm/include/kvm/assembly.h | 24 +
tools/kvm/include/kvm/barrier.h | 15 +
tools/kvm/include/kvm/bios-export.h | 13 +
tools/kvm/include/kvm/bios.h | 88 ++
tools/kvm/include/kvm/boot-protocol.h | 16 +
tools/kvm/include/kvm/brlock.h | 41 +
tools/kvm/include/kvm/builtin-balloon.h | 7 +
tools/kvm/include/kvm/builtin-debug.h | 7 +
tools/kvm/include/kvm/builtin-help.h | 6 +
tools/kvm/include/kvm/builtin-list.h | 7 +
tools/kvm/include/kvm/builtin-pause.h | 7 +
tools/kvm/include/kvm/builtin-resume.h | 7 +
tools/kvm/include/kvm/builtin-run.h | 7 +
tools/kvm/include/kvm/builtin-setup.h | 9 +
tools/kvm/include/kvm/builtin-stat.h | 7 +
tools/kvm/include/kvm/builtin-stop.h | 7 +
tools/kvm/include/kvm/builtin-version.h | 6 +
tools/kvm/include/kvm/compiler.h | 6 +
tools/kvm/include/kvm/cpufeature.h | 41 +
tools/kvm/include/kvm/disk-image.h | 81 ++
tools/kvm/include/kvm/e820.h | 12 +
tools/kvm/include/kvm/framebuffer.h | 34 +
tools/kvm/include/kvm/guest_compat.h | 9 +
tools/kvm/include/kvm/i8042.h | 12 +
tools/kvm/include/kvm/interrupt.h | 26 +
tools/kvm/include/kvm/ioeventfd.h | 27 +
tools/kvm/include/kvm/ioport.h | 65 ++
tools/kvm/include/kvm/irq.h | 31 +
tools/kvm/include/kvm/kvm-cmd.h | 17 +
tools/kvm/include/kvm/kvm-cpu.h | 46 +
tools/kvm/include/kvm/kvm-ipc.h | 27 +
tools/kvm/include/kvm/kvm.h | 108 +++
tools/kvm/include/kvm/mptable.h | 8 +
tools/kvm/include/kvm/mutex.h | 33 +
tools/kvm/include/kvm/parse-options.h | 213 ++++
tools/kvm/include/kvm/pci-shmem.h | 28 +
tools/kvm/include/kvm/pci.h | 74 ++
tools/kvm/include/kvm/qcow.h | 131 +++
tools/kvm/include/kvm/rbtree-interval.h | 27 +
tools/kvm/include/kvm/read-write.h | 43 +
tools/kvm/include/kvm/rtc.h | 6 +
tools/kvm/include/kvm/rwsem.h | 39 +
tools/kvm/include/kvm/sdl.h | 17 +
tools/kvm/include/kvm/segment.h | 21 +
tools/kvm/include/kvm/strbuf.h | 6 +
tools/kvm/include/kvm/symbol.h | 22 +
tools/kvm/include/kvm/term.h | 18 +
tools/kvm/include/kvm/threadpool.h | 37 +
tools/kvm/include/kvm/types.h | 7 +
tools/kvm/include/kvm/uip.h | 358 +++++++
tools/kvm/include/kvm/util.h | 78 ++
tools/kvm/include/kvm/vesa.h | 18 +
tools/kvm/include/kvm/virtio-9p.h | 74 ++
tools/kvm/include/kvm/virtio-balloon.h | 8 +
tools/kvm/include/kvm/virtio-blk.h | 13 +
tools/kvm/include/kvm/virtio-console.h | 9 +
tools/kvm/include/kvm/virtio-net.h | 21 +
tools/kvm/include/kvm/virtio-pci-dev.h | 37 +
tools/kvm/include/kvm/virtio-pci.h | 60 ++
tools/kvm/include/kvm/virtio-rng.h | 9 +
tools/kvm/include/kvm/virtio.h | 62 ++
tools/kvm/include/kvm/vnc.h | 14 +
tools/kvm/include/linux/bitops.h | 33 +
tools/kvm/include/linux/byteorder.h | 7 +
tools/kvm/include/linux/kernel.h | 39 +
tools/kvm/include/linux/module.h | 6 +
tools/kvm/include/linux/prefetch.h | 6 +
tools/kvm/include/linux/types.h | 50 +
tools/kvm/interrupt.c | 27 +
tools/kvm/ioeventfd.c | 128 +++
tools/kvm/ioport.c | 192 ++++
tools/kvm/irq.c | 193 ++++
tools/kvm/kvm-cmd.c | 91 ++
tools/kvm/kvm-cpu.c | 523 ++++++++++
tools/kvm/kvm-ipc.c | 171 ++++
tools/kvm/kvm.c | 821 ++++++++++++++++
tools/kvm/main.c | 19 +
tools/kvm/mmio.c | 132 +++
tools/kvm/mptable.c | 284 ++++++
tools/kvm/net/uip/arp.c | 30 +
tools/kvm/net/uip/buf.c | 114 +++
tools/kvm/net/uip/core.c | 190 ++++
tools/kvm/net/uip/csum.c | 92 ++
tools/kvm/net/uip/dhcp.c | 203 ++++
tools/kvm/net/uip/icmp.c | 29 +
tools/kvm/net/uip/ipv4.c | 29 +
tools/kvm/net/uip/tcp.c | 317 ++++++
tools/kvm/net/uip/udp.c | 236 +++++
tools/kvm/pci.c | 169 ++++
tools/kvm/read-write.c | 344 +++++++
tools/kvm/symbol.c | 98 ++
tools/kvm/term.c | 170 ++++
tools/kvm/tests/Makefile | 19 +
tools/kvm/tests/boot/Makefile | 13 +
tools/kvm/tests/boot/init.c | 11 +
tools/kvm/tests/kernel/.gitignore | 2 +
tools/kvm/tests/kernel/Makefile | 20 +
tools/kvm/tests/kernel/README | 16 +
tools/kvm/tests/kernel/kernel.S | 8 +
tools/kvm/tests/pit/.gitignore | 2 +
tools/kvm/tests/pit/Makefile | 20 +
tools/kvm/tests/pit/README | 16 +
tools/kvm/tests/pit/tick.S | 109 +++
tools/kvm/threadpool.c | 146 +++
tools/kvm/ui/sdl.c | 280 ++++++
tools/kvm/ui/vnc.c | 218 +++++
tools/kvm/util.c | 101 ++
tools/kvm/util/KVMTOOLS-VERSION-GEN | 40 +
tools/kvm/util/generate-cmdlist.sh | 23 +
tools/kvm/util/kvm-ifup-vbr0 | 6 +
tools/kvm/util/parse-options.c | 577 +++++++++++
tools/kvm/util/rbtree-interval.c | 90 ++
tools/kvm/util/set_private_br.sh | 51 +
tools/kvm/util/strbuf.c | 13 +
tools/kvm/virtio/9p-pdu.c | 287 ++++++
tools/kvm/virtio/9p.c | 1266 ++++++++++++++++++++++++
tools/kvm/virtio/balloon.c | 264 +++++
tools/kvm/virtio/blk.c | 288 ++++++
tools/kvm/virtio/console.c | 199 ++++
tools/kvm/virtio/core.c | 111 +++
tools/kvm/virtio/net.c | 423 ++++++++
tools/kvm/virtio/pci.c | 319 ++++++
tools/kvm/virtio/rng.c | 185 ++++
186 files changed, 19071 insertions(+), 179 deletions(-)
create mode 100644 tools/kvm/.gitignore
create mode 100644 tools/kvm/CREDITS-Git
create mode 100644 tools/kvm/Documentation/kernel-debugging.txt
create mode 100644 tools/kvm/Documentation/kvm-balloon.txt
create mode 100644 tools/kvm/Documentation/kvm-debug.txt
create mode 100644 tools/kvm/Documentation/kvm-list.txt
create mode 100644 tools/kvm/Documentation/kvm-pause.txt
create mode 100644 tools/kvm/Documentation/kvm-resume.txt
create mode 100644 tools/kvm/Documentation/kvm-run.txt
create mode 100644 tools/kvm/Documentation/kvm-setup.txt
create mode 100644 tools/kvm/Documentation/kvm-stat.txt
create mode 100644 tools/kvm/Documentation/kvm-stop.txt
create mode 100644 tools/kvm/Documentation/kvm-version.txt
create mode 100644 tools/kvm/Makefile
create mode 100644 tools/kvm/README
create mode 100644 tools/kvm/bios.c
create mode 100644 tools/kvm/bios/.gitignore
create mode 100644 tools/kvm/bios/bios-rom.S
create mode 100644 tools/kvm/bios/e820.c
create mode 100644 tools/kvm/bios/entry.S
create mode 100644 tools/kvm/bios/gen-offsets.sh
create mode 100644 tools/kvm/bios/int10.c
create mode 100644 tools/kvm/bios/int15.c
create mode 100644 tools/kvm/bios/local.S
create mode 100644 tools/kvm/bios/macro.S
create mode 100644 tools/kvm/bios/memcpy.c
create mode 100644 tools/kvm/bios/rom.ld.S
create mode 100644 tools/kvm/builtin-balloon.c
create mode 100644 tools/kvm/builtin-debug.c
create mode 100644 tools/kvm/builtin-help.c
create mode 100644 tools/kvm/builtin-list.c
create mode 100644 tools/kvm/builtin-pause.c
create mode 100644 tools/kvm/builtin-resume.c
create mode 100644 tools/kvm/builtin-run.c
create mode 100644 tools/kvm/builtin-setup.c
create mode 100644 tools/kvm/builtin-stat.c
create mode 100644 tools/kvm/builtin-stop.c
create mode 100644 tools/kvm/builtin-version.c
create mode 100644 tools/kvm/code16gcc.h
create mode 100644 tools/kvm/command-list.txt
create mode 100644 tools/kvm/config/feature-tests.mak
create mode 100644 tools/kvm/config/utilities.mak
create mode 100644 tools/kvm/cpuid.c
create mode 100644 tools/kvm/disk/blk.c
create mode 100644 tools/kvm/disk/core.c
create mode 100644 tools/kvm/disk/qcow.c
create mode 100644 tools/kvm/disk/raw.c
create mode 100644 tools/kvm/framebuffer.c
create mode 100644 tools/kvm/guest/init.c
create mode 100644 tools/kvm/guest_compat.c
create mode 100644 tools/kvm/hw/i8042.c
create mode 100644 tools/kvm/hw/pci-shmem.c
create mode 100644 tools/kvm/hw/rtc.c
create mode 100644 tools/kvm/hw/serial.c
create mode 100644 tools/kvm/hw/vesa.c
create mode 100644 tools/kvm/include/asm/hweight.h
create mode 100644 tools/kvm/include/bios/memcpy.h
create mode 100644 tools/kvm/include/kvm/8250-serial.h
create mode 100644 tools/kvm/include/kvm/apic.h
create mode 100644 tools/kvm/include/kvm/assembly.h
create mode 100644 tools/kvm/include/kvm/barrier.h
create mode 100644 tools/kvm/include/kvm/bios-export.h
create mode 100644 tools/kvm/include/kvm/bios.h
create mode 100644 tools/kvm/include/kvm/boot-protocol.h
create mode 100644 tools/kvm/include/kvm/brlock.h
create mode 100644 tools/kvm/include/kvm/builtin-balloon.h
create mode 100644 tools/kvm/include/kvm/builtin-debug.h
create mode 100644 tools/kvm/include/kvm/builtin-help.h
create mode 100644 tools/kvm/include/kvm/builtin-list.h
create mode 100644 tools/kvm/include/kvm/builtin-pause.h
create mode 100644 tools/kvm/include/kvm/builtin-resume.h
create mode 100644 tools/kvm/include/kvm/builtin-run.h
create mode 100644 tools/kvm/include/kvm/builtin-setup.h
create mode 100644 tools/kvm/include/kvm/builtin-stat.h
create mode 100644 tools/kvm/include/kvm/builtin-stop.h
create mode 100644 tools/kvm/include/kvm/builtin-version.h
create mode 100644 tools/kvm/include/kvm/compiler.h
create mode 100644 tools/kvm/include/kvm/cpufeature.h
create mode 100644 tools/kvm/include/kvm/disk-image.h
create mode 100644 tools/kvm/include/kvm/e820.h
create mode 100644 tools/kvm/include/kvm/framebuffer.h
create mode 100644 tools/kvm/include/kvm/guest_compat.h
create mode 100644 tools/kvm/include/kvm/i8042.h
create mode 100644 tools/kvm/include/kvm/interrupt.h
create mode 100644 tools/kvm/include/kvm/ioeventfd.h
create mode 100644 tools/kvm/include/kvm/ioport.h
create mode 100644 tools/kvm/include/kvm/irq.h
create mode 100644 tools/kvm/include/kvm/kvm-cmd.h
create mode 100644 tools/kvm/include/kvm/kvm-cpu.h
create mode 100644 tools/kvm/include/kvm/kvm-ipc.h
create mode 100644 tools/kvm/include/kvm/kvm.h
create mode 100644 tools/kvm/include/kvm/mptable.h
create mode 100644 tools/kvm/include/kvm/mutex.h
create mode 100644 tools/kvm/include/kvm/parse-options.h
create mode 100644 tools/kvm/include/kvm/pci-shmem.h
create mode 100644 tools/kvm/include/kvm/pci.h
create mode 100644 tools/kvm/include/kvm/qcow.h
create mode 100644 tools/kvm/include/kvm/rbtree-interval.h
create mode 100644 tools/kvm/include/kvm/read-write.h
create mode 100644 tools/kvm/include/kvm/rtc.h
create mode 100644 tools/kvm/include/kvm/rwsem.h
create mode 100644 tools/kvm/include/kvm/sdl.h
create mode 100644 tools/kvm/include/kvm/segment.h
create mode 100644 tools/kvm/include/kvm/strbuf.h
create mode 100644 tools/kvm/include/kvm/symbol.h
create mode 100644 tools/kvm/include/kvm/term.h
create mode 100644 tools/kvm/include/kvm/threadpool.h
create mode 100644 tools/kvm/include/kvm/types.h
create mode 100644 tools/kvm/include/kvm/uip.h
create mode 100644 tools/kvm/include/kvm/util.h
create mode 100644 tools/kvm/include/kvm/vesa.h
create mode 100644 tools/kvm/include/kvm/virtio-9p.h
create mode 100644 tools/kvm/include/kvm/virtio-balloon.h
create mode 100644 tools/kvm/include/kvm/virtio-blk.h
create mode 100644 tools/kvm/include/kvm/virtio-console.h
create mode 100644 tools/kvm/include/kvm/virtio-net.h
create mode 100644 tools/kvm/include/kvm/virtio-pci-dev.h
create mode 100644 tools/kvm/include/kvm/virtio-pci.h
create mode 100644 tools/kvm/include/kvm/virtio-rng.h
create mode 100644 tools/kvm/include/kvm/virtio.h
create mode 100644 tools/kvm/include/kvm/vnc.h
create mode 100644 tools/kvm/include/linux/bitops.h
create mode 100644 tools/kvm/include/linux/byteorder.h
create mode 100644 tools/kvm/include/linux/kernel.h
create mode 100644 tools/kvm/include/linux/module.h
create mode 100644 tools/kvm/include/linux/prefetch.h
create mode 100644 tools/kvm/include/linux/types.h
create mode 100644 tools/kvm/interrupt.c
create mode 100644 tools/kvm/ioeventfd.c
create mode 100644 tools/kvm/ioport.c
create mode 100644 tools/kvm/irq.c
create mode 100644 tools/kvm/kvm-cmd.c
create mode 100644 tools/kvm/kvm-cpu.c
create mode 100644 tools/kvm/kvm-ipc.c
create mode 100644 tools/kvm/kvm.c
create mode 100644 tools/kvm/main.c
create mode 100644 tools/kvm/mmio.c
create mode 100644 tools/kvm/mptable.c
create mode 100644 tools/kvm/net/uip/arp.c
create mode 100644 tools/kvm/net/uip/buf.c
create mode 100644 tools/kvm/net/uip/core.c
create mode 100644 tools/kvm/net/uip/csum.c
create mode 100644 tools/kvm/net/uip/dhcp.c
create mode 100644 tools/kvm/net/uip/icmp.c
create mode 100644 tools/kvm/net/uip/ipv4.c
create mode 100644 tools/kvm/net/uip/tcp.c
create mode 100644 tools/kvm/net/uip/udp.c
create mode 100644 tools/kvm/pci.c
create mode 100644 tools/kvm/read-write.c
create mode 100644 tools/kvm/symbol.c
create mode 100644 tools/kvm/term.c
create mode 100644 tools/kvm/tests/Makefile
create mode 100644 tools/kvm/tests/boot/Makefile
create mode 100644 tools/kvm/tests/boot/init.c
create mode 100644 tools/kvm/tests/kernel/.gitignore
create mode 100644 tools/kvm/tests/kernel/Makefile
create mode 100644 tools/kvm/tests/kernel/README
create mode 100644 tools/kvm/tests/kernel/kernel.S
create mode 100644 tools/kvm/tests/pit/.gitignore
create mode 100644 tools/kvm/tests/pit/Makefile
create mode 100644 tools/kvm/tests/pit/README
create mode 100644 tools/kvm/tests/pit/tick.S
create mode 100644 tools/kvm/threadpool.c
create mode 100644 tools/kvm/ui/sdl.c
create mode 100644 tools/kvm/ui/vnc.c
create mode 100644 tools/kvm/util.c
create mode 100755 tools/kvm/util/KVMTOOLS-VERSION-GEN
create mode 100755 tools/kvm/util/generate-cmdlist.sh
create mode 100755 tools/kvm/util/kvm-ifup-vbr0
create mode 100644 tools/kvm/util/parse-options.c
create mode 100644 tools/kvm/util/rbtree-interval.c
create mode 100755 tools/kvm/util/set_private_br.sh
create mode 100644 tools/kvm/util/strbuf.c
create mode 100644 tools/kvm/virtio/9p-pdu.c
create mode 100644 tools/kvm/virtio/9p.c
create mode 100644 tools/kvm/virtio/balloon.c
create mode 100644 tools/kvm/virtio/blk.c
create mode 100644 tools/kvm/virtio/console.c
create mode 100644 tools/kvm/virtio/core.c
create mode 100644 tools/kvm/virtio/net.c
create mode 100644 tools/kvm/virtio/pci.c
create mode 100644 tools/kvm/virtio/rng.c
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 8:38 [RFC/GIT PULL] Linux KVM tool for v3.2 Pekka Enberg
@ 2011-11-04 12:16 ` Christoph Hellwig
2011-11-04 12:35 ` Pekka Enberg
2011-11-04 14:47 ` Jan Kiszka
` (2 subsequent siblings)
3 siblings, 1 reply; 38+ messages in thread
From: Christoph Hellwig @ 2011-11-04 12:16 UTC (permalink / raw)
To: Pekka Enberg
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm
On Fri, Nov 04, 2011 at 10:38:21AM +0200, Pekka Enberg wrote:
> Hi Linus,
>
> Please consider pulling the latest KVM tool tree from:
There still is absolutely zero reason to throw it in the kernel tree.
Please prepare a nice standalone git repository and tarball for it.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 12:16 ` Christoph Hellwig
@ 2011-11-04 12:35 ` Pekka Enberg
2011-11-04 13:02 ` Christoph Hellwig
2011-11-04 13:14 ` Joerg Roedel
0 siblings, 2 replies; 38+ messages in thread
From: Pekka Enberg @ 2011-11-04 12:35 UTC (permalink / raw)
To: Christoph Hellwig
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm
On Fri, Nov 04, 2011 at 10:38:21AM +0200, Pekka Enberg wrote:
>> Please consider pulling the latest KVM tool tree from:
On Fri, Nov 4, 2011 at 2:16 PM, Christoph Hellwig <hch@infradead.org> wrote:
> There still is absolutely zero reason to throw it in the kernel tree.
>
> Please prepare a nice standalone git repository and tarball for it.
We are reusing kernel code and headers and I am not interested in
copying them over. Living in the kernel tree is part of the design,
whether you like it or not.
Pekka
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 12:35 ` Pekka Enberg
@ 2011-11-04 13:02 ` Christoph Hellwig
2011-11-04 13:32 ` Pekka Enberg
2011-11-04 13:14 ` Joerg Roedel
1 sibling, 1 reply; 38+ messages in thread
From: Christoph Hellwig @ 2011-11-04 13:02 UTC (permalink / raw)
To: Pekka Enberg
Cc: Christoph Hellwig, Linus Torvalds, Avi Kivity, Andrew Morton,
Ingo Molnar, linux-kernel, kvm
On Fri, Nov 04, 2011 at 02:35:18PM +0200, Pekka Enberg wrote:
> We are reusing kernel code and headers and I am not interested in
> copying them over. Living in the kernel tree is part of the design,
> whether you like it or not.
That's pretty much a blanko argument for throwing everything into the
kernel. What's next, throwing your jvm into the kernel because you like
some kernel helpers?
We've been through this a few times - there is no reason why a tool
using the KVM ioctls should be considered close to the kernel - all
other users get away just fine staying out of tree, and that has
helped to keep the ABI stable.
This sounds more like you should create a libkernelutil with useful
data structures we use in the kernel for userspace programs. I'd love
to use that for a few projects, btw.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 12:35 ` Pekka Enberg
2011-11-04 13:02 ` Christoph Hellwig
@ 2011-11-04 13:14 ` Joerg Roedel
1 sibling, 0 replies; 38+ messages in thread
From: Joerg Roedel @ 2011-11-04 13:14 UTC (permalink / raw)
To: Pekka Enberg
Cc: Christoph Hellwig, Linus Torvalds, Avi Kivity, Andrew Morton,
Ingo Molnar, linux-kernel, kvm
On Fri, Nov 04, 2011 at 02:35:18PM +0200, Pekka Enberg wrote:
> We are reusing kernel code and headers and I am not interested in
> copying them over. Living in the kernel tree is part of the design,
> whether you like it or not.
Besides that the KVM tool with its small and clean code-base is a really
nice reference on how to use the KVM kernel interface for anyone willing
to implement its own user-space. As a developer you can learn a lot more
from it as by reading the files on Documentation/. So I think it should
definitly be part of the kernel source tree.
Whether it lives in tools/ or Documentation/ ... I don't care. In tools/
is certainly better for all the developers already using the it for
testing their kernels.
Regards,
Joerg
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 13:02 ` Christoph Hellwig
@ 2011-11-04 13:32 ` Pekka Enberg
2011-11-04 14:42 ` Jan Kiszka
0 siblings, 1 reply; 38+ messages in thread
From: Pekka Enberg @ 2011-11-04 13:32 UTC (permalink / raw)
To: Christoph Hellwig
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm
On Fri, Nov 4, 2011 at 3:02 PM, Christoph Hellwig <hch@infradead.org> wrote:
> That's pretty much a blanko argument for throwing everything into the
> kernel. What's next, throwing your jvm into the kernel because you like
> some kernel helpers?
Please don't give Ingo any funny ideas! :-)
On Fri, Nov 4, 2011 at 3:02 PM, Christoph Hellwig <hch@infradead.org> wrote:
> We've been through this a few times - there is no reason why a tool
> using the KVM ioctls should be considered close to the kernel - all
> other users get away just fine staying out of tree, and that has
> helped to keep the ABI stable.
It's not just about the KVM ABI - it's VESA BIOS data structures,
E820, serial console registers, virtio drivers, kernel utils, and perf
utils.
I know you don't see the benefits of integrated code base but I as a
developer do.
On Fri, Nov 4, 2011 at 3:02 PM, Christoph Hellwig <hch@infradead.org> wrote:
> This sounds more like you should create a libkernelutil with useful
> data structures we use in the kernel for userspace programs. I'd love
> to use that for a few projects, btw.
It's certainly a worthwhile project for someone. I'd love to use that too.
Pekka
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 13:32 ` Pekka Enberg
@ 2011-11-04 14:42 ` Jan Kiszka
2011-11-04 15:16 ` Sasha Levin
2011-11-04 16:13 ` Joerg Roedel
0 siblings, 2 replies; 38+ messages in thread
From: Jan Kiszka @ 2011-11-04 14:42 UTC (permalink / raw)
To: Pekka Enberg
Cc: Christoph Hellwig, Linus Torvalds, Avi Kivity, Andrew Morton,
Ingo Molnar, linux-kernel, kvm
On 2011-11-04 14:32, Pekka Enberg wrote:
> I know you don't see the benefits of integrated code base but I as a
> developer do.
IIRC, this discussion still lacks striking, concrete examples from the
KVM tool vs. QEMU development processes.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 8:38 [RFC/GIT PULL] Linux KVM tool for v3.2 Pekka Enberg
2011-11-04 12:16 ` Christoph Hellwig
@ 2011-11-04 14:47 ` Jan Kiszka
2011-11-08 14:44 ` richard -rw- weinberger
2011-11-10 3:50 ` Anthony Liguori
3 siblings, 0 replies; 38+ messages in thread
From: Jan Kiszka @ 2011-11-04 14:47 UTC (permalink / raw)
To: Pekka Enberg
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm
On 2011-11-04 09:38, Pekka Enberg wrote:
> Finally, I discovered one interesting (and esoteric) use case at LinuxCon
> Europe for the KVM tool:
>
> https://events.linuxfoundation.org/events/linuxcon-europe/sweeney
>
> It turns out they use KVM tool in some parts of their simulation clusters
> because its startup memory footprint is much smaller than Qemu's.
That's mostly due to QEMU's internal guest memory represenation which
will be reworked in the near future (the large amount of device models
for all the QEMU target architectures had to be converted first).
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 14:42 ` Jan Kiszka
@ 2011-11-04 15:16 ` Sasha Levin
2011-11-04 16:26 ` Jan Kiszka
2011-11-04 16:13 ` Joerg Roedel
1 sibling, 1 reply; 38+ messages in thread
From: Sasha Levin @ 2011-11-04 15:16 UTC (permalink / raw)
To: Jan Kiszka
Cc: Pekka Enberg, Christoph Hellwig, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm
On Fri, 2011-11-04 at 15:42 +0100, Jan Kiszka wrote:
> On 2011-11-04 14:32, Pekka Enberg wrote:
> > I know you don't see the benefits of integrated code base but I as a
> > developer do.
>
> IIRC, this discussion still lacks striking, concrete examples from the
> KVM tool vs. QEMU development processes.
I'll give a current example: Michael and Rusty are currently considering
a change in the virtio spec (allowing MMIO config BARs - but thats
irrelevant).
I'll quote what Anthony said about how he sees the big picture of how
this change is going to be implemented - something which we all agree
with:
On Thu, 2011-11-03 at 09:37 -0500, Anthony Liguori wrote:
> Well, what's needed before the spec is changed is an interesting question, but I
> think the main thing is, don't commit any virtio ABI changes to vhost, QEMU,
> NKT, or the kernel until the spec for the change has been committed.
>
> It would be nice to have a working implementation before committing a spec
> change. Even nicer would be to have Acked-by's a maintainer in each area affected.
Which is pretty smart. Get a working implementation before we commit to
a spec.
Now, how would the development process look when the trees aren't
integrated? You'd try to get the kernel side stabilized, then you'd do
your usermode changes, go back to the kernel patches to fix bugs and
things people missed, which would require in turn new patches to the
usermode part, and so until you get 5-6 versions (best case) of this
change in *each* tree.
Add some technical difficulties which just make it uglier, such as
having to copy over new kernel headers into the usermode tool for each
new version you want to send (linux-headers/ dir in QEMU) and you get a
process which is not that pretty anymore :)
How would it look for an integrated project? You'd be working on the
same codebase, one series of patches would take care of both the kernel
changes and the userspace changes, this would speed up iterations and
make testing quite easier.
--
Sasha.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 14:42 ` Jan Kiszka
2011-11-04 15:16 ` Sasha Levin
@ 2011-11-04 16:13 ` Joerg Roedel
2011-11-04 16:42 ` Jan Kiszka
1 sibling, 1 reply; 38+ messages in thread
From: Joerg Roedel @ 2011-11-04 16:13 UTC (permalink / raw)
To: Jan Kiszka
Cc: Pekka Enberg, Christoph Hellwig, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm
On Fri, Nov 04, 2011 at 03:42:22PM +0100, Jan Kiszka wrote:
> On 2011-11-04 14:32, Pekka Enberg wrote:
> > I know you don't see the benefits of integrated code base but I as a
> > developer do.
>
> IIRC, this discussion still lacks striking, concrete examples from the
> KVM tool vs. QEMU development processes.
How does it matter? KVM tool does not compete with QEMU. The use
cases for both programs are different. KVM tool is a helper for kernel
developers during development and additionally good example code on how
to use the KVM kernel interface (because it focuses on KVM only while
QEMU is much more than a KVM userspace).
Therefore it makes sense for KVM tool to be developed in the kernel tree
while it doesn't make sense for QEMU.
Regards,
Joerg
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 15:16 ` Sasha Levin
@ 2011-11-04 16:26 ` Jan Kiszka
2011-11-04 16:48 ` Sasha Levin
0 siblings, 1 reply; 38+ messages in thread
From: Jan Kiszka @ 2011-11-04 16:26 UTC (permalink / raw)
To: Sasha Levin
Cc: Pekka Enberg, Christoph Hellwig, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm
On 2011-11-04 16:16, Sasha Levin wrote:
> On Fri, 2011-11-04 at 15:42 +0100, Jan Kiszka wrote:
>> On 2011-11-04 14:32, Pekka Enberg wrote:
>>> I know you don't see the benefits of integrated code base but I as a
>>> developer do.
>>
>> IIRC, this discussion still lacks striking, concrete examples from the
>> KVM tool vs. QEMU development processes.
>
> I'll give a current example: Michael and Rusty are currently considering
> a change in the virtio spec (allowing MMIO config BARs - but thats
> irrelevant).
>
> I'll quote what Anthony said about how he sees the big picture of how
> this change is going to be implemented - something which we all agree
> with:
>
> On Thu, 2011-11-03 at 09:37 -0500, Anthony Liguori wrote:
>> Well, what's needed before the spec is changed is an interesting question, but I
>> think the main thing is, don't commit any virtio ABI changes to vhost, QEMU,
>> NKT, or the kernel until the spec for the change has been committed.
>>
>> It would be nice to have a working implementation before committing a spec
>> change. Even nicer would be to have Acked-by's a maintainer in each area affected.
>
> Which is pretty smart. Get a working implementation before we commit to
> a spec.
>
> Now, how would the development process look when the trees aren't
> integrated? You'd try to get the kernel side stabilized, then you'd do
> your usermode changes, go back to the kernel patches to fix bugs and
> things people missed, which would require in turn new patches to the
> usermode part, and so until you get 5-6 versions (best case) of this
> change in *each* tree.
This can happen if the kernel API went totally wrong on the first run.
It happens, but not frequently. Or do you see many examples for this in
KVM's history?
I don't remember finding this particularly problematic for any of my own
patch sets. If the API is controversial, you usually try to get that
conceptually resolved instead of updating all bits over and over again.
Once the API is accepted, changes to the implementations become
independent anyway.
>
> Add some technical difficulties which just make it uglier, such as
> having to copy over new kernel headers into the usermode tool for each
> new version you want to send (linux-headers/ dir in QEMU) and you get a
> process which is not that pretty anymore :)
Synching headers has become trivial these days (reloading updated KVM
modules may take more steps ;) ).
>
> How would it look for an integrated project? You'd be working on the
> same codebase, one series of patches would take care of both the kernel
> changes and the userspace changes, this would speed up iterations and
> make testing quite easier.
I can't imagine that the ability to do a single 'make' for a change that
remains split nevertheless justifies merging more user land into the
kernel. You can always set up a meta project for this.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 16:13 ` Joerg Roedel
@ 2011-11-04 16:42 ` Jan Kiszka
2011-11-04 17:41 ` Pekka Enberg
0 siblings, 1 reply; 38+ messages in thread
From: Jan Kiszka @ 2011-11-04 16:42 UTC (permalink / raw)
To: Joerg Roedel
Cc: Pekka Enberg, Christoph Hellwig, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm
On 2011-11-04 17:13, Joerg Roedel wrote:
> On Fri, Nov 04, 2011 at 03:42:22PM +0100, Jan Kiszka wrote:
>> On 2011-11-04 14:32, Pekka Enberg wrote:
>>> I know you don't see the benefits of integrated code base but I as a
>>> developer do.
>>
>> IIRC, this discussion still lacks striking, concrete examples from the
>> KVM tool vs. QEMU development processes.
>
> How does it matter? KVM tool does not compete with QEMU.
I'm still under the impression that it will start to compete for the
reference implementation of KVM changes. I might see ghosts, but I
surely do not want to see this happen for many reasons.
> The use cases for both programs are different.
Really?
> KVM tool is a helper for kernel
> developers during development
Well, 'make' is a helper for kernel development as well...
> and additionally good example code on how
> to use the KVM kernel interface (because it focuses on KVM only while
> QEMU is much more than a KVM userspace).
[ If this is architecturally good or bad would be worth a separate
discussion. ]
> Therefore it makes sense for KVM tool to be developed in the kernel tree
> while it doesn't make sense for QEMU.
And I disagree regarding KVM tool based on the arguments brought forward
so far.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 16:26 ` Jan Kiszka
@ 2011-11-04 16:48 ` Sasha Levin
2011-11-04 17:33 ` Jan Kiszka
0 siblings, 1 reply; 38+ messages in thread
From: Sasha Levin @ 2011-11-04 16:48 UTC (permalink / raw)
To: Jan Kiszka
Cc: Pekka Enberg, Christoph Hellwig, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm
On Fri, 2011-11-04 at 17:26 +0100, Jan Kiszka wrote:
> On 2011-11-04 16:16, Sasha Levin wrote:
> > On Fri, 2011-11-04 at 15:42 +0100, Jan Kiszka wrote:
> >> On 2011-11-04 14:32, Pekka Enberg wrote:
> >>> I know you don't see the benefits of integrated code base but I as a
> >>> developer do.
> >>
> >> IIRC, this discussion still lacks striking, concrete examples from the
> >> KVM tool vs. QEMU development processes.
> >
> > I'll give a current example: Michael and Rusty are currently considering
> > a change in the virtio spec (allowing MMIO config BARs - but thats
> > irrelevant).
> >
> > I'll quote what Anthony said about how he sees the big picture of how
> > this change is going to be implemented - something which we all agree
> > with:
> >
> > On Thu, 2011-11-03 at 09:37 -0500, Anthony Liguori wrote:
> >> Well, what's needed before the spec is changed is an interesting question, but I
> >> think the main thing is, don't commit any virtio ABI changes to vhost, QEMU,
> >> NKT, or the kernel until the spec for the change has been committed.
> >>
> >> It would be nice to have a working implementation before committing a spec
> >> change. Even nicer would be to have Acked-by's a maintainer in each area affected.
> >
> > Which is pretty smart. Get a working implementation before we commit to
> > a spec.
> >
> > Now, how would the development process look when the trees aren't
> > integrated? You'd try to get the kernel side stabilized, then you'd do
> > your usermode changes, go back to the kernel patches to fix bugs and
> > things people missed, which would require in turn new patches to the
> > usermode part, and so until you get 5-6 versions (best case) of this
> > change in *each* tree.
>
> This can happen if the kernel API went totally wrong on the first run.
> It happens, but not frequently. Or do you see many examples for this in
> KVM's history?
A recent example is the NMI emulation fix which reached v6 for both
trees. And from what I gather it's supposed to be a smaller scale change
than the virtio one I've mentioned before.
There are more similar examples.
>
> I don't remember finding this particularly problematic for any of my own
> patch sets. If the API is controversial, you usually try to get that
> conceptually resolved instead of updating all bits over and over again.
> Once the API is accepted, changes to the implementations become
> independent anyway.
>
> >
> > Add some technical difficulties which just make it uglier, such as
> > having to copy over new kernel headers into the usermode tool for each
> > new version you want to send (linux-headers/ dir in QEMU) and you get a
> > process which is not that pretty anymore :)
>
> Synching headers has become trivial these days (reloading updated KVM
> modules may take more steps ;) ).
Yup, it's a simple copy - I didn't say it was hard, I said it's ugly.
> >
> > How would it look for an integrated project? You'd be working on the
> > same codebase, one series of patches would take care of both the kernel
> > changes and the userspace changes, this would speed up iterations and
> > make testing quite easier.
>
> I can't imagine that the ability to do a single 'make' for a change that
> remains split nevertheless justifies merging more user land into the
> kernel. You can always set up a meta project for this.
Thats not the only reason for the merge ofcourse, it's just one which
you asked about.
You can do a meta project, you can't send patches out like that though -
which makes that meaningless.
--
Sasha.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 16:48 ` Sasha Levin
@ 2011-11-04 17:33 ` Jan Kiszka
0 siblings, 0 replies; 38+ messages in thread
From: Jan Kiszka @ 2011-11-04 17:33 UTC (permalink / raw)
To: Sasha Levin
Cc: Pekka Enberg, Christoph Hellwig, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm
On 2011-11-04 17:48, Sasha Levin wrote:
> On Fri, 2011-11-04 at 17:26 +0100, Jan Kiszka wrote:
>> On 2011-11-04 16:16, Sasha Levin wrote:
>>> On Fri, 2011-11-04 at 15:42 +0100, Jan Kiszka wrote:
>>>> On 2011-11-04 14:32, Pekka Enberg wrote:
>>>>> I know you don't see the benefits of integrated code base but I as a
>>>>> developer do.
>>>>
>>>> IIRC, this discussion still lacks striking, concrete examples from the
>>>> KVM tool vs. QEMU development processes.
>>>
>>> I'll give a current example: Michael and Rusty are currently considering
>>> a change in the virtio spec (allowing MMIO config BARs - but thats
>>> irrelevant).
>>>
>>> I'll quote what Anthony said about how he sees the big picture of how
>>> this change is going to be implemented - something which we all agree
>>> with:
>>>
>>> On Thu, 2011-11-03 at 09:37 -0500, Anthony Liguori wrote:
>>>> Well, what's needed before the spec is changed is an interesting question, but I
>>>> think the main thing is, don't commit any virtio ABI changes to vhost, QEMU,
>>>> NKT, or the kernel until the spec for the change has been committed.
>>>>
>>>> It would be nice to have a working implementation before committing a spec
>>>> change. Even nicer would be to have Acked-by's a maintainer in each area affected.
>>>
>>> Which is pretty smart. Get a working implementation before we commit to
>>> a spec.
>>>
>>> Now, how would the development process look when the trees aren't
>>> integrated? You'd try to get the kernel side stabilized, then you'd do
>>> your usermode changes, go back to the kernel patches to fix bugs and
>>> things people missed, which would require in turn new patches to the
>>> usermode part, and so until you get 5-6 versions (best case) of this
>>> change in *each* tree.
>>
>> This can happen if the kernel API went totally wrong on the first run.
>> It happens, but not frequently. Or do you see many examples for this in
>> KVM's history?
>
> A recent example is the NMI emulation fix which reached v6 for both
> trees.
Both series had problems of their own. That contributed to the number of
independent iteration. I would have stopped sending user changes after
the first rounds until the revised kernel side was accepted.
> And from what I gather it's supposed to be a smaller scale change
> than the virtio one I've mentioned before.
>
> There are more similar examples.
>
>>
>> I don't remember finding this particularly problematic for any of my own
>> patch sets. If the API is controversial, you usually try to get that
>> conceptually resolved instead of updating all bits over and over again.
>> Once the API is accepted, changes to the implementations become
>> independent anyway.
>>
>>>
>>> Add some technical difficulties which just make it uglier, such as
>>> having to copy over new kernel headers into the usermode tool for each
>>> new version you want to send (linux-headers/ dir in QEMU) and you get a
>>> process which is not that pretty anymore :)
>>
>> Synching headers has become trivial these days (reloading updated KVM
>> modules may take more steps ;) ).
>
> Yup, it's a simple copy - I didn't say it was hard, I said it's ugly.
I have to install the API headers the kernel generates and then build
against it anyway (not technically, but for cleanness reasons). If that
installation is done temporarily or tracked in some separate version
control is a footnote IMHO.
>
>>>
>>> How would it look for an integrated project? You'd be working on the
>>> same codebase, one series of patches would take care of both the kernel
>>> changes and the userspace changes, this would speed up iterations and
>>> make testing quite easier.
>>
>> I can't imagine that the ability to do a single 'make' for a change that
>> remains split nevertheless justifies merging more user land into the
>> kernel. You can always set up a meta project for this.
>
> Thats not the only reason for the merge ofcourse, it's just one which
> you asked about.
>
> You can do a meta project, you can't send patches out like that though -
> which makes that meaningless.
You can script a lot of things.
In fact, I was more interested in the organizational aspect of this, not
so much in tooling setups.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 16:42 ` Jan Kiszka
@ 2011-11-04 17:41 ` Pekka Enberg
0 siblings, 0 replies; 38+ messages in thread
From: Pekka Enberg @ 2011-11-04 17:41 UTC (permalink / raw)
To: Jan Kiszka
Cc: Joerg Roedel, Christoph Hellwig, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm
On Fri, Nov 4, 2011 at 6:42 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> How does it matter? KVM tool does not compete with QEMU.
>
> I'm still under the impression that it will start to compete for the
> reference implementation of KVM changes. I might see ghosts, but I
> surely do not want to see this happen for many reasons.
Yes, you are indeed seeing ghosts.
Pekka
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 8:38 [RFC/GIT PULL] Linux KVM tool for v3.2 Pekka Enberg
2011-11-04 12:16 ` Christoph Hellwig
2011-11-04 14:47 ` Jan Kiszka
@ 2011-11-08 14:44 ` richard -rw- weinberger
2011-11-08 15:36 ` Pekka Enberg
2011-11-10 3:50 ` Anthony Liguori
3 siblings, 1 reply; 38+ messages in thread
From: richard -rw- weinberger @ 2011-11-08 14:44 UTC (permalink / raw)
To: Pekka Enberg
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm
Pekka,
On Fri, Nov 4, 2011 at 9:38 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> ./kvm run
>
> We also support booting both raw images and QCOW2 images in read-only
> mode:
>
> ./kvm run -d debian_squeeze_amd64_standard.qcow2 -p "root=/dev/vda1"
>
I'm trying to use the kvm tool, but the virtio_blk userland seems to freeze.
Any idea what happens here?
./kvm run -d /scratch/rw/fc14_64_image.qcow2 -p "root=/dev/vda1
nolapic init=/bin/sh notsc hpet=disable debug"
Warning: Forcing read-only support for QCOW
# kvm run -k ../../arch/x86/boot/bzImage -m 320 -c 2 --name guest-9815
eeaarrllyy ccoonnssoollee iinn sseettuupp ccooddee
early console in decompress_kernel
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
[ 0.000000] Linux version 3.1.0-00905-ge0cab7f (rw@inhelltoy) (gcc
version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #3 Tue Nov 8 14:14:24
CET 2011
[ 0.000000] Command line: notsc noapic noacpi pci=conf1 reboot=k
panic=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 console=ttyS0
earlyprintk=serial i8042.noaux=1 root=/dev/vda1 nolapic init=/bin/sh
notsc hpet=disable debug
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 00000000000fffff (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000014000000 (usable)
[ 0.000000] bootconsole [earlyser0] enabled
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI not present or invalid.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000
(usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x14000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges disabled:
[ 0.000000] 00000-FFFFF uncachable
[ 0.000000] MTRR variable ranges disabled:
[ 0.000000] 0 disabled
[ 0.000000] 1 disabled
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106
[ 0.000000] CPU MTRRs all blank - virtualized system.
[ 0.000000] found SMP MP-table at [ffff8800000f0370] f0370
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
[ 0.000000] init_memory_mapping: 0000000000000000-0000000014000000
[ 0.000000] 0000000000 - 0014000000 page 2M
[ 0.000000] kernel direct mapping tables up to 14000000 @ 13ffe000-14000000
[ 0.000000] ACPI Error: A valid RSDP was not found (20110623/tbxfroot-219)
[ 0.000000] [ffffea0000000000-ffffea00005fffff] PMD ->
[ffff880013000000-ffff8800135fffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal empty
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x00014000
[ 0.000000] On node 0 totalpages: 81807
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 5 pages reserved
[ 0.000000] DMA zone: 3914 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 1216 pages used for memmap
[ 0.000000] DMA32 zone: 76608 pages, LIFO batch:15
[ 0.000000] Intel MultiProcessor Specification v1.4
[ 0.000000] MPTABLE: OEM ID: KVMCPU00
[ 0.000000] MPTABLE: Product ID: 0.1
[ 0.000000] MPTABLE: APIC at: 0xFEE00000
[ 0.000000] Processor #0 (Bootup-CPU)
[ 0.000000] Processor #1
[ 0.000000] ACPI: NR_CPUS/possible_cpus limit of 1 reached.
Processor 1/0x1 ignored.
[ 0.000000] IOAPIC[0]: apic_id 3, version 17, address 0xfec00000, GSI 0-23
[ 0.000000] Processors: 1
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] Allocating PCI resources starting at 14000000 (gap:
14000000:ec000000)
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 80522
[ 0.000000] Kernel command line: notsc noapic noacpi pci=conf1
reboot=k panic=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1
console=ttyS0 earlyprintk=serial i8042.noaux=1 root=/dev/vda1 nolapic
init=/bin/sh notsc hpet=disable debug
[ 0.000000] notsc: Kernel compiled with CONFIG_X86_TSC, cannot
disable TSC completely.
[ 0.000000] notsc: Kernel compiled with CONFIG_X86_TSC, cannot
disable TSC completely.
[ 0.000000] PID hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Memory: 304564k/327680k available (3056k kernel code,
452k absent, 22664k reserved, 3527k data, 344k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:288
[ 0.000000] Console: colour *CGA 80x25
[ 0.000000] console [ttyS0] enabled, bootconsole disabled
[ 0.000000] console [ttyS0] enabled, bootconsole disabled
[ 0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat,
Inc., Ingo Molnar
[ 0.000000] ... MAX_LOCKDEP_SUBCLASSES: 8
[ 0.000000] ... MAX_LOCK_DEPTH: 48
[ 0.000000] ... MAX_LOCKDEP_KEYS: 8191
[ 0.000000] ... CLASSHASH_SIZE: 4096
[ 0.000000] ... MAX_LOCKDEP_ENTRIES: 16384
[ 0.000000] ... MAX_LOCKDEP_CHAINS: 32768
[ 0.000000] ... CHAINHASH_SIZE: 16384
[ 0.000000] memory used by lock dependency info: 5855 kB
[ 0.000000] per task-struct memory footprint: 1920 bytes
[ 0.000000] Fast TSC calibration failed
[ 0.000000] TSC: Unable to calibrate against PIT
[ 0.000000] TSC: No reference (HPET/PMTIMER) available
[ 0.000000] Marking TSC unstable due to could not calculate TSC khz
[ 0.020001] Calibrating delay loop... 5656.57 BogoMIPS (lpj=11313152)
[ 0.040002] pid_max: default: 32768 minimum: 301
[ 0.040002] Mount-cache hash table entries: 256
[ 0.044002] CPU: Intel(R) Core(TM)2 CPU X6800 @ 2.93GHz stepping 05
[ 0.048002] Performance Events: unsupported p6 CPU model 15 no PMU
driver, software events only.
[ 0.052002] NMI watchdog disabled (cpu0): hardware events not enabled
[ 0.056003] Apic disabled
[ 0.060003] NET: Registered protocol family 16
[ 0.060003] PCI: Using configuration type 1 for base access
[ 0.064003] bio: create slab <bio-0> at 0
[ 0.068003] ACPI: Interpreter disabled.
[ 0.068003] vgaarb: loaded
[ 0.068003] PCI: Probing PCI hardware
[ 0.072003] PCI: Probing PCI hardware (bus 00)
[ 0.076003] pci 0000:00:01.0: [1af4:1001] type 0 class 0x000180
[ 0.076003] pci 0000:00:01.0: reg 10: [io 0x6200-0x62ff]
[ 0.080004] pci 0000:00:01.0: reg 14: [mem 0xd1000000-0xd10000ff 64bit]
[ 0.084004] pci 0000:00:01.0: reg 1c: [mem 0xd1000100-0xd10001ff 64bit]
[ 0.088004] pci 0000:00:02.0: [1af4:1000] type 0 class 0x000200
[ 0.088004] pci 0000:00:02.0: reg 10: [io 0x6600-0x66ff]
[ 0.092004] pci 0000:00:02.0: reg 14: [mem 0xd1000200-0xd10002ff 64bit]
[ 0.096005] pci 0000:00:02.0: reg 1c: [mem 0xd1000300-0xd10003ff 64bit]
[ 0.100005] PCI: pci_cache_line_size set to 64 bytes
[ 0.100005] reserve RAM buffer: 000000000009fc00 - 000000000009ffff
[ 0.104005] pnp: PnP ACPI: disabled
[ 0.108005] PCI: max bus depth: 0 pci_try_num: 1
[ 0.112006] pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
[ 0.112006] pci_bus 0000:00: resource 1 [mem 0x00000000-0xfffffffff]
[ 0.116006] NET: Registered protocol family 2
[ 0.120006] IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.124007] TCP established hash table entries: 16384 (order: 6,
262144 bytes)
[ 0.128007] TCP bind hash table entries: 16384 (order: 8, 1048576 bytes)
[ 0.136007] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.136007] TCP reno registered
[ 0.140008] UDP hash table entries: 256 (order: 3, 40960 bytes)
[ 0.140008] UDP-Lite hash table entries: 256 (order: 3, 40960 bytes)
[ 0.144008] PCI: CLS 0 bytes, default 64
[ 0.148008] platform rtc_cmos: registered platform RTC device (no
PNP device found)
[ 0.156009] Installing v9fs 9p2000 file system support
[ 0.160009] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 254)
[ 0.160009] io scheduler noop registered
[ 0.164009] io scheduler deadline registered
[ 0.164009] io scheduler cfq registered (default)
[ 0.168009] start plist test
[ 0.168009] end plist test
[ 0.168009] virtio-pci 0000:00:01.0: enabling device (0000 -> 0003)
[ 0.172010] virtio-pci 0000:00:01.0: setting latency timer to 64
[ 0.176010] virtio-pci 0000:00:02.0: enabling device (0000 -> 0003)
[ 0.180010] virtio-pci 0000:00:02.0: setting latency timer to 64
[ 0.200011] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.208012] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.220013] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 0.232013] serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
[ 240.167008] INFO: task swapper:1 blocked for more than 120 seconds.
[ 240.167008] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[ 240.171009] swapper D ffffffff81071c70 0 1 0 0x00000000
[ 240.171009] ffff880012c2d8b0 0000000000000046 ffff880000000000
ffff880012c2d7d0
[ 240.175009] 0000000000000003 ffff880012c2d8b0 ffff880012c30000
ffff880012c2dfd8
[ 240.179009] ffff880012c2c000 ffff880012c2dfd8 ffffffff81614040
ffff880012c30000
[ 240.179009] Call Trace:
[ 240.179009] [<ffffffff810a1307>] ? kmem_cache_alloc+0xa7/0xe0
[ 240.183009] [<ffffffff81057b61>] ? mark_held_locks+0x61/0x150
[ 240.183009] [<ffffffff812f97db>] ? _raw_spin_unlock_irqrestore+0x3b/0x70
[ 240.187010] [<ffffffff81071c70>] ? file_read_actor+0x190/0x190
[ 240.187010] [<ffffffff81057d4d>] ? trace_hardirqs_on_caller+0xfd/0x190
[ 240.191010] [<ffffffff81071c70>] ? file_read_actor+0x190/0x190
[ 240.191010] [<ffffffff812f6eb9>] schedule+0x39/0x50
[ 240.191010] [<ffffffff812f711e>] io_schedule+0x3e/0x60
[ 240.195010] [<ffffffff812f983b>] ? _raw_spin_unlock_irq+0x2b/0x50
[ 240.195010] [<ffffffff81071c79>] sleep_on_page+0x9/0x10
[ 240.199010] [<ffffffff812f76f1>] __wait_on_bit_lock+0x51/0xb0
[ 240.203011] [<ffffffff810d5520>] ? bioset_create+0x280/0x280
[ 240.203011] [<ffffffff810726f1>] __lock_page+0x61/0x70
[ 240.203011] [<ffffffff81045440>] ? autoremove_wake_function+0x40/0x40
[ 240.207011] [<ffffffff81072ac7>] do_read_cache_page+0x177/0x1a0
[ 240.207011] [<ffffffff810d5ac0>] ? blkdev_write_begin+0x20/0x20
[ 240.211011] [<ffffffff81074007>] read_cache_page_async+0x17/0x20
[ 240.211011] [<ffffffff81074049>] read_cache_page+0x9/0x20
[ 240.215011] [<ffffffff810f7a8b>] read_dev_sector+0x2b/0x90
[ 240.215011] [<ffffffff810f7e10>] ? parse_extended+0x2c0/0x2c0
[ 240.219012] [<ffffffff810f7e8a>] msdos_partition+0x7a/0x5b0
[ 240.219012] [<ffffffff811855e4>] ? snprintf+0x34/0x40
[ 240.219012] [<ffffffff810f7e10>] ? parse_extended+0x2c0/0x2c0
[ 240.223012] [<ffffffff810f7758>] rescan_partitions+0x1a8/0x4b0
[ 240.227012] [<ffffffff810d6c4e>] __blkdev_get+0x26e/0x3a0
[ 240.227012] [<ffffffff810d6dce>] blkdev_get+0x4e/0x380
[ 240.227012] [<ffffffff8117df77>] ? kobject_put+0x27/0x60
[ 240.231012] [<ffffffff811731c8>] ? disk_get_part+0x18/0xc0
[ 240.231012] [<ffffffff81173e57>] register_disk+0x157/0x180
[ 240.235013] [<ffffffff81173f25>] add_disk+0xa5/0x300
[ 240.235013] [<ffffffff812f4c5a>] virtblk_probe+0x51f/0x5a3
[ 240.235013] [<ffffffff812f7a9f>] ? mutex_lock_nested+0x22f/0x300
[ 240.239013] [<ffffffff81209830>] ? do_virtblk_request+0x450/0x450
[ 240.239013] [<ffffffff811d2720>] ? vp_reset+0x20/0x20
[ 240.243013] [<ffffffff811d0ee1>] virtio_dev_probe+0xe1/0x140
[ 240.247013] [<ffffffff812013e8>] driver_probe_device+0x88/0x1a0
[ 240.247013] [<ffffffff812015a3>] __driver_attach+0xa3/0xb0
[ 240.247013] [<ffffffff81201500>] ? driver_probe_device+0x1a0/0x1a0
[ 240.251014] [<ffffffff8120011e>] bus_for_each_dev+0x5e/0x90
[ 240.251014] [<ffffffff812016d9>] driver_attach+0x19/0x20
[ 240.255014] [<ffffffff81200888>] bus_add_driver+0x148/0x280
[ 240.255014] [<ffffffff8168d694>] ? firmware_class_init+0x19/0x19
[ 240.255014] [<ffffffff81201f11>] driver_register+0x71/0x140
[ 240.259014] [<ffffffff812f86d9>] ? mutex_unlock+0x9/0x10
[ 240.259014] [<ffffffff8168d694>] ? firmware_class_init+0x19/0x19
[ 240.263014] [<ffffffff811d0fcb>] register_virtio_driver+0x1b/0x30
[ 240.263014] [<ffffffff8168d6ee>] init+0x5a/0x84
[ 240.267015] [<ffffffff81670b15>] do_one_initcall+0x78/0x12b
[ 240.267015] [<ffffffff81670c58>] kernel_init+0x90/0x110
[ 240.271015] [<ffffffff811871ee>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[ 240.271015] [<ffffffff812fb834>] kernel_thread_helper+0x4/0x10
[ 240.275015] [<ffffffff812fa259>] ? retint_restore_args+0xe/0xe
[ 240.275015] [<ffffffff81670bc8>] ? do_one_initcall+0x12b/0x12b
[ 240.275015] [<ffffffff812fb830>] ? gs_change+0xb/0xb
[ 240.279015] 3 locks held by swapper/1:
[ 240.279015] #0: (&__lockdep_no_validate__){......}, at:
[<ffffffff81201553>] __driver_attach+0x53/0xb0
[ 240.283016] #1: (&__lockdep_no_validate__){......}, at:
[<ffffffff81201561>] __driver_attach+0x61/0xb0
[ 240.287016] #2: (&bdev->bd_mutex){+.+.+.}, at:
[<ffffffff810d6a1b>] __blkdev_get+0x3b/0x3a0
--
Thanks,
//richard
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-08 14:44 ` richard -rw- weinberger
@ 2011-11-08 15:36 ` Pekka Enberg
2011-11-08 16:00 ` richard -rw- weinberger
0 siblings, 1 reply; 38+ messages in thread
From: Pekka Enberg @ 2011-11-08 15:36 UTC (permalink / raw)
To: richard -rw- weinberger
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm, Sasha Levin
Hi Richard,
(I'm adding Sasha to the CC.)
On Tue, Nov 8, 2011 at 4:44 PM, richard -rw- weinberger
<richard.weinberger@gmail.com> wrote:
> Pekka,
>
> On Fri, Nov 4, 2011 at 9:38 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>> ./kvm run
>>
>> We also support booting both raw images and QCOW2 images in read-only
>> mode:
>>
>> ./kvm run -d debian_squeeze_amd64_standard.qcow2 -p "root=/dev/vda1"
>>
>
> I'm trying to use the kvm tool, but the virtio_blk userland seems to freeze.
> Any idea what happens here?
>
> ./kvm run -d /scratch/rw/fc14_64_image.qcow2 -p "root=/dev/vda1
> nolapic init=/bin/sh notsc hpet=disable debug"
> Warning: Forcing read-only support for QCOW
> # kvm run -k ../../arch/x86/boot/bzImage -m 320 -c 2 --name guest-9815
> eeaarrllyy ccoonnssoollee iinn sseettuupp ccooddee
>
> early console in decompress_kernel
>
> Decompressing Linux... Parsing ELF... done.
> Booting the kernel.
> [ 0.000000] Linux version 3.1.0-00905-ge0cab7f (rw@inhelltoy) (gcc
> version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #3 Tue Nov 8 14:14:24
> CET 2011
> [ 0.000000] Command line: notsc noapic noacpi pci=conf1 reboot=k
> panic=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 console=ttyS0
> earlyprintk=serial i8042.noaux=1 root=/dev/vda1 nolapic init=/bin/sh
> notsc hpet=disable debug
> [ 0.000000] BIOS-provided physical RAM map:
> [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> [ 0.000000] BIOS-e820: 00000000000f0000 - 00000000000fffff (reserved)
> [ 0.000000] BIOS-e820: 0000000000100000 - 0000000014000000 (usable)
> [ 0.000000] bootconsole [earlyser0] enabled
> [ 0.000000] NX (Execute Disable) protection: active
> [ 0.000000] DMI not present or invalid.
> [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000
> (usable) ==> (reserved)
> [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
> [ 0.000000] No AGP bridge found
> [ 0.000000] last_pfn = 0x14000 max_arch_pfn = 0x400000000
> [ 0.000000] MTRR default type: uncachable
> [ 0.000000] MTRR fixed ranges disabled:
> [ 0.000000] 00000-FFFFF uncachable
> [ 0.000000] MTRR variable ranges disabled:
> [ 0.000000] 0 disabled
> [ 0.000000] 1 disabled
> [ 0.000000] 2 disabled
> [ 0.000000] 3 disabled
> [ 0.000000] 4 disabled
> [ 0.000000] 5 disabled
> [ 0.000000] 6 disabled
> [ 0.000000] 7 disabled
> [ 0.000000] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106
> [ 0.000000] CPU MTRRs all blank - virtualized system.
> [ 0.000000] found SMP MP-table at [ffff8800000f0370] f0370
> [ 0.000000] initial memory mapped : 0 - 20000000
> [ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
> [ 0.000000] init_memory_mapping: 0000000000000000-0000000014000000
> [ 0.000000] 0000000000 - 0014000000 page 2M
> [ 0.000000] kernel direct mapping tables up to 14000000 @ 13ffe000-14000000
> [ 0.000000] ACPI Error: A valid RSDP was not found (20110623/tbxfroot-219)
> [ 0.000000] [ffffea0000000000-ffffea00005fffff] PMD ->
> [ffff880013000000-ffff8800135fffff] on node 0
> [ 0.000000] Zone PFN ranges:
> [ 0.000000] DMA 0x00000010 -> 0x00001000
> [ 0.000000] DMA32 0x00001000 -> 0x00100000
> [ 0.000000] Normal empty
> [ 0.000000] Movable zone start PFN for each node
> [ 0.000000] early_node_map[2] active PFN ranges
> [ 0.000000] 0: 0x00000010 -> 0x0000009f
> [ 0.000000] 0: 0x00000100 -> 0x00014000
> [ 0.000000] On node 0 totalpages: 81807
> [ 0.000000] DMA zone: 64 pages used for memmap
> [ 0.000000] DMA zone: 5 pages reserved
> [ 0.000000] DMA zone: 3914 pages, LIFO batch:0
> [ 0.000000] DMA32 zone: 1216 pages used for memmap
> [ 0.000000] DMA32 zone: 76608 pages, LIFO batch:15
> [ 0.000000] Intel MultiProcessor Specification v1.4
> [ 0.000000] MPTABLE: OEM ID: KVMCPU00
> [ 0.000000] MPTABLE: Product ID: 0.1
> [ 0.000000] MPTABLE: APIC at: 0xFEE00000
> [ 0.000000] Processor #0 (Bootup-CPU)
> [ 0.000000] Processor #1
> [ 0.000000] ACPI: NR_CPUS/possible_cpus limit of 1 reached.
> Processor 1/0x1 ignored.
> [ 0.000000] IOAPIC[0]: apic_id 3, version 17, address 0xfec00000, GSI 0-23
> [ 0.000000] Processors: 1
> [ 0.000000] nr_irqs_gsi: 40
> [ 0.000000] Allocating PCI resources starting at 14000000 (gap:
> 14000000:ec000000)
> [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
> [ 0.000000] pcpu-alloc: [0] 0
> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
> Total pages: 80522
> [ 0.000000] Kernel command line: notsc noapic noacpi pci=conf1
> reboot=k panic=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1
> console=ttyS0 earlyprintk=serial i8042.noaux=1 root=/dev/vda1 nolapic
> init=/bin/sh notsc hpet=disable debug
> [ 0.000000] notsc: Kernel compiled with CONFIG_X86_TSC, cannot
> disable TSC completely.
> [ 0.000000] notsc: Kernel compiled with CONFIG_X86_TSC, cannot
> disable TSC completely.
> [ 0.000000] PID hash table entries: 2048 (order: 2, 16384 bytes)
> [ 0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> [ 0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> [ 0.000000] Checking aperture...
> [ 0.000000] No AGP bridge found
> [ 0.000000] Memory: 304564k/327680k available (3056k kernel code,
> 452k absent, 22664k reserved, 3527k data, 344k init)
> [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0,
> CPUs=1, Nodes=1
> [ 0.000000] NR_IRQS:288
> [ 0.000000] Console: colour *CGA 80x25
> [ 0.000000] console [ttyS0] enabled, bootconsole disabled
> [ 0.000000] console [ttyS0] enabled, bootconsole disabled
> [ 0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat,
> Inc., Ingo Molnar
> [ 0.000000] ... MAX_LOCKDEP_SUBCLASSES: 8
> [ 0.000000] ... MAX_LOCK_DEPTH: 48
> [ 0.000000] ... MAX_LOCKDEP_KEYS: 8191
> [ 0.000000] ... CLASSHASH_SIZE: 4096
> [ 0.000000] ... MAX_LOCKDEP_ENTRIES: 16384
> [ 0.000000] ... MAX_LOCKDEP_CHAINS: 32768
> [ 0.000000] ... CHAINHASH_SIZE: 16384
> [ 0.000000] memory used by lock dependency info: 5855 kB
> [ 0.000000] per task-struct memory footprint: 1920 bytes
> [ 0.000000] Fast TSC calibration failed
> [ 0.000000] TSC: Unable to calibrate against PIT
> [ 0.000000] TSC: No reference (HPET/PMTIMER) available
> [ 0.000000] Marking TSC unstable due to could not calculate TSC khz
> [ 0.020001] Calibrating delay loop... 5656.57 BogoMIPS (lpj=11313152)
> [ 0.040002] pid_max: default: 32768 minimum: 301
> [ 0.040002] Mount-cache hash table entries: 256
> [ 0.044002] CPU: Intel(R) Core(TM)2 CPU X6800 @ 2.93GHz stepping 05
> [ 0.048002] Performance Events: unsupported p6 CPU model 15 no PMU
> driver, software events only.
> [ 0.052002] NMI watchdog disabled (cpu0): hardware events not enabled
> [ 0.056003] Apic disabled
> [ 0.060003] NET: Registered protocol family 16
> [ 0.060003] PCI: Using configuration type 1 for base access
> [ 0.064003] bio: create slab <bio-0> at 0
> [ 0.068003] ACPI: Interpreter disabled.
> [ 0.068003] vgaarb: loaded
> [ 0.068003] PCI: Probing PCI hardware
> [ 0.072003] PCI: Probing PCI hardware (bus 00)
> [ 0.076003] pci 0000:00:01.0: [1af4:1001] type 0 class 0x000180
> [ 0.076003] pci 0000:00:01.0: reg 10: [io 0x6200-0x62ff]
> [ 0.080004] pci 0000:00:01.0: reg 14: [mem 0xd1000000-0xd10000ff 64bit]
> [ 0.084004] pci 0000:00:01.0: reg 1c: [mem 0xd1000100-0xd10001ff 64bit]
> [ 0.088004] pci 0000:00:02.0: [1af4:1000] type 0 class 0x000200
> [ 0.088004] pci 0000:00:02.0: reg 10: [io 0x6600-0x66ff]
> [ 0.092004] pci 0000:00:02.0: reg 14: [mem 0xd1000200-0xd10002ff 64bit]
> [ 0.096005] pci 0000:00:02.0: reg 1c: [mem 0xd1000300-0xd10003ff 64bit]
> [ 0.100005] PCI: pci_cache_line_size set to 64 bytes
> [ 0.100005] reserve RAM buffer: 000000000009fc00 - 000000000009ffff
> [ 0.104005] pnp: PnP ACPI: disabled
> [ 0.108005] PCI: max bus depth: 0 pci_try_num: 1
> [ 0.112006] pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
> [ 0.112006] pci_bus 0000:00: resource 1 [mem 0x00000000-0xfffffffff]
> [ 0.116006] NET: Registered protocol family 2
> [ 0.120006] IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
> [ 0.124007] TCP established hash table entries: 16384 (order: 6,
> 262144 bytes)
> [ 0.128007] TCP bind hash table entries: 16384 (order: 8, 1048576 bytes)
> [ 0.136007] TCP: Hash tables configured (established 16384 bind 16384)
> [ 0.136007] TCP reno registered
> [ 0.140008] UDP hash table entries: 256 (order: 3, 40960 bytes)
> [ 0.140008] UDP-Lite hash table entries: 256 (order: 3, 40960 bytes)
> [ 0.144008] PCI: CLS 0 bytes, default 64
> [ 0.148008] platform rtc_cmos: registered platform RTC device (no
> PNP device found)
> [ 0.156009] Installing v9fs 9p2000 file system support
> [ 0.160009] Block layer SCSI generic (bsg) driver version 0.4
> loaded (major 254)
> [ 0.160009] io scheduler noop registered
> [ 0.164009] io scheduler deadline registered
> [ 0.164009] io scheduler cfq registered (default)
> [ 0.168009] start plist test
> [ 0.168009] end plist test
> [ 0.168009] virtio-pci 0000:00:01.0: enabling device (0000 -> 0003)
> [ 0.172010] virtio-pci 0000:00:01.0: setting latency timer to 64
> [ 0.176010] virtio-pci 0000:00:02.0: enabling device (0000 -> 0003)
> [ 0.180010] virtio-pci 0000:00:02.0: setting latency timer to 64
> [ 0.200011] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> [ 0.208012] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [ 0.220013] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> [ 0.232013] serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
> [ 240.167008] INFO: task swapper:1 blocked for more than 120 seconds.
> [ 240.167008] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [ 240.171009] swapper D ffffffff81071c70 0 1 0 0x00000000
> [ 240.171009] ffff880012c2d8b0 0000000000000046 ffff880000000000
> ffff880012c2d7d0
> [ 240.175009] 0000000000000003 ffff880012c2d8b0 ffff880012c30000
> ffff880012c2dfd8
> [ 240.179009] ffff880012c2c000 ffff880012c2dfd8 ffffffff81614040
> ffff880012c30000
> [ 240.179009] Call Trace:
> [ 240.179009] [<ffffffff810a1307>] ? kmem_cache_alloc+0xa7/0xe0
> [ 240.183009] [<ffffffff81057b61>] ? mark_held_locks+0x61/0x150
> [ 240.183009] [<ffffffff812f97db>] ? _raw_spin_unlock_irqrestore+0x3b/0x70
> [ 240.187010] [<ffffffff81071c70>] ? file_read_actor+0x190/0x190
> [ 240.187010] [<ffffffff81057d4d>] ? trace_hardirqs_on_caller+0xfd/0x190
> [ 240.191010] [<ffffffff81071c70>] ? file_read_actor+0x190/0x190
> [ 240.191010] [<ffffffff812f6eb9>] schedule+0x39/0x50
> [ 240.191010] [<ffffffff812f711e>] io_schedule+0x3e/0x60
> [ 240.195010] [<ffffffff812f983b>] ? _raw_spin_unlock_irq+0x2b/0x50
> [ 240.195010] [<ffffffff81071c79>] sleep_on_page+0x9/0x10
> [ 240.199010] [<ffffffff812f76f1>] __wait_on_bit_lock+0x51/0xb0
> [ 240.203011] [<ffffffff810d5520>] ? bioset_create+0x280/0x280
> [ 240.203011] [<ffffffff810726f1>] __lock_page+0x61/0x70
> [ 240.203011] [<ffffffff81045440>] ? autoremove_wake_function+0x40/0x40
> [ 240.207011] [<ffffffff81072ac7>] do_read_cache_page+0x177/0x1a0
> [ 240.207011] [<ffffffff810d5ac0>] ? blkdev_write_begin+0x20/0x20
> [ 240.211011] [<ffffffff81074007>] read_cache_page_async+0x17/0x20
> [ 240.211011] [<ffffffff81074049>] read_cache_page+0x9/0x20
> [ 240.215011] [<ffffffff810f7a8b>] read_dev_sector+0x2b/0x90
> [ 240.215011] [<ffffffff810f7e10>] ? parse_extended+0x2c0/0x2c0
> [ 240.219012] [<ffffffff810f7e8a>] msdos_partition+0x7a/0x5b0
> [ 240.219012] [<ffffffff811855e4>] ? snprintf+0x34/0x40
> [ 240.219012] [<ffffffff810f7e10>] ? parse_extended+0x2c0/0x2c0
> [ 240.223012] [<ffffffff810f7758>] rescan_partitions+0x1a8/0x4b0
> [ 240.227012] [<ffffffff810d6c4e>] __blkdev_get+0x26e/0x3a0
> [ 240.227012] [<ffffffff810d6dce>] blkdev_get+0x4e/0x380
> [ 240.227012] [<ffffffff8117df77>] ? kobject_put+0x27/0x60
> [ 240.231012] [<ffffffff811731c8>] ? disk_get_part+0x18/0xc0
> [ 240.231012] [<ffffffff81173e57>] register_disk+0x157/0x180
> [ 240.235013] [<ffffffff81173f25>] add_disk+0xa5/0x300
> [ 240.235013] [<ffffffff812f4c5a>] virtblk_probe+0x51f/0x5a3
> [ 240.235013] [<ffffffff812f7a9f>] ? mutex_lock_nested+0x22f/0x300
> [ 240.239013] [<ffffffff81209830>] ? do_virtblk_request+0x450/0x450
> [ 240.239013] [<ffffffff811d2720>] ? vp_reset+0x20/0x20
> [ 240.243013] [<ffffffff811d0ee1>] virtio_dev_probe+0xe1/0x140
> [ 240.247013] [<ffffffff812013e8>] driver_probe_device+0x88/0x1a0
> [ 240.247013] [<ffffffff812015a3>] __driver_attach+0xa3/0xb0
> [ 240.247013] [<ffffffff81201500>] ? driver_probe_device+0x1a0/0x1a0
> [ 240.251014] [<ffffffff8120011e>] bus_for_each_dev+0x5e/0x90
> [ 240.251014] [<ffffffff812016d9>] driver_attach+0x19/0x20
> [ 240.255014] [<ffffffff81200888>] bus_add_driver+0x148/0x280
> [ 240.255014] [<ffffffff8168d694>] ? firmware_class_init+0x19/0x19
> [ 240.255014] [<ffffffff81201f11>] driver_register+0x71/0x140
> [ 240.259014] [<ffffffff812f86d9>] ? mutex_unlock+0x9/0x10
> [ 240.259014] [<ffffffff8168d694>] ? firmware_class_init+0x19/0x19
> [ 240.263014] [<ffffffff811d0fcb>] register_virtio_driver+0x1b/0x30
> [ 240.263014] [<ffffffff8168d6ee>] init+0x5a/0x84
> [ 240.267015] [<ffffffff81670b15>] do_one_initcall+0x78/0x12b
> [ 240.267015] [<ffffffff81670c58>] kernel_init+0x90/0x110
> [ 240.271015] [<ffffffff811871ee>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> [ 240.271015] [<ffffffff812fb834>] kernel_thread_helper+0x4/0x10
> [ 240.275015] [<ffffffff812fa259>] ? retint_restore_args+0xe/0xe
> [ 240.275015] [<ffffffff81670bc8>] ? do_one_initcall+0x12b/0x12b
> [ 240.275015] [<ffffffff812fb830>] ? gs_change+0xb/0xb
> [ 240.279015] 3 locks held by swapper/1:
> [ 240.279015] #0: (&__lockdep_no_validate__){......}, at:
> [<ffffffff81201553>] __driver_attach+0x53/0xb0
> [ 240.283016] #1: (&__lockdep_no_validate__){......}, at:
> [<ffffffff81201561>] __driver_attach+0x61/0xb0
> [ 240.287016] #2: (&bdev->bd_mutex){+.+.+.}, at:
> [<ffffffff810d6a1b>] __blkdev_get+0x3b/0x3a0
Can you please run "kvm debug -a" on a host terminal when the guest
hangs? Please copy the guest output and debug information from the
host terminal. Also, please share your .config with us.
Pekka
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-08 15:36 ` Pekka Enberg
@ 2011-11-08 16:00 ` richard -rw- weinberger
0 siblings, 0 replies; 38+ messages in thread
From: richard -rw- weinberger @ 2011-11-08 16:00 UTC (permalink / raw)
To: Pekka Enberg
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm, Sasha Levin
[-- Attachment #1: Type: text/plain, Size: 13276 bytes --]
Hi Pekka,
On Tue, Nov 8, 2011 at 4:36 PM, Pekka Enberg <penberg@kernel.org> wrote:
> Can you please run "kvm debug -a" on a host terminal when the guest
> hangs? Please copy the guest output and debug information from the
> host terminal. Also, please share your .config with us.
There you go!
---8<---
$ ./kvm run -d /scratch/rw/fc14_64_image.qcow2 -p "root=/dev/vda1
nolapic init=/bin/sh"
Warning: Forcing read-only support for QCOW
# kvm run -k ../../arch/x86/boot/bzImage -m 320 -c 2 --name guest-13045
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.1.0+ (rw@inhelltoy) (gcc version 4.5.1
20100924 (Red Hat 4.5.1-4) (GCC) ) #2 SMP Tue Nov 8 16:06:18 CET 2011
[ 0.000000] Command line: notsc noapic noacpi pci=conf1 reboot=k
panic=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 console=ttyS0
earlyprintk=serial i8042.noaux=1 root=/dev/vda1 nolapic init=/bin/sh
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 00000000000fffff (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000014000000 (usable)
[ 0.000000] bootconsole [earlyser0] enabled
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI not present or invalid.
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x14000 max_arch_pfn = 0x400000000
[ 0.000000] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106
[ 0.000000] CPU MTRRs all blank - virtualized system.
[ 0.000000] found SMP MP-table at [ffff8800000f0370] f0370
[ 0.000000] init_memory_mapping: 0000000000000000-0000000014000000
[ 0.000000] ACPI Error: A valid RSDP was not found (20110623/tbxfroot-219)
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-0000000014000000
[ 0.000000] Initmem setup node 0 0000000000000000-0000000014000000
[ 0.000000] NODE_DATA [0000000013ffb000 - 0000000013ffffff]
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal empty
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x00014000
[ 0.000000] Intel MultiProcessor Specification v1.4
[ 0.000000] MPTABLE: OEM ID: KVMCPU00
[ 0.000000] MPTABLE: Product ID: 0.1
[ 0.000000] MPTABLE: APIC at: 0xFEE00000
[ 0.000000] Processor #0 (Bootup-CPU)
[ 0.000000] Processor #1
[ 0.000000] IOAPIC[0]: apic_id 3, version 17, address 0xfec00000, GSI 0-23
[ 0.000000] Processors: 2
[ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 00000000000ff000
[ 0.000000] PM: Registered nosave memory: 00000000000ff000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 14000000 (gap:
14000000:ec000000)
[ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64
nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 26 pages/cpu @ffff880013c00000 s74624
r8192 d23680 u1048576
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on.
Total pages: 80522
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: notsc noapic noacpi pci=conf1
reboot=k panic=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1
console=ttyS0 earlyprintk=serial i8042.noaux=1 root=/dev/vda1 nolapic
init=/bin/sh
[ 0.000000] notsc: Kernel compiled with CONFIG_X86_TSC, cannot
disable TSC completely.
[ 0.000000] PID hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Memory: 306192k/327680k available (7420k kernel code,
452k absent, 21036k reserved, 5488k data, 648k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0,
CPUs=2, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:4352 nr_irqs:512 16
[ 0.000000] Console: colour *CGA 80x25
[ 0.000000] console [ttyS0] enabled, bootconsole disabled
[ 0.000000] console [ttyS0] enabled, bootconsole disabled
[ 0.000000] Fast TSC calibration failed
[ 0.000000] TSC: Unable to calibrate against PIT
[ 0.000000] TSC: No reference (HPET/PMTIMER) available
[ 0.000000] Marking TSC unstable due to could not calculate TSC khz
[ 0.008999] Calibrating delay loop... 5480.44 BogoMIPS (lpj=2740224)
[ 0.020998] pid_max: default: 32768 minimum: 301
[ 0.022998] Security Framework initialized
[ 0.024998] SELinux: Initializing.
[ 0.026998] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.030997] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.033997] Mount-cache hash table entries: 256
[ 0.036997] Initializing cgroup subsys cpuacct
[ 0.038997] Initializing cgroup subsys freezer
[ 0.040997] mce: CPU supports 32 MCE banks
[ 0.043996] SMP disabled
[ 0.045996] Performance Events: unsupported p6 CPU model 15 no PMU
driver, software events only.
[ 0.049996] Brought up 1 CPUs
[ 0.051995] Total of 1 processors activated (5480.44 BogoMIPS).
[ 0.054995] kworker/u:0 used greatest stack depth: 6288 bytes left
[ 0.056995] RTC time: 15:08:28, date: 11/08/11
[ 0.059994] NET: Registered protocol family 16
[ 0.061994] kworker/u:0 used greatest stack depth: 5968 bytes left
[ 0.064994] PCI: Using configuration type 1 for base access
[ 0.068993] kworker/u:0 used greatest stack depth: 5552 bytes left
[ 0.078993] bio: create slab <bio-0> at 0
[ 0.080992] ACPI: Interpreter disabled.
[ 0.082992] vgaarb: loaded
[ 0.083992] SCSI subsystem initialized
[ 0.086992] usbcore: registered new interface driver usbfs
[ 0.088992] usbcore: registered new interface driver hub
[ 0.090992] usbcore: registered new device driver usb
[ 0.093991] Advanced Linux Sound Architecture Driver Version 1.0.24.
[ 0.095991] PCI: Probing PCI hardware
[ 0.100991] cfg80211: Calling CRDA to update world regulatory domain
[ 0.102990] NetLabel: Initializing
[ 0.103990] NetLabel: domain hash size = 128
[ 0.105990] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.107990] NetLabel: unlabeled traffic allowed by default
[ 0.116989] pnp: PnP ACPI: disabled
[ 0.122988] NET: Registered protocol family 2
[ 0.124988] IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.126988] TCP established hash table entries: 16384 (order: 6,
262144 bytes)
[ 0.129987] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[ 0.131987] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.133987] TCP reno registered
[ 0.134987] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.136986] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.138986] NET: Registered protocol family 1
[ 0.141986] RPC: Registered named UNIX socket transport module.
[ 0.143986] RPC: Registered udp transport module.
[ 0.144985] RPC: Registered tcp transport module.
[ 0.146985] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.148985] platform rtc_cmos: registered platform RTC device (no
PNP device found)
[ 0.151985] microcode: CPU0 sig=0x6f5, pf=0x1, revision=0x0
[ 0.154984] microcode: Microcode Update Driver: v2.00
<tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 0.157984] audit: initializing netlink socket (disabled)
[ 0.159984] type=2000 audit(4476438508.159:1): initialized
[ 0.176981] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.182980] VFS: Disk quotas dquot_6.5.2
[ 0.184980] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.187980] Installing v9fs 9p2000 file system support
[ 0.190979] msgmni has been set to 598
[ 0.192979] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 253)
[ 0.195979] io scheduler noop registered
[ 0.196978] io scheduler deadline registered
[ 0.198978] io scheduler cfq registered (default)
[ 0.201978] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.204977] virtio-pci 0000:00:01.0: enabling device (0000 -> 0003)
[ 0.207977] virtio-pci 0000:00:02.0: enabling device (0000 -> 0003)
[ 0.209977] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
�[ 0.458939] serial8250: ttyS0 at I/O 0x3f8 (irq = 0) is a 16550A
�[ 0.706901] serial8250: ttyS1 at I/O 0x2f8 (irq = 0) is a 16550A
�[ 0.954863] serial8250: ttyS2 at I/O 0x3e8 (irq = 0) is a 16550A
[ 0.956863] Non-volatile memory driver v1.3
[ 0.958862] Linux agpgart interface v0.103
[ 0.960862] [drm] Initialized drm 1.1.0 20060810
[ 0.962862] [drm:i915_init] *ERROR* drm/i915 can't work without
intel_agp module!
[ 0.967861] brd: module loaded
[ 0.970861] loop: module loaded
0x00008000: 00 00 00 00 00 00 00 00
0x00008008: 00 00 00 00 00 00 00 00
0x00008010: 00 00 00 00 00 00 00 00
0x00008018: 00 00 00 00 00 00 00 00
--->8---
$ ./kvm debug -a
#
# vCPU #0's dump:
#
Registers:
----------
rip: ffffffff8100a015 rsp: ffffffff81c01f08 flags: 0000000000000246
rax: 0000000000000000 rbx: ffffffff81c00000 rcx: 00000000ffffffff
rdx: 0000000000000000 rsi: 0000000000000001 rdi: 0000000000000000
rbp: ffffffff81c01f18 r8: 0000000000000000 r9: 0000000000000000
r10: 0000000000000001 r11: 0000000000000000 r12: 0000000000000000
r13: ffffffff81c00000 r14: ffffffffffffffff r15: 0000000000000000
cr0: 000000008005003b cr2: 0000000000000000 cr3: 0000000001c05000
cr4: 00000000000006f0 cr8: 0000000000000000
Segment registers:
------------------
register selector base limit type p dpl db s l g avl
cs 0010 0000000000000000 ffffffff 0b 1 0 0 1 1 1 0
ss 0018 0000000000000000 ffffffff 03 1 0 1 1 0 1 0
ds 0000 0000000000000000 ffffffff 00 0 0 0 0 0 0 0
es 0000 0000000000000000 ffffffff 00 0 0 0 0 0 0 0
fs 0000 0000000000000000 ffffffff 00 0 0 0 0 0 0 0
gs 0000 ffff880013c00000 ffffffff 00 0 0 0 0 0 0 0
tr 0040 ffff880013c0f340 00002087 0b 1 0 0 0 0 0 0
ldt 0000 0000000000000000 ffffffff 00 0 0 0 0 0 0 0
gdt ffff880013c04000 0000007f
idt ffffffff81d48000 00000fff
APIC:
-----
efer: 0000000000000d01 apic base: 00000000fee00900 nmi: enabled
Interrupt bitmap:
-----------------
0000000000000000 0000000000000000 0000000000000000 0000000000000000
Code:
-----
rip: [<ffffffff8100a015>] <unknown>
Stack:
------
#
# vCPU #1's dump:
#
Registers:
----------
rip: 0000000000000200 rsp: 0000000000008000 flags: 0000000000000002
rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000
rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000
rbp: 0000000000008000 r8: 0000000000000000 r9: 0000000000000000
r10: 0000000000000000 r11: 0000000000000000 r12: 0000000000000000
r13: 0000000000000000 r14: 0000000000000000 r15: 0000000000000000
cr0: 0000000060000010 cr2: 0000000000000000 cr3: 0000000000000000
cr4: 0000000000000000 cr8: 0000000000000000
Segment registers:
------------------
register selector base limit type p dpl db s l g avl
cs 1000 0000000000010000 0000ffff 03 1 3 0 1 0 0 0
ss 1000 0000000000010000 0000ffff 03 1 3 0 1 0 0 0
ds 1000 0000000000010000 0000ffff 03 1 3 0 1 0 0 0
es 1000 0000000000010000 0000ffff 03 1 3 0 1 0 0 0
fs 1000 0000000000010000 0000ffff 03 1 3 0 1 0 0 0
gs 1000 0000000000010000 0000ffff 03 1 3 0 1 0 0 0
tr 0000 0000000000000000 0000ffff 0b 1 0 0 0 0 0 0
ldt 0000 0000000000000000 0000ffff 02 1 0 0 0 0 0 0
gdt 0000000000000000 0000ffff
idt 0000000000000000 0000ffff
APIC:
-----
efer: 0000000000000000 apic base: 00000000fee00800 nmi: enabled
Interrupt bitmap:
-----------------
0000000000000000 0000000000000000 0000000000000000 0000000000000000
Code:
-----
rip: [<0000000000000200>] <unknown>
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 19 01 00 14 db 04 00 00 00 00 00 00 00 55 aa <eb> 62 48
64 72 53 0a 02 00 00 00 00 00 10 44 2f ff 81 00 80 00
Stack:
------
---8<---
.config is attached.
Basically it's x86_64 defconfig+kvmconfig+ext2,3,4
--
Thanks,
//richard
[-- Attachment #2: config.kvm --]
[-- Type: application/octet-stream, Size: 77134 bytes --]
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.1.0 Kernel Configuration
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11"
# CONFIG_KTIME_SCALAR is not set
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_HAVE_IRQ_WORK=y
CONFIG_IRQ_WORK=y
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_FHANDLE is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
CONFIG_HAVE_GENERIC_HARDIRQS=y
#
# IRQ subsystem
#
CONFIG_GENERIC_HARDIRQS=y
CONFIG_HAVE_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_PREEMPT_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=64
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_RCU_FAST_NO_HZ is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=18
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_DEVICE is not set
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
# CONFIG_CGROUP_MEM_RES_CTLR is not set
# CONFIG_CGROUP_PERF is not set
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_BLK_CGROUP is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_PERF_COUNTERS is not set
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y
# CONFIG_OPROFILE is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
# CONFIG_JUMP_LABEL is not set
CONFIG_OPTPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_FREEZER=y
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_VSMP is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_KVMTOOL_TEST_ENABLE=y
# CONFIG_PARAVIRT_GUEST is not set
CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=7
CONFIG_X86_CMPXCHG=y
CONFIG_CMPXCHG_LOCAL=y
CONFIG_CMPXCHG_DOUBLE=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
CONFIG_CALGARY_IOMMU=y
CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=64
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
# CONFIG_I8K is not set
CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y
CONFIG_MICROCODE_AMD=y
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
CONFIG_AMD_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=6
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_HAVE_MEMBLOCK=y
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_COMPACTION is not set
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
# CONFIG_TRANSPARENT_HUGEPAGE is not set
# CONFIG_CLEANCACHE is not set
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
CONFIG_X86_RESERVE_LOW=64
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_EFI=y
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
# CONFIG_KEXEC_JUMP is not set
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y
#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATE_CALLBACKS=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_RUNTIME is not set
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_ADVANCED_DEBUG is not set
# CONFIG_PM_TEST_SUSPEND is not set
CONFIG_CAN_PM_TRACE=y
CONFIG_PM_TRACE=y
CONFIG_PM_TRACE_RTC=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
# CONFIG_ACPI_PROCFS_POWER is not set
# CONFIG_ACPI_EC_DEBUGFS is not set
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
# CONFIG_ACPI_HED is not set
# CONFIG_ACPI_CUSTOM_METHOD is not set
# CONFIG_ACPI_APEI is not set
# CONFIG_SFI is not set
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_STAT is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
#
# x86 CPU frequency scaling drivers
#
# CONFIG_X86_PCC_CPUFREQ is not set
CONFIG_X86_ACPI_CPUFREQ=y
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_P4_CLOCKMOD is not set
#
# shared options
#
# CONFIG_X86_SPEEDSTEP_LIB is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_INTEL_IDLE is not set
#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
CONFIG_PCIEPORTBUS=y
# CONFIG_HOTPLUG_PCI_PCIE is not set
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
CONFIG_HT_IRQ=y
CONFIG_PCI_IOV=y
CONFIG_PCI_IOAPIC=y
CONFIG_PCI_LABEL=y
CONFIG_ISA_DMA_API=y
CONFIG_AMD_NB=y
CONFIG_PCCARD=y
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
CONFIG_PCCARD_NONSTATIC=y
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
# CONFIG_RAPIDIO is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_KEYS_COMPAT=y
CONFIG_HAVE_TEXT_POKE_SMP=y
CONFIG_NET=y
CONFIG_COMPAT_NETLINK_MESSAGES=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_FIB_TRIE_STATS is not set
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not set
CONFIG_IP_MROUTE=y
# CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_LRO=y
# CONFIG_INET_DIAG is not set
CONFIG_TCP_CONG_ADVANCED=y
# CONFIG_TCP_CONG_BIC is not set
CONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_TCP_CONG_LP is not set
# CONFIG_TCP_CONG_VENO is not set
# CONFIG_TCP_CONG_YEAH is not set
# CONFIG_TCP_CONG_ILLINOIS is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
CONFIG_INET6_AH=y
CONFIG_INET6_ESP=y
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
CONFIG_INET6_XFRM_MODE_TUNNEL=y
CONFIG_INET6_XFRM_MODE_BEET=y
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_IPV6_SIT=y
# CONFIG_IPV6_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_NETFILTER_ADVANCED is not set
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CONNTRACK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_FTP=y
CONFIG_NF_CONNTRACK_IRC=y
CONFIG_NF_CONNTRACK_SIP=y
CONFIG_NF_CT_NETLINK=y
CONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#
CONFIG_NETFILTER_XT_MARK=m
#
# Xtables targets
#
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=y
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
CONFIG_NETFILTER_XT_TARGET_SECMARK=y
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NETFILTER_XT_MATCH_POLICY=y
CONFIG_NETFILTER_XT_MATCH_STATE=y
# CONFIG_IP_SET is not set
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=y
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_NF_NAT=y
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_NF_NAT_FTP=y
CONFIG_NF_NAT_IRC=y
# CONFIG_NF_NAT_TFTP is not set
# CONFIG_NF_NAT_AMANDA is not set
# CONFIG_NF_NAT_PPTP is not set
# CONFIG_NF_NAT_H323 is not set
CONFIG_NF_NAT_SIP=y
CONFIG_IP_NF_MANGLE=y
#
# IPv6: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV6=y
CONFIG_NF_CONNTRACK_IPV6=y
CONFIG_IP6_NF_IPTABLES=y
CONFIG_IP6_NF_MATCH_IPV6HEADER=y
CONFIG_IP6_NF_TARGET_LOG=y
CONFIG_IP6_NF_FILTER=y
CONFIG_IP6_NF_TARGET_REJECT=y
CONFIG_IP6_NF_MANGLE=y
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
CONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_MULTIQ is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFB is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_DRR is not set
# CONFIG_NET_SCH_MQPRIO is not set
# CONFIG_NET_SCH_CHOKE is not set
# CONFIG_NET_SCH_QFQ is not set
# CONFIG_NET_SCH_INGRESS is not set
#
# Classification
#
CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
# CONFIG_NET_CLS_TCINDEX is not set
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not set
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
# CONFIG_NET_CLS_CGROUP is not set
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
# CONFIG_NET_EMATCH_CMP is not set
# CONFIG_NET_EMATCH_NBYTE is not set
# CONFIG_NET_EMATCH_U32 is not set
# CONFIG_NET_EMATCH_META is not set
# CONFIG_NET_EMATCH_TEXT is not set
CONFIG_NET_CLS_ACT=y
# CONFIG_NET_ACT_POLICE is not set
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
# CONFIG_NET_ACT_IPT is not set
# CONFIG_NET_ACT_NAT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not set
# CONFIG_NET_ACT_CSUM is not set
CONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set
CONFIG_DNS_RESOLVER=y
# CONFIG_BATMAN_ADV is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
CONFIG_HAVE_BPF_JIT=y
# CONFIG_BPF_JIT is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_NET_DROP_MONITOR is not set
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
# CONFIG_AX25 is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_CFG80211=y
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_WEXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
# CONFIG_LIB80211 is not set
CONFIG_MAC80211=y
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_MINSTREL_HT=y
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
# CONFIG_MAC80211_MESH is not set
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
CONFIG_NET_9P=y
CONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_DEBUG is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
CONFIG_DEBUG_DEVRES=y
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_VIRTIO_BLK=y
# CONFIG_BLK_DEV_HD is not set
# CONFIG_BLK_DEV_RBD is not set
# CONFIG_SENSORS_LIS3LV02D is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# CONFIG_SCSI_LOWLEVEL is not set
# CONFIG_SCSI_LOWLEVEL_PCMCIA is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=y
# CONFIG_SATA_AHCI_PLATFORM is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not set
CONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
CONFIG_PATA_AMD=y
# CONFIG_PATA_ARASAN_CF is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
CONFIG_PATA_OLDPIIX=y
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SC1200 is not set
CONFIG_PATA_SCH=y
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_LEGACY is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_CRYPT is not set
# CONFIG_DM_SNAPSHOT is not set
CONFIG_DM_MIRROR=y
# CONFIG_DM_RAID is not set
# CONFIG_DM_LOG_USERSPACE is not set
CONFIG_DM_ZERO=y
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_DM_FLAKEY is not set
# CONFIG_TARGET_CORE is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
# CONFIG_I2O is not set
CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_NETDEVICES=y
# CONFIG_IFB is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
CONFIG_MII=y
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_MICREL_PHY is not set
# CONFIG_FIXED_PHY is not set
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_VORTEX is not set
# CONFIG_TYPHOON is not set
# CONFIG_ETHOC is not set
# CONFIG_DNET is not set
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_PCMCIA_XIRCOM is not set
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_KSZ884X_PCI is not set
# CONFIG_B44 is not set
CONFIG_FORCEDETH=y
CONFIG_E100=y
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
CONFIG_8139TOO_PIO=y
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SMSC9420 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_KS8851_MLL is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
# CONFIG_ATL2 is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
# CONFIG_E1000E is not set
# CONFIG_IP1000 is not set
# CONFIG_IGB is not set
# CONFIG_IGBVF is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
CONFIG_SKY2=y
# CONFIG_SKY2_DEBUG is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=y
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_JME is not set
# CONFIG_STMMAC_ETH is not set
# CONFIG_PCH_GBE is not set
CONFIG_NETDEV_10000=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_CHELSIO_T4 is not set
# CONFIG_CHELSIO_T4VF is not set
# CONFIG_ENIC is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGBEVF is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_VXGE is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
# CONFIG_BNX2X is not set
# CONFIG_QLCNIC is not set
# CONFIG_QLGE is not set
# CONFIG_BNA is not set
# CONFIG_SFC is not set
# CONFIG_BE2NET is not set
CONFIG_TR=y
# CONFIG_IBMOL is not set
# CONFIG_3C359 is not set
# CONFIG_TMS380TR is not set
CONFIG_WLAN=y
# CONFIG_PCMCIA_RAYCS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_AIRO is not set
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not set
# CONFIG_AIRO_CS is not set
# CONFIG_PCMCIA_WL3501 is not set
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not set
# CONFIG_ADM8211 is not set
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_MWL8K is not set
# CONFIG_ATH_COMMON is not set
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_HOSTAP is not set
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_IWLAGN is not set
# CONFIG_IWL4965 is not set
# CONFIG_IWL3945 is not set
# CONFIG_LIBERTAS is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not set
# CONFIG_RT2X00 is not set
# CONFIG_RTL8192CE is not set
# CONFIG_RTL8192SE is not set
# CONFIG_RTL8192DE is not set
# CONFIG_RTL8192CU is not set
# CONFIG_WL1251 is not set
# CONFIG_WL12XX_MENU is not set
# CONFIG_ZD1211RW is not set
# CONFIG_MWIFIEX is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_IPHETH is not set
CONFIG_NET_PCMCIA=y
# CONFIG_PCMCIA_3C589 is not set
# CONFIG_PCMCIA_3C574 is not set
# CONFIG_PCMCIA_FMVJ18X is not set
# CONFIG_PCMCIA_PCNET is not set
# CONFIG_PCMCIA_NMCLAN is not set
# CONFIG_PCMCIA_SMC91C92 is not set
# CONFIG_PCMCIA_XIRC2PS is not set
# CONFIG_PCMCIA_AXNET is not set
# CONFIG_PCMCIA_IBMTR is not set
# CONFIG_WAN is not set
#
# CAIF transport drivers
#
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
# CONFIG_SKFP is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
CONFIG_NETCONSOLE=y
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VIRTIO_NET=y
# CONFIG_VMXNET3 is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y
CONFIG_INPUT_POLLDEV=y
CONFIG_INPUT_SPARSEKMAP=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not set
# CONFIG_JOYSTICK_AS5011 is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not set
CONFIG_INPUT_TABLET=y
# CONFIG_TABLET_USB_ACECAD is not set
# CONFIG_TABLET_USB_AIPTEK is not set
# CONFIG_TABLET_USB_GTCO is not set
# CONFIG_TABLET_USB_HANWANG is not set
# CONFIG_TABLET_USB_KBTAB is not set
# CONFIG_TABLET_USB_WACOM is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_MMA8450 is not set
# CONFIG_INPUT_MPU3050 is not set
# CONFIG_INPUT_APANEL is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_KXTJ9 is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_CMA3000 is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_NOZOMI is not set
# CONFIG_ISI is not set
# CONFIG_N_HDLC is not set
# CONFIG_N_GSM is not set
# CONFIG_TRACE_SINK is not set
CONFIG_DEVKMEM=y
# CONFIG_STALDRV is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MFD_HSU is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_CONSOLE_POLL=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_PCH_UART is not set
# CONFIG_SERIAL_XILINX_PS_UART is not set
CONFIG_HVC_DRIVER=y
CONFIG_VIRTIO_CONSOLE=y
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_INTEL is not set
# CONFIG_HW_RANDOM_AMD is not set
CONFIG_HW_RANDOM_VIA=y
CONFIG_HW_RANDOM_VIRTIO=y
CONFIG_NVRAM=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_IPWIRELESS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_MMAP is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_RAMOOPS is not set
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
# CONFIG_I2C_CHARDEV is not set
# CONFIG_I2C_MUX is not set
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
CONFIG_I2C_I801=y
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_INTEL_MID is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_PXA_PCI is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
# CONFIG_I2C_EG20T is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_SPI is not set
#
# PPS support
#
# CONFIG_PPS is not set
#
# PPS generators support
#
#
# PTP clock support
#
#
# Enable Device Drivers -> PPS to see the PTP clock options.
#
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_BQ20Z75 is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_K10TEMP is not set
# CONFIG_SENSORS_FAM15H_POWER is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_LINEAGE is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LTC4151 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_LM95245 is not set
# CONFIG_SENSORS_MAX16065 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_NTC_THERMISTOR is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_SHT21 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SCH56XX_COMMON is not set
# CONFIG_SENSORS_SCH5627 is not set
# CONFIG_SENSORS_SCH5636 is not set
# CONFIG_SENSORS_ADS1015 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_APPLESMC is not set
#
# ACPI drivers
#
# CONFIG_SENSORS_ACPI_POWER is not set
# CONFIG_SENSORS_ATK0110 is not set
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_CORE is not set
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_F71808E_WDT is not set
# CONFIG_SP5100_TCO is not set
# CONFIG_SC520_WDT is not set
# CONFIG_SBC_FITPC2_WATCHDOG is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_ITCO_WDT is not set
# CONFIG_IT8712F_WDT is not set
# CONFIG_IT87_WDT is not set
# CONFIG_HP_WATCHDOG is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
# CONFIG_NV_TCO is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC_SCH311X_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83697HF_WDT is not set
# CONFIG_W83697UG_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y
#
# Broadcom specific AMBA
#
# CONFIG_BCMA is not set
CONFIG_MFD_SUPPORT=y
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS6507X is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_MFD_STMPE is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_CS5535 is not set
# CONFIG_LPC_SCH is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_VX855 is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_REGULATOR is not set
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
# CONFIG_VGA_SWITCHEROO is not set
CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
CONFIG_DRM_I915=y
CONFIG_DRM_I915_KMS=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_STUB_POULSBO is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=y
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_WMT_GE_ROPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set
CONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
# CONFIG_BACKLIGHT_PROGEAR is not set
# CONFIG_BACKLIGHT_APPLE is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_SEQ_DUMMY=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_HRTIMER=y
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_DMA_SGBUF=y
# CONFIG_SND_RAWMIDI_SEQ is not set
# CONFIG_SND_OPL3_LIB_SEQ is not set
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
# CONFIG_SND_EMU10K1_SEQ is not set
CONFIG_SND_DRIVERS=y
# CONFIG_SND_PCSP is not set
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_ALOOP is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ASIHPI is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_CTXFI is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=y
CONFIG_SND_HDA_PREALLOC_SIZE=64
CONFIG_SND_HDA_HWDEP=y
# CONFIG_SND_HDA_RECONFIG is not set
# CONFIG_SND_HDA_INPUT_BEEP is not set
# CONFIG_SND_HDA_INPUT_JACK is not set
# CONFIG_SND_HDA_PATCH_LOADER is not set
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_ENABLE_REALTEK_QUIRKS=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_HDMI=y
CONFIG_SND_HDA_CODEC_CIRRUS=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CA0110=y
CONFIG_SND_HDA_CODEC_CA0132=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
# CONFIG_SND_HDA_POWER_SAVE is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_LOLA is not set
# CONFIG_SND_LX6464ES is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_US122L is not set
# CONFIG_SND_USB_6FIRE is not set
CONFIG_SND_PCMCIA=y
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
CONFIG_HIDRAW=y
#
# USB Input Devices
#
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
#
# Special HID drivers
#
CONFIG_HID_A4TECH=y
# CONFIG_HID_ACRUX is not set
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
# CONFIG_HID_PRODIKEYS is not set
CONFIG_HID_CYPRESS=y
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
CONFIG_HID_EZKEY=y
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_KEYTOUCH is not set
CONFIG_HID_KYE=y
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
CONFIG_HID_GYRATION=y
# CONFIG_HID_TWINHAN is not set
CONFIG_HID_KENSINGTON=y
# CONFIG_HID_LCPOWER is not set
CONFIG_HID_LOGITECH=y
CONFIG_LOGITECH_FF=y
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWII_FF is not set
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
# CONFIG_HID_MULTITOUCH is not set
CONFIG_HID_NTRIG=y
# CONFIG_HID_ORTEK is not set
CONFIG_HID_PANTHERLORD=y
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PETALYNX=y
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_QUANTA is not set
# CONFIG_HID_ROCCAT is not set
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
# CONFIG_HID_SPEEDLINK is not set
CONFIG_HID_SUNPLUS=y
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
CONFIG_HID_TOPSEED=y
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEBUG=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_MON=y
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_XHCI_HCD is not set
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_REALTEK is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_STORAGE_ENE_UB6250 is not set
# CONFIG_USB_UAS is not set
CONFIG_USB_LIBUSUAL=y
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_GADGET is not set
#
# OTG and related infrastructure
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
#
# LED drivers
#
# CONFIG_LEDS_LM3530 is not set
# CONFIG_LEDS_ALIX2 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_LP5521 is not set
# CONFIG_LEDS_LP5523 is not set
# CONFIG_LEDS_CLEVO_MAIL is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_INTEL_SS4200 is not set
CONFIG_LEDS_TRIGGERS=y
#
# LED Triggers
#
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set
#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=y
# CONFIG_EDAC_MCE_INJ is not set
# CONFIG_EDAC_MM_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
# CONFIG_RTC_HCTOSYS is not set
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
#
# SPI RTC drivers
#
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
#
# on-CPU RTC drivers
#
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#
# CONFIG_INTEL_MID_DMAC is not set
# CONFIG_INTEL_IOATDMA is not set
# CONFIG_TIMB_DMA is not set
# CONFIG_PCH_DMA is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
#
# Virtio drivers
#
CONFIG_VIRTIO_PCI=y
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_STAGING is not set
CONFIG_X86_PLATFORM_DEVICES=y
# CONFIG_ACERHDF is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_HP_ACCEL is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_COMPAL_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_IDEAPAD_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_INTEL_MENLOW is not set
CONFIG_EEEPC_LAPTOP=y
# CONFIG_ACPI_WMI is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_TOPSTAR_LAPTOP is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
# CONFIG_ACPI_CMPC is not set
# CONFIG_INTEL_IPS is not set
# CONFIG_IBM_RTL is not set
# CONFIG_XO15_EBOOK is not set
# CONFIG_SAMSUNG_LAPTOP is not set
# CONFIG_INTEL_OAKTRAIL is not set
# CONFIG_SAMSUNG_Q10 is not set
CONFIG_CLKEVT_I8253=y
CONFIG_I8253_LOCK=y
CONFIG_CLKBLD_I8253=y
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_STATS=y
CONFIG_DMAR=y
# CONFIG_DMAR_DEFAULT_ON is not set
CONFIG_DMAR_FLOPPY_WA=y
# CONFIG_INTR_REMAP is not set
# CONFIG_VIRT_DRIVERS is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_EFI_VARS=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
# CONFIG_DMI_SYSFS is not set
# CONFIG_ISCSI_IBFT_FIND is not set
# CONFIG_SIGMA is not set
# CONFIG_GOOGLE_FIRMWARE is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
# CONFIG_PRINT_QUOTA_WARNING is not set
# CONFIG_QUOTA_DEBUG is not set
CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_QUOTACTL_COMPAT=y
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y
#
# Caches
#
# CONFIG_FSCACHE is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_LOGFS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_PSTORE is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
# CONFIG_NFS_USE_NEW_IDMAPPER is not set
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_9P_FS=y
# CONFIG_9P_FS_POSIX_ACL is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4
# CONFIG_ENABLE_WARN_DEPRECATED is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=2048
CONFIG_MAGIC_SYSRQ=y
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
# CONFIG_LOCKUP_DETECTOR is not set
# CONFIG_HARDLOCKUP_DETECTOR is not set
# CONFIG_DETECT_HUNG_TASK is not set
# CONFIG_SCHED_DEBUG is not set
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_SPARSE_RCU_POINTER is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
CONFIG_DEBUG_STACK_USAGE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=60
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_LKDTM is not set
# CONFIG_CPU_NOTIFIER_ERROR_INJECT is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_EVENT_POWER_TRACING_DEPRECATED=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_FTRACE_SYSCALLS is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_STACK_TRACER is not set
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_KPROBE_EVENT=y
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
# CONFIG_KGDB_TESTS is not set
# CONFIG_KGDB_LOW_LEVEL_TRAP is not set
# CONFIG_KGDB_KDB is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_KMEMCHECK is not set
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_EARLY_PRINTK_DBGP=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_SET_MODULE_RONX is not set
CONFIG_DEBUG_NX_TEST=m
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
# CONFIG_X86_DECODER_SELFTEST is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
CONFIG_DEBUG_BOOT_PARAMS=y
# CONFIG_CPA_DEBUG is not set
CONFIG_OPTIMIZE_INLINING=y
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set
#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
# CONFIG_SECURITY_DMESG_RESTRICT is not set
CONFIG_SECURITY=y
# CONFIG_SECURITYFS is not set
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
# CONFIG_SECURITY_PATH is not set
# CONFIG_INTEL_TXT is not set
CONFIG_LSM_MMAP_MIN_ADDR=65536
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_IMA is not set
CONFIG_DEFAULT_SECURITY_SELINUX=y
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_DEFAULT_SECURITY="selinux"
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y
# CONFIG_CRYPTO_TEST is not set
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set
#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
# CONFIG_CRYPTO_GHASH is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set
#
# Ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_AES_NI_INTEL is not set
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_ARC4=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_ZLIB is not set
# CONFIG_CRYPTO_LZO is not set
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
# CONFIG_VHOST_NET is not set
CONFIG_BINARY_PRINTF=y
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
# CONFIG_CRC_CCITT is not set
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
# CONFIG_CRC8 is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_CPU_RMAP=y
CONFIG_NLATTR=y
CONFIG_AVERAGE=y
# CONFIG_CORDIC is not set
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-04 8:38 [RFC/GIT PULL] Linux KVM tool for v3.2 Pekka Enberg
` (2 preceding siblings ...)
2011-11-08 14:44 ` richard -rw- weinberger
@ 2011-11-10 3:50 ` Anthony Liguori
2011-11-10 6:46 ` Pekka Enberg
3 siblings, 1 reply; 38+ messages in thread
From: Anthony Liguori @ 2011-11-10 3:50 UTC (permalink / raw)
To: Pekka Enberg
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm, Christoph Hellwig
On 11/04/2011 03:38 AM, Pekka Enberg wrote:
> Hi Linus,
>
> Please consider pulling the latest KVM tool tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git kvmtool/for-linus
>
[snip]
> tools/kvm/virtio/net.c | 423 ++++++++
> tools/kvm/virtio/pci.c | 319 ++++++
> tools/kvm/virtio/rng.c | 185 ++++
> 186 files changed, 19071 insertions(+), 179 deletions(-)
So let's assume for a moment that a tool like this should live in the kernel.
What's disturbing about a PULL request like this is the lack of reviewability of
it and the lack of any real review from people that understand what's going on
in this code base.
There are no Acked-by's by people that really understand what the code is doing
or that have domain expertise in filesystems and networking.
There are major functionality short comings in this code base, data corruptors,
and CVEs. I'm not saying that the kvm-tool developers are bad developers, but
the code is not at the appropriate quality level for the kernel. It just looks
pretty on the surface to people that are used to the kernel coding style.
To highlight a few of the issues:
1) The RTC emulation is limited to emulating CMOS and only the few fields used
to store the date and time. If code is added to arch/x86 that tries to make use
of a CMOS field for something useful, kvm-tool is going to fall over.
None of the register A/B/C logic is implemented and none of the timer logic is
implemented. I imagine this requires kernel command line hackery to keep the
kernel from throwing up.
If a kernel change that works on bare metal but breaks kvm-tool because kvm-tool
is incomplete is committed, is that a regression that requires reverting the
change in arch/x86?
2) The qcow2 code is a filesystem implemented in userspace. Image formats are
file systems. It really should be reviewed by the filesystem maintainers.
There is absolutely no attempt made to synchronize the metadata during write
operations which means that you do not have crash consistency of the meta data.
If you experience a power failure or kvm-tool crashs, your image will get
corrupted. I highly doubt a file system would ever be merged into Linux that
was this naive about data integrity.
3) The block probing code replicates a well known CVE from three years ago[1].
Using kvm-tool, a malicious guest could write the qcow2 signature to the zero
sector and use that to attack the host.
I found these three issues in the course of about 30 seconds of looking through
the kvm-tool code. I'm sure if other people with expertise in these areas
looked through the code, they would find a lot more issues. I'm sure I could
find many, many more issues.
This is really the problem with the tools/kvm approach. It circumvents the
normal review process in the kernel because the kernel maintainer structure is
not equipped to properly review userspace code in tools. This is a tool with
data integrity and security implications. It is not a pretty printing routine
or a test case.
While I think it's a neat and potentially useful project, I think long before we
get to the point where we discuss merging it into the kernel, the code quality
has to improve considerably.
[1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2004
Regards,
Anthony Liguori
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 3:50 ` Anthony Liguori
@ 2011-11-10 6:46 ` Pekka Enberg
2011-11-10 7:57 ` Markus Armbruster
2011-11-10 13:43 ` Anthony Liguori
0 siblings, 2 replies; 38+ messages in thread
From: Pekka Enberg @ 2011-11-10 6:46 UTC (permalink / raw)
To: Anthony Liguori
Cc: Pekka Enberg, Linus Torvalds, Avi Kivity, Andrew Morton,
Ingo Molnar, linux-kernel, kvm, Christoph Hellwig
Hi Anthony,
> On 11/04/2011 03:38 AM, Pekka Enberg wrote:
>> Hi Linus,
>>
>> Please consider pulling the latest KVM tool tree from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git
>> kvmtool/for-linus
>>
>
> [snip]
>
>> tools/kvm/virtio/net.c | 423 ++++++++
>> tools/kvm/virtio/pci.c | 319 ++++++
>> tools/kvm/virtio/rng.c | 185 ++++
>> 186 files changed, 19071 insertions(+), 179 deletions(-)
On Wed, 9 Nov 2011, Anthony Liguori wrote:
> So let's assume for a moment that a tool like this should live in the kernel.
> What's disturbing about a PULL request like this is the lack of reviewability
> of it and the lack of any real review from people that understand what's
> going on in this code base.
>
> There are no Acked-by's by people that really understand what the code is
> doing or that have domain expertise in filesystems and networking.
>
> There are major functionality short comings in this code base, data
> corruptors, and CVEs. I'm not saying that the kvm-tool developers are bad
> developers, but the code is not at the appropriate quality level for the
> kernel. It just looks pretty on the surface to people that are used to the
> kernel coding style.
>
> To highlight a few of the issues:
>
> 1) The RTC emulation is limited to emulating CMOS and only the few fields
> used to store the date and time. If code is added to arch/x86 that tries to
> make use of a CMOS field for something useful, kvm-tool is going to fall
> over.
>
> None of the register A/B/C logic is implemented and none of the timer logic
> is implemented. I imagine this requires kernel command line hackery to keep
> the kernel from throwing up.
The "fake it until you make it" design principle is actually something
Ingo suggested early on and has been a really important factor in getting
us to where we are right now.
Not that I disagree with you. I think we should definitely clean up
our hardware emulation code.
> If a kernel change that works on bare metal but breaks kvm-tool because
> kvm-tool is incomplete is committed, is that a regression that requires
> reverting the change in arch/x86?
If it's the KVM tool being silly, obviously not.
> 2) The qcow2 code is a filesystem implemented in userspace. Image formats
> are file systems. It really should be reviewed by the filesystem
> maintainers. There is absolutely no attempt made to synchronize the metadata
> during write operations which means that you do not have crash consistency of
> the meta data.
>
> If you experience a power failure or kvm-tool crashs, your image will get
> corrupted. I highly doubt a file system would ever be merged into Linux that
> was this naive about data integrity.
The QCOW2 is lagging behind because we lost the main developer. It's
forced as read-only for the issues you mention. If you think it's a merge
blocker, we can drop it completely from the tree until the issues are
sorted out.
I personally don't see the issue of having it as a read-only filesystem.
> 3) The block probing code replicates a well known CVE from three years
> ago[1]. Using kvm-tool, a malicious guest could write the qcow2 signature to
> the zero sector and use that to attack the host.
We don't support QCOW2 snapshots so I don't see how the "arbitrary file"
thing can happen.
It's pretty sad though that we're replicating a known security issue :-/
> [1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2004
> I found these three issues in the course of about 30 seconds of looking
> through the kvm-tool code. I'm sure if other people with expertise in these
> areas looked through the code, they would find a lot more issues. I'm sure I
> could find many, many more issues.
Thanks for the review!
Would you be interested in spending another 30 seconds to find out
some more issue? :-)
> This is really the problem with the tools/kvm approach. It circumvents the
> normal review process in the kernel because the kernel maintainer structure
> is not equipped to properly review userspace code in tools. This is a tool
> with data integrity and security implications. It is not a pretty printing
> routine or a test case.
>
> While I think it's a neat and potentially useful project, I think long before
> we get to the point where we discuss merging it into the kernel, the code
> quality has to improve considerably.
It's a problem, sure. I think we have a decent track record in fixing up
issues raised on kvm@. We've probably even fixed most of the issues you
and Avi pointed out very early on because lets face it, you were right and
I was wrong about quite a few things. ;-)
Pekka
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 6:46 ` Pekka Enberg
@ 2011-11-10 7:57 ` Markus Armbruster
2011-11-10 8:21 ` Pekka Enberg
2011-11-10 8:23 ` Sasha Levin
2011-11-10 13:43 ` Anthony Liguori
1 sibling, 2 replies; 38+ messages in thread
From: Markus Armbruster @ 2011-11-10 7:57 UTC (permalink / raw)
To: Pekka Enberg
Cc: Anthony Liguori, Pekka Enberg, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm, Christoph Hellwig
Pekka Enberg <penberg@kernel.org> writes:
> Hi Anthony,
>
>> On 11/04/2011 03:38 AM, Pekka Enberg wrote:
>>> Hi Linus,
>>>
>>> Please consider pulling the latest KVM tool tree from:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git
>>> kvmtool/for-linus
>>>
>>
>> [snip]
>>
>>> tools/kvm/virtio/net.c | 423 ++++++++
>>> tools/kvm/virtio/pci.c | 319 ++++++
>>> tools/kvm/virtio/rng.c | 185 ++++
>>> 186 files changed, 19071 insertions(+), 179 deletions(-)
>
> On Wed, 9 Nov 2011, Anthony Liguori wrote:
>> So let's assume for a moment that a tool like this should live in
>> the kernel. What's disturbing about a PULL request like this is the
>> lack of reviewability of it and the lack of any real review from
>> people that understand what's going on in this code base.
>>
>> There are no Acked-by's by people that really understand what the
>> code is doing or that have domain expertise in filesystems and
>> networking.
>>
>> There are major functionality short comings in this code base, data
>> corruptors, and CVEs. I'm not saying that the kvm-tool developers
>> are bad developers, but the code is not at the appropriate quality
>> level for the kernel. It just looks pretty on the surface to people
>> that are used to the kernel coding style.
>>
>> To highlight a few of the issues:
[...]
>> 2) The qcow2 code is a filesystem implemented in userspace. Image
>> formats are file systems. It really should be reviewed by the
>> filesystem maintainers. There is absolutely no attempt made to
>> synchronize the metadata during write operations which means that
>> you do not have crash consistency of the meta data.
>>
>> If you experience a power failure or kvm-tool crashs, your image
>> will get corrupted. I highly doubt a file system would ever be
>> merged into Linux that was this naive about data integrity.
>
> The QCOW2 is lagging behind because we lost the main developer. It's
> forced as read-only for the issues you mention. If you think it's a
> merge blocker, we can drop it completely from the tree until the
> issues are sorted out.
>
> I personally don't see the issue of having it as a read-only filesystem.
>
>> 3) The block probing code replicates a well known CVE from three
>> years ago[1]. Using kvm-tool, a malicious guest could write the
>> qcow2 signature to the zero sector and use that to attack the host.
>
> We don't support QCOW2 snapshots so I don't see how the "arbitrary
> file" thing can happen.
You don't need snapshots for the hole.
Start with a clean read/write raw image. Probing declares it raw.
Guest writes QCOW signature to it, with a backing file of its choice.
Restart with the same image. Probing declares it QCOW2. Guest can read
the backing file. Oops.
Probing images works when all image types can be probed reliably, and
the guest can't mess with the probing. Requires distinctive signatures
the guest can't change. Raw images spoil it.
> It's pretty sad though that we're replicating a known security issue :-/
Maybe I'm wrong, but I got the impression you've been replicating quite
a few of QEMU's early mistakes.
I hope you can create something better than QEMU, I really, really do.
But to successfully build a second system, you need to learn the right
lessons from the first system. Are you sure you do?
>> [1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2004
[...]
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 7:57 ` Markus Armbruster
@ 2011-11-10 8:21 ` Pekka Enberg
2011-11-10 8:23 ` Sasha Levin
1 sibling, 0 replies; 38+ messages in thread
From: Pekka Enberg @ 2011-11-10 8:21 UTC (permalink / raw)
To: Markus Armbruster
Cc: Anthony Liguori, Linus Torvalds, Avi Kivity, Andrew Morton,
Ingo Molnar, linux-kernel, kvm, Christoph Hellwig
On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
>>> 3) The block probing code replicates a well known CVE from three
>>> years ago[1]. Using kvm-tool, a malicious guest could write the
>>> qcow2 signature to the zero sector and use that to attack the host.
>>
>> We don't support QCOW2 snapshots so I don't see how the "arbitrary
>> file" thing can happen.
>
> You don't need snapshots for the hole.
>
> Start with a clean read/write raw image. Probing declares it raw.
> Guest writes QCOW signature to it, with a backing file of its choice.
>
> Restart with the same image. Probing declares it QCOW2. Guest can read
> the backing file. Oops.
>
> Probing images works when all image types can be probed reliably, and
> the guest can't mess with the probing. Requires distinctive signatures
> the guest can't change. Raw images spoil it.
We don't support that "backing file" thing either. ;-)
On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
>> It's pretty sad though that we're replicating a known security issue :-/
>
> Maybe I'm wrong, but I got the impression you've been replicating quite
> a few of QEMU's early mistakes.
>
> I hope you can create something better than QEMU, I really, really do.
> But to successfully build a second system, you need to learn the right
> lessons from the first system. Are you sure you do?
We do but it's a fair question if we're doing it enough. I don't have
a simple answer to that.
Pekka
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 7:57 ` Markus Armbruster
2011-11-10 8:21 ` Pekka Enberg
@ 2011-11-10 8:23 ` Sasha Levin
2011-11-10 8:28 ` Pekka Enberg
2011-11-10 8:57 ` Markus Armbruster
1 sibling, 2 replies; 38+ messages in thread
From: Sasha Levin @ 2011-11-10 8:23 UTC (permalink / raw)
To: Markus Armbruster
Cc: Pekka Enberg, Anthony Liguori, Pekka Enberg, Linus Torvalds,
Avi Kivity, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
> Pekka Enberg <penberg@kernel.org> writes:
>
>> Hi Anthony,
>>
>>> On 11/04/2011 03:38 AM, Pekka Enberg wrote:
>>>> Hi Linus,
>>>>
>>>> Please consider pulling the latest KVM tool tree from:
>>>>
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git
>>>> kvmtool/for-linus
>>>>
>>>
>>> [snip]
>>>
>>>> tools/kvm/virtio/net.c | 423 ++++++++
>>>> tools/kvm/virtio/pci.c | 319 ++++++
>>>> tools/kvm/virtio/rng.c | 185 ++++
>>>> 186 files changed, 19071 insertions(+), 179 deletions(-)
>>
>> On Wed, 9 Nov 2011, Anthony Liguori wrote:
>>> So let's assume for a moment that a tool like this should live in
>>> the kernel. What's disturbing about a PULL request like this is the
>>> lack of reviewability of it and the lack of any real review from
>>> people that understand what's going on in this code base.
>>>
>>> There are no Acked-by's by people that really understand what the
>>> code is doing or that have domain expertise in filesystems and
>>> networking.
>>>
>>> There are major functionality short comings in this code base, data
>>> corruptors, and CVEs. I'm not saying that the kvm-tool developers
>>> are bad developers, but the code is not at the appropriate quality
>>> level for the kernel. It just looks pretty on the surface to people
>>> that are used to the kernel coding style.
>>>
>>> To highlight a few of the issues:
> [...]
>>> 2) The qcow2 code is a filesystem implemented in userspace. Image
>>> formats are file systems. It really should be reviewed by the
>>> filesystem maintainers. There is absolutely no attempt made to
>>> synchronize the metadata during write operations which means that
>>> you do not have crash consistency of the meta data.
>>>
>>> If you experience a power failure or kvm-tool crashs, your image
>>> will get corrupted. I highly doubt a file system would ever be
>>> merged into Linux that was this naive about data integrity.
>>
>> The QCOW2 is lagging behind because we lost the main developer. It's
>> forced as read-only for the issues you mention. If you think it's a
>> merge blocker, we can drop it completely from the tree until the
>> issues are sorted out.
>>
>> I personally don't see the issue of having it as a read-only filesystem.
>>
>>> 3) The block probing code replicates a well known CVE from three
>>> years ago[1]. Using kvm-tool, a malicious guest could write the
>>> qcow2 signature to the zero sector and use that to attack the host.
>>
>> We don't support QCOW2 snapshots so I don't see how the "arbitrary
>> file" thing can happen.
>
> You don't need snapshots for the hole.
>
> Start with a clean read/write raw image. Probing declares it raw.
> Guest writes QCOW signature to it, with a backing file of its choice.
>
> Restart with the same image. Probing declares it QCOW2. Guest can read
> the backing file. Oops.
Thats an excellent scenario why you'd want to have 'Secure KVM' with
seccomp filters :)
I'm actually not sure why KVM tool got QCOW support in the first
place. You can have anything QCOW provides if you use btrfs (among
several other FSs).
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 8:23 ` Sasha Levin
@ 2011-11-10 8:28 ` Pekka Enberg
2011-11-10 8:57 ` Markus Armbruster
1 sibling, 0 replies; 38+ messages in thread
From: Pekka Enberg @ 2011-11-10 8:28 UTC (permalink / raw)
To: Sasha Levin
Cc: Markus Armbruster, Anthony Liguori, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm, Christoph Hellwig
On Thu, Nov 10, 2011 at 10:23 AM, Sasha Levin <levinsasha928@gmail.com> wrote:
> I'm actually not sure why KVM tool got QCOW support in the first
> place. You can have anything QCOW provides if you use btrfs (among
> several other FSs).
To make it easy for people to use their existing images. I would love
to see native support for other image formats as well.
Pekka
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 8:23 ` Sasha Levin
2011-11-10 8:28 ` Pekka Enberg
@ 2011-11-10 8:57 ` Markus Armbruster
2011-11-10 9:04 ` Sasha Levin
1 sibling, 1 reply; 38+ messages in thread
From: Markus Armbruster @ 2011-11-10 8:57 UTC (permalink / raw)
To: Sasha Levin
Cc: Pekka Enberg, Anthony Liguori, Pekka Enberg, Linus Torvalds,
Avi Kivity, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
Sasha Levin <levinsasha928@gmail.com> writes:
> On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
[...]
>> Start with a clean read/write raw image. Probing declares it raw.
>> Guest writes QCOW signature to it, with a backing file of its choice.
>>
>> Restart with the same image. Probing declares it QCOW2. Guest can read
>> the backing file. Oops.
>
> Thats an excellent scenario why you'd want to have 'Secure KVM' with
> seccomp filters :)
Yup.
For what it's worth, sVirt (use SELinux to secure virtualization)
mitigates the problem. Doesn't mean we couldn't use "Secure KVM".
> I'm actually not sure why KVM tool got QCOW support in the first
> place. You can have anything QCOW provides if you use btrfs (among
> several other FSs).
Maybe it's just me, but isn't it weird to have a filesystem (QCOW2)
sitting in the kernel sources that you can't mount(2)?
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 8:57 ` Markus Armbruster
@ 2011-11-10 9:04 ` Sasha Levin
2011-11-10 9:09 ` Avi Kivity
2011-11-10 9:48 ` Markus Armbruster
0 siblings, 2 replies; 38+ messages in thread
From: Sasha Levin @ 2011-11-10 9:04 UTC (permalink / raw)
To: Markus Armbruster
Cc: Pekka Enberg, Anthony Liguori, Pekka Enberg, Linus Torvalds,
Avi Kivity, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On Thu, Nov 10, 2011 at 10:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
> Sasha Levin <levinsasha928@gmail.com> writes:
>
>> On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
> [...]
>>> Start with a clean read/write raw image. Probing declares it raw.
>>> Guest writes QCOW signature to it, with a backing file of its choice.
>>>
>>> Restart with the same image. Probing declares it QCOW2. Guest can read
>>> the backing file. Oops.
>>
>> Thats an excellent scenario why you'd want to have 'Secure KVM' with
>> seccomp filters :)
>
> Yup.
>
> For what it's worth, sVirt (use SELinux to secure virtualization)
> mitigates the problem. Doesn't mean we couldn't use "Secure KVM".
How does it do it do that? You have a hypervisor trying to read
arbitrary files on the host FS, no?
>> I'm actually not sure why KVM tool got QCOW support in the first
>> place. You can have anything QCOW provides if you use btrfs (among
>> several other FSs).
>
> Maybe it's just me, but isn't it weird to have a filesystem (QCOW2)
> sitting in the kernel sources that you can't mount(2)?
>
It's not really a filesystem, it's a disk image :)
When we did the initial QCOW patches this issue (in some form) came
up. The main concern there was that we shouldn't be duplicating QCOW
code and instead be using a 'libdiskimage' or something like that.
Since nothing like that existed at that time, and splitting it out of
QEMU wasn't trivial, we ended up agreeing on doing a rewrite of the
code.
The point you raised could be solved if we do end up having a usermode
lib which can handle disk images.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 9:04 ` Sasha Levin
@ 2011-11-10 9:09 ` Avi Kivity
2011-11-10 9:14 ` Sasha Levin
2011-11-10 9:48 ` Markus Armbruster
1 sibling, 1 reply; 38+ messages in thread
From: Avi Kivity @ 2011-11-10 9:09 UTC (permalink / raw)
To: Sasha Levin
Cc: Markus Armbruster, Pekka Enberg, Anthony Liguori, Pekka Enberg,
Linus Torvalds, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On 11/10/2011 11:04 AM, Sasha Levin wrote:
> On Thu, Nov 10, 2011 at 10:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
> > Sasha Levin <levinsasha928@gmail.com> writes:
> >
> >> On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
> > [...]
> >>> Start with a clean read/write raw image. Probing declares it raw.
> >>> Guest writes QCOW signature to it, with a backing file of its choice.
> >>>
> >>> Restart with the same image. Probing declares it QCOW2. Guest can read
> >>> the backing file. Oops.
> >>
> >> Thats an excellent scenario why you'd want to have 'Secure KVM' with
> >> seccomp filters :)
> >
> > Yup.
> >
> > For what it's worth, sVirt (use SELinux to secure virtualization)
> > mitigates the problem. Doesn't mean we couldn't use "Secure KVM".
>
> How does it do it do that? You have a hypervisor trying to read
> arbitrary files on the host FS, no?
Trying and failing. sVirt will deny access to all files except those
explicitly allowed by libvirt.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 9:09 ` Avi Kivity
@ 2011-11-10 9:14 ` Sasha Levin
2011-11-10 9:23 ` Avi Kivity
0 siblings, 1 reply; 38+ messages in thread
From: Sasha Levin @ 2011-11-10 9:14 UTC (permalink / raw)
To: Avi Kivity
Cc: Markus Armbruster, Pekka Enberg, Anthony Liguori, Pekka Enberg,
Linus Torvalds, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On Thu, Nov 10, 2011 at 11:09 AM, Avi Kivity <avi@redhat.com> wrote:
> On 11/10/2011 11:04 AM, Sasha Levin wrote:
>> On Thu, Nov 10, 2011 at 10:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
>> > Sasha Levin <levinsasha928@gmail.com> writes:
>> >
>> >> On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
>> > [...]
>> >>> Start with a clean read/write raw image. Probing declares it raw.
>> >>> Guest writes QCOW signature to it, with a backing file of its choice.
>> >>>
>> >>> Restart with the same image. Probing declares it QCOW2. Guest can read
>> >>> the backing file. Oops.
>> >>
>> >> Thats an excellent scenario why you'd want to have 'Secure KVM' with
>> >> seccomp filters :)
>> >
>> > Yup.
>> >
>> > For what it's worth, sVirt (use SELinux to secure virtualization)
>> > mitigates the problem. Doesn't mean we couldn't use "Secure KVM".
>>
>> How does it do it do that? You have a hypervisor trying to read
>> arbitrary files on the host FS, no?
>
> Trying and failing. sVirt will deny access to all files except those
> explicitly allowed by libvirt.
It still allows the guest to read more than enough files which it
shouldn't be reading.
Unless you configure sVirt on a per-guest basis...
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 9:14 ` Sasha Levin
@ 2011-11-10 9:23 ` Avi Kivity
2011-11-10 9:34 ` Sasha Levin
0 siblings, 1 reply; 38+ messages in thread
From: Avi Kivity @ 2011-11-10 9:23 UTC (permalink / raw)
To: Sasha Levin
Cc: Markus Armbruster, Pekka Enberg, Anthony Liguori, Pekka Enberg,
Linus Torvalds, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On 11/10/2011 11:14 AM, Sasha Levin wrote:
> > Trying and failing. sVirt will deny access to all files except those
> > explicitly allowed by libvirt.
>
> It still allows the guest to read more than enough files which it
> shouldn't be reading.
>
> Unless you configure sVirt on a per-guest basis...
sVirt is per-guest.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 9:23 ` Avi Kivity
@ 2011-11-10 9:34 ` Sasha Levin
2011-11-10 9:43 ` Avi Kivity
0 siblings, 1 reply; 38+ messages in thread
From: Sasha Levin @ 2011-11-10 9:34 UTC (permalink / raw)
To: Avi Kivity
Cc: Markus Armbruster, Pekka Enberg, Anthony Liguori, Pekka Enberg,
Linus Torvalds, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On Thu, Nov 10, 2011 at 11:23 AM, Avi Kivity <avi@redhat.com> wrote:
> On 11/10/2011 11:14 AM, Sasha Levin wrote:
>> > Trying and failing. sVirt will deny access to all files except those
>> > explicitly allowed by libvirt.
>>
>> It still allows the guest to read more than enough files which it
>> shouldn't be reading.
>>
>> Unless you configure sVirt on a per-guest basis...
>
> sVirt is per-guest.
It still would mean that the guest can access any file (actually, even
device, no?) the hypervisor can access.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 9:34 ` Sasha Levin
@ 2011-11-10 9:43 ` Avi Kivity
2011-11-10 9:49 ` Sasha Levin
0 siblings, 1 reply; 38+ messages in thread
From: Avi Kivity @ 2011-11-10 9:43 UTC (permalink / raw)
To: Sasha Levin
Cc: Markus Armbruster, Pekka Enberg, Anthony Liguori, Pekka Enberg,
Linus Torvalds, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On 11/10/2011 11:34 AM, Sasha Levin wrote:
> On Thu, Nov 10, 2011 at 11:23 AM, Avi Kivity <avi@redhat.com> wrote:
> > On 11/10/2011 11:14 AM, Sasha Levin wrote:
> >> > Trying and failing. sVirt will deny access to all files except those
> >> > explicitly allowed by libvirt.
> >>
> >> It still allows the guest to read more than enough files which it
> >> shouldn't be reading.
> >>
> >> Unless you configure sVirt on a per-guest basis...
> >
> > sVirt is per-guest.
>
> It still would mean that the guest can access any file (actually, even
> device, no?) the hypervisor can access.
It does, but the hypervisor can only access the guest's images, and a
few internal files (like the qemu-kvm executable and its libraries).
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 9:04 ` Sasha Levin
2011-11-10 9:09 ` Avi Kivity
@ 2011-11-10 9:48 ` Markus Armbruster
1 sibling, 0 replies; 38+ messages in thread
From: Markus Armbruster @ 2011-11-10 9:48 UTC (permalink / raw)
To: Sasha Levin
Cc: Pekka Enberg, Anthony Liguori, Pekka Enberg, Linus Torvalds,
Avi Kivity, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
Sasha Levin <levinsasha928@gmail.com> writes:
> On Thu, Nov 10, 2011 at 10:57 AM, Markus Armbruster <armbru@redhat.com> wrote:
>> Sasha Levin <levinsasha928@gmail.com> writes:
[...]
>>> I'm actually not sure why KVM tool got QCOW support in the first
>>> place. You can have anything QCOW provides if you use btrfs (among
>>> several other FSs).
>>
>> Maybe it's just me, but isn't it weird to have a filesystem (QCOW2)
>> sitting in the kernel sources that you can't mount(2)?
>>
>
> It's not really a filesystem, it's a disk image :)
Sloppy language on my part, sorry about that.
It's a transport for blocks. We have a few of those in the kernel
already: block devices. Including loop devices and DRBD. You use a
filesystem to interpret their contents. The resulting stack is what
gets mounted. Adding another transport for blocks to the kernel that
cannot be used that way strikes me as weird.
[...]
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 9:43 ` Avi Kivity
@ 2011-11-10 9:49 ` Sasha Levin
2011-11-10 9:50 ` Avi Kivity
0 siblings, 1 reply; 38+ messages in thread
From: Sasha Levin @ 2011-11-10 9:49 UTC (permalink / raw)
To: Avi Kivity
Cc: Markus Armbruster, Pekka Enberg, Anthony Liguori, Pekka Enberg,
Linus Torvalds, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On Thu, Nov 10, 2011 at 11:43 AM, Avi Kivity <avi@redhat.com> wrote:
> On 11/10/2011 11:34 AM, Sasha Levin wrote:
>> On Thu, Nov 10, 2011 at 11:23 AM, Avi Kivity <avi@redhat.com> wrote:
>> > On 11/10/2011 11:14 AM, Sasha Levin wrote:
>> >> > Trying and failing. sVirt will deny access to all files except those
>> >> > explicitly allowed by libvirt.
>> >>
>> >> It still allows the guest to read more than enough files which it
>> >> shouldn't be reading.
>> >>
>> >> Unless you configure sVirt on a per-guest basis...
>> >
>> > sVirt is per-guest.
>>
>> It still would mean that the guest can access any file (actually, even
>> device, no?) the hypervisor can access.
>
> It does, but the hypervisor can only access the guest's images, and a
> few internal files (like the qemu-kvm executable and its libraries).
What about devices? You let the guest read and write to devices as
well (/dev/kvm for example, or network devices).
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 9:49 ` Sasha Levin
@ 2011-11-10 9:50 ` Avi Kivity
0 siblings, 0 replies; 38+ messages in thread
From: Avi Kivity @ 2011-11-10 9:50 UTC (permalink / raw)
To: Sasha Levin
Cc: Markus Armbruster, Pekka Enberg, Anthony Liguori, Pekka Enberg,
Linus Torvalds, Andrew Morton, Ingo Molnar, linux-kernel, kvm,
Christoph Hellwig
On 11/10/2011 11:49 AM, Sasha Levin wrote:
> >
> > It does, but the hypervisor can only access the guest's images, and a
> > few internal files (like the qemu-kvm executable and its libraries).
>
> What about devices? You let the guest read and write to devices as
> well (/dev/kvm for example, or network devices).
They're all protected. /dev/kvm is obviously rw for anyone, but it
can't be used to transfer information.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 6:46 ` Pekka Enberg
2011-11-10 7:57 ` Markus Armbruster
@ 2011-11-10 13:43 ` Anthony Liguori
2011-11-10 13:56 ` Pekka Enberg
1 sibling, 1 reply; 38+ messages in thread
From: Anthony Liguori @ 2011-11-10 13:43 UTC (permalink / raw)
To: Pekka Enberg
Cc: Pekka Enberg, Linus Torvalds, Avi Kivity, Andrew Morton,
Ingo Molnar, linux-kernel, kvm, Christoph Hellwig
On 11/10/2011 12:46 AM, Pekka Enberg wrote:
> Hi Anthony,
>
>> 1) The RTC emulation is limited to emulating CMOS and only the few fields used
>> to store the date and time. If code is added to arch/x86 that tries to make
>> use of a CMOS field for something useful, kvm-tool is going to fall over.
>>
>> None of the register A/B/C logic is implemented and none of the timer logic is
>> implemented. I imagine this requires kernel command line hackery to keep the
>> kernel from throwing up.
>
> The "fake it until you make it" design principle is actually something Ingo
> suggested early on and has been a really important factor in getting us to where
> we are right now.
>
> Not that I disagree with you. I think we should definitely clean up our hardware
> emulation code.
>
>> If a kernel change that works on bare metal but breaks kvm-tool because
>> kvm-tool is incomplete is committed, is that a regression that requires
>> reverting the change in arch/x86?
>
> If it's the KVM tool being silly, obviously not.
>
>> 2) The qcow2 code is a filesystem implemented in userspace. Image formats are
>> file systems. It really should be reviewed by the filesystem maintainers.
>> There is absolutely no attempt made to synchronize the metadata during write
>> operations which means that you do not have crash consistency of the meta data.
>>
>> If you experience a power failure or kvm-tool crashs, your image will get
>> corrupted. I highly doubt a file system would ever be merged into Linux that
>> was this naive about data integrity.
>
> The QCOW2 is lagging behind because we lost the main developer. It's forced as
> read-only for the issues you mention. If you think it's a merge blocker, we can
> drop it completely from the tree until the issues are sorted out.
It's not just the qcow2 implementation or even the block layer. This pull
requests adds a userspace TCP/IP stack to the kernel and yet netdev isn't on the
CC and there are no Ack's from anyone from the networking stack. I'm fairly
sure if they knew what was happening here they would object.
And the implementation isn't even strictly needed. You can just as well achieve
the same goal using tun/tap with a privileged helper[1].
>> I found these three issues in the course of about 30 seconds of looking
>> through the kvm-tool code. I'm sure if other people with expertise in these
>> areas looked through the code, they would find a lot more issues. I'm sure I
>> could find many, many more issues.
>
> Thanks for the review!
>
> Would you be interested in spending another 30 seconds to find out some more
> issue? :-)
I could, provided you could take the things you want to do differently and
submit them as patches to qemu.git instead of creating a new tool.
There are lots of people on qemu-devel than can provide deep review of this type
of code. That's the advantage of working in qemu.git.
[1] http://mid.gmane.org/1320086191-23641-1-git-send-email-coreyb@linux.vnet.ibm.com
Regards,
Anthony Liguori
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 13:43 ` Anthony Liguori
@ 2011-11-10 13:56 ` Pekka Enberg
2011-11-10 14:47 ` Markus Armbruster
0 siblings, 1 reply; 38+ messages in thread
From: Pekka Enberg @ 2011-11-10 13:56 UTC (permalink / raw)
To: Anthony Liguori
Cc: Linus Torvalds, Avi Kivity, Andrew Morton, Ingo Molnar,
linux-kernel, kvm, Christoph Hellwig
Hi Anthony,
On Thu, Nov 10, 2011 at 3:43 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> It's not just the qcow2 implementation or even the block layer. This pull
> requests adds a userspace TCP/IP stack to the kernel and yet netdev isn't on
> the CC and there are no Ack's from anyone from the networking stack. I'm
> fairly sure if they knew what was happening here they would object.
It's something we consider extremely important because it allows easy
non-root networking. But you're right, we definitely ought to ping the
networking folks before the next merge window.
On Thu, Nov 10, 2011 at 3:43 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>> Would you be interested in spending another 30 seconds to find out some
>> more issue? :-)
>
> I could, provided you could take the things you want to do differently and
> submit them as patches to qemu.git instead of creating a new tool.
>
> There are lots of people on qemu-devel than can provide deep review of this
> type of code. That's the advantage of working in qemu.git.
I fully understand if you don't want to spend your time reviewing the
KVM tool code. I'm just saying that if you do spend the next 30
seconds next time you're bored, I'm all ears and happy to fix any
issues you point out.
Pekka
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 13:56 ` Pekka Enberg
@ 2011-11-10 14:47 ` Markus Armbruster
2011-11-10 15:33 ` Stefan Hajnoczi
0 siblings, 1 reply; 38+ messages in thread
From: Markus Armbruster @ 2011-11-10 14:47 UTC (permalink / raw)
To: Pekka Enberg
Cc: Anthony Liguori, Linus Torvalds, Avi Kivity, Andrew Morton,
Ingo Molnar, linux-kernel, kvm, Christoph Hellwig
Pekka Enberg <penberg@kernel.org> writes:
> Hi Anthony,
>
> On Thu, Nov 10, 2011 at 3:43 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>> It's not just the qcow2 implementation or even the block layer. This pull
>> requests adds a userspace TCP/IP stack to the kernel and yet netdev isn't on
>> the CC and there are no Ack's from anyone from the networking stack. I'm
>> fairly sure if they knew what was happening here they would object.
>
> It's something we consider extremely important because it allows easy
> non-root networking. But you're right, we definitely ought to ping the
> networking folks before the next merge window.
The problem is real. The solution "duplicate in user space" sucks. If
you engaging with the kernel networking folks leads to one that doesn't
suck, we should bathe you in free beer.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/GIT PULL] Linux KVM tool for v3.2
2011-11-10 14:47 ` Markus Armbruster
@ 2011-11-10 15:33 ` Stefan Hajnoczi
0 siblings, 0 replies; 38+ messages in thread
From: Stefan Hajnoczi @ 2011-11-10 15:33 UTC (permalink / raw)
To: Markus Armbruster
Cc: Pekka Enberg, Anthony Liguori, Linus Torvalds, Avi Kivity,
Andrew Morton, Ingo Molnar, linux-kernel, kvm, Christoph Hellwig
On Thu, Nov 10, 2011 at 2:47 PM, Markus Armbruster <armbru@redhat.com> wrote:
> Pekka Enberg <penberg@kernel.org> writes:
>
>> Hi Anthony,
>>
>> On Thu, Nov 10, 2011 at 3:43 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>>> It's not just the qcow2 implementation or even the block layer. This pull
>>> requests adds a userspace TCP/IP stack to the kernel and yet netdev isn't on
>>> the CC and there are no Ack's from anyone from the networking stack. I'm
>>> fairly sure if they knew what was happening here they would object.
>>
>> It's something we consider extremely important because it allows easy
>> non-root networking. But you're right, we definitely ought to ping the
>> networking folks before the next merge window.
>
> The problem is real. The solution "duplicate in user space" sucks. If
> you engaging with the kernel networking folks leads to one that doesn't
> suck, we should bathe you in free beer.
Look at disks, the problem is addressed by the udisks daemon on dbus.
Anything can try talking to it. If you have permissions or can get
the user to authenticate then you can manipulate LVM volumes, mount
file systems, etc. We could do something similar for tap networking.
The Ubuntu folks seem to want VDE instead to solve the same problem.
Create a VDE switch with a single tap device on startup. Then let all
VMs talk to the VDE without privileges.
I don't think going through VDE is nice or performant, would be better
to have add virtual network functionality over dbus just like udisks
did for disks.
Stefan
^ permalink raw reply [flat|nested] 38+ messages in thread
end of thread, other threads:[~2011-11-10 15:33 UTC | newest]
Thread overview: 38+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-04 8:38 [RFC/GIT PULL] Linux KVM tool for v3.2 Pekka Enberg
2011-11-04 12:16 ` Christoph Hellwig
2011-11-04 12:35 ` Pekka Enberg
2011-11-04 13:02 ` Christoph Hellwig
2011-11-04 13:32 ` Pekka Enberg
2011-11-04 14:42 ` Jan Kiszka
2011-11-04 15:16 ` Sasha Levin
2011-11-04 16:26 ` Jan Kiszka
2011-11-04 16:48 ` Sasha Levin
2011-11-04 17:33 ` Jan Kiszka
2011-11-04 16:13 ` Joerg Roedel
2011-11-04 16:42 ` Jan Kiszka
2011-11-04 17:41 ` Pekka Enberg
2011-11-04 13:14 ` Joerg Roedel
2011-11-04 14:47 ` Jan Kiszka
2011-11-08 14:44 ` richard -rw- weinberger
2011-11-08 15:36 ` Pekka Enberg
2011-11-08 16:00 ` richard -rw- weinberger
2011-11-10 3:50 ` Anthony Liguori
2011-11-10 6:46 ` Pekka Enberg
2011-11-10 7:57 ` Markus Armbruster
2011-11-10 8:21 ` Pekka Enberg
2011-11-10 8:23 ` Sasha Levin
2011-11-10 8:28 ` Pekka Enberg
2011-11-10 8:57 ` Markus Armbruster
2011-11-10 9:04 ` Sasha Levin
2011-11-10 9:09 ` Avi Kivity
2011-11-10 9:14 ` Sasha Levin
2011-11-10 9:23 ` Avi Kivity
2011-11-10 9:34 ` Sasha Levin
2011-11-10 9:43 ` Avi Kivity
2011-11-10 9:49 ` Sasha Levin
2011-11-10 9:50 ` Avi Kivity
2011-11-10 9:48 ` Markus Armbruster
2011-11-10 13:43 ` Anthony Liguori
2011-11-10 13:56 ` Pekka Enberg
2011-11-10 14:47 ` Markus Armbruster
2011-11-10 15:33 ` Stefan Hajnoczi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).