Home
last modified time | relevance | path

Searched full:probably (Results 1 – 25 of 161) sorted by relevance

1234567

/qemu/docs/config/
H A Dq35-virtio-graphical.cfg10 # You will probably need to tweak the lines marked as
52 # Using less than 1 GiB of memory is probably not going to
220 # headless host, you will probably want to append something
H A Dmach-virt-graphical.cfg11 # You will probably need to tweak the lines marked as
48 # Using less than 1 GiB of memory is probably not going to
271 # headless host, you will probably want to append something
H A Dq35-emulated.cfg10 # You will probably need to tweak the lines marked as
54 # Using less than 1 GiB of memory is probably not going to
261 # headless host, you will probably want to append something
H A Dq35-virtio-serial.cfg11 # You will probably need to tweak the lines marked as
57 # Using less than 1 GiB of memory is probably not going to
H A Dmach-virt-serial.cfg12 # You will probably need to tweak the lines marked as
54 # Using less than 1 GiB of memory is probably not going to
/qemu/tests/functional/
H A Dtest_virtio_gpu.py72 # TODO: probably fails because we are missing the VirGL features
131 # TODO: probably fails because we are missing the VirGL features
/qemu/tests/qemu-iotests/tests/
H A Dblock-status-cache75 # This will probably detect an allocated data sector first (qemu likes
90 # We need to run this map twice: On the first call, we probably still
/qemu/gdb-xml/
H A Darm-vfp-sysregs.xml8 These are A/R profile VFP system registers. Debugger users probably
/qemu/subprojects/libvhost-user/
H A Dlink-test.c3 * probably based off libvhost-user-glib instead.
/qemu/docs/system/
H A Dtarget-sparc.rst63 Please note that currently older Solaris kernels don't work; this is probably
H A Dtarget-openrisc.rst34 help`` output. If it is listed, then you can probably use that board model. If
H A Dtarget-riscv.rst38 in its ``-machine help`` output. If it is listed, then you can probably
H A Dtarget-arm.rst48 in its ``-machine help`` output. If it is listed, then you can probably
/qemu/util/
H A Dsystemd.c61 /* If we cannot set FD_CLOEXEC then it probably means the file in check_socket_activation()
/qemu/docs/system/arm/
H A Dimx8mp-evk.rst36 Probably the easiest way to get started with a whole Linux system on the machine
/qemu/tests/qemu-iotests/
H A Dpylintrc45 # TODO notes are fine, but FIXMEs or XXXs should probably just be
/qemu/contrib/gitdm/
H A Daliases10 # "...is an author name, probably not what you want"
/qemu/contrib/plugins/
H A Dlockstep.c208 * other end has probably died and we should shut down gracefully. in vcpu_tb_exec()
220 * Now read where our peer has reached. Again a failure probably in vcpu_tb_exec()
/qemu/hw/xen/
H A Dxen_pt_load_rom.c73 error_printf("Device option ROM contents are probably invalid " in pci_assign_dev_load_option_rom()
/qemu/include/hw/ssi/
H A Dssi.h96 * to set properties then ssi_create_peripheral() is probably better (as it
/qemu/hw/usb/
H A Ddev-storage-classic.c49 * The hack is probably a bad idea. in usb_msd_storage_realize()
/qemu/bsd-user/freebsd/
H A Dtarget_os_elf.h34 /* should probably go in elf.h */
/qemu/scripts/coccinelle/
H A Dreset-type.cocci39 // itself (probably chaining to the parent class reset) then add the
/qemu/bsd-user/netbsd/
H A Dtarget_os_elf.h32 /* should probably go in elf.h */
/qemu/bsd-user/openbsd/
H A Dtarget_os_elf.h32 /* should probably go in elf.h */

1234567