Home
last modified time | relevance | path

Searched full:can (Results 1 – 25 of 3425) sorted by relevance

12345678910>>...137

/qemu/docs/system/devices/
H A Dcan.rst1 CAN Bus Emulation Support
3 The CAN bus emulation provides mechanism to connect multiple
4 emulated CAN controller chips together by one or multiple CAN buses
6 can be connected to host system CAN API (at this time only Linux
9 The concept of buses is generic and different CAN controllers
10 can be implemented.
16 The PCI addon card hardware has been selected as the first CAN
17 interface to implement because such device can be easily connected
20 In 2020, CTU CAN FD controller model has been added as part
28 CAN subsystem for RTEMS. But lack of common environment for code and RTEMS
[all …]
H A Dnet.rst6 QEMU can simulate several network cards (e.g. PCI or ISA cards on the PC
7 target) and can connect them to a network backend on the host or an
8 emulated hub. The various host network backends can either be used to
18 virtual network device on your host (called ``tapN``), and you can then
24 As an example, you can download the ``linux-test-xxx.tar.gz`` archive
26 ``sudo`` so that the command ``ifconfig`` contained in ``qemu-ifup`` can
57 incoming connections. You can use a DHCP client to automatically
61 In order to check that the user mode network is working, you can ping
67 shall work, however. If you're using QEMU on Linux >= 3.0, it can use
77 connections can be redirected from the host to the guest. It allows for
[all …]
H A Dcanokey.rst28 the guest OS can use all the functionalities of a secure key as if
33 * libcanokey-qemu supports debugging output thus developers can
37 and key can be captured and analysed
42 they can see what happens inside the secure key
44 can be easily captured and analysed
46 Also since this is a virtual card, it can be easily used in CI for testing
74 # depending on your env, lib/pkgconfig can be lib64/pkgconfig
93 After the guest OS boots, you can check that there is a USB device.
128 If you want to capture USB packets between the guest and the host, you can:
138 designed for embedded systems. Thus one qemu instance can not have
[all …]
H A Dusb.rst4 QEMU can emulate a PCI UHCI, OHCI, EHCI or XHCI USB controller. You can
32 The QEMU EHCI Adapter supports USB 2.0 devices. It can be used either
38 When running EHCI in standalone mode you can add UHCI or OHCI
49 You can use the standard ``-device`` switch to add a EHCI controller to
55 When adding USB devices using the ``-device`` switch you can specify the
74 The UHCI and OHCI controllers can attach to a USB bus created by EHCI
83 you, which you can use like this:
100 USB devices can be connected with the ``-device usb-...`` command line
131 specify what those disks are backed by. One ``usb-uas`` device can
168 ``tablet`` above but it can be used with the tslib library because in
[all …]
/qemu/tests/qemu-iotests/
H A D083.out4 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
8 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
12 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
16 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
20 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
24 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
28 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
32 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
36 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
40 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
[all …]
H A D092.out5 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
6 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
7 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
8 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
12 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
13 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
14 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
15 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
19 qemu-io: can't open device TEST_DIR/t.qcow: Image too large
20 qemu-io: can't open device TEST_DIR/t.qcow: Image too large
[all …]
H A D080.out5 qemu-io: can't open device TEST_DIR/t.qcow2: qcow2 header exceeds cluster size
6 qemu-io: can't open device TEST_DIR/t.qcow2: qcow2 header exceeds cluster size
10 qemu-io: can't open device TEST_DIR/t.qcow2: Invalid backing file offset
11 qemu-io: can't open device TEST_DIR/t.qcow2: Header extension too large
12 qemu-io: can't open device TEST_DIR/t.qcow2: Header extension too large
16 qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table too large
17 qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table too large
21 qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table offset invalid
25 qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table offset invalid
29 qemu-io: can't open device TEST_DIR/t.qcow2: Snapshot table too large
[all …]
H A D293.out26 qemu-io: can't open: Invalid password, cannot unlock any keyslot
29 qemu-io: can't open: Invalid password, cannot unlock any keyslot
38 qemu-img: Can't add a keyslot - all keyslots are in use
57 qemu-io: can't open: Invalid password, cannot unlock any keyslot
58 qemu-io: can't open: Invalid password, cannot unlock any keyslot
59 qemu-io: can't open: Invalid password, cannot unlock any keyslot
69 qemu-io: can't open: Invalid password, cannot unlock any keyslot
70 qemu-io: can't open: Invalid password, cannot unlock any keyslot
71 qemu-io: can't open: Invalid password, cannot unlock any keyslot
79 qemu-io: can't open: Invalid password, cannot unlock any keyslot
[all …]
H A D075.out3 == check that the first sector can be read ==
7 == check that the last sector can be read ==
12 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: block_size 513 must be a multiple of 512
15 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: block_size cannot be zero
18 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: block_size 4294966784 must be 64 MB or le…
21 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: n_blocks 4294967295 must be 536870911 or …
24 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: image requires too many offsets, try incr…
27 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: offsets not monotonically increasing at i…
30 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: invalid compressed block size at index 1,…
H A D226.out6 qemu-io: can't open: 'file' driver requires 'TEST_DIR/t.IMGFMT' to be a regular file
7 qemu-io: can't open: 'file' driver requires '/dev/null' to be a regular file
9 qemu-io: can't open: Could not open 'TEST_DIR/t.IMGFMT': Is a directory
10 qemu-io: can't open: 'file' driver requires '/dev/null' to be a regular file
15 qemu-io: can't open: 'host_device' driver requires 'TEST_DIR/t.IMGFMT' to be either a character or …
17 qemu-io: can't open: Could not open 'TEST_DIR/t.IMGFMT': Is a directory
22 qemu-io: can't open: 'host_cdrom' driver requires 'TEST_DIR/t.IMGFMT' to be either a character or b…
24 qemu-io: can't open: Could not open 'TEST_DIR/t.IMGFMT': Is a directory
H A D116.out5 qemu-io: can't open device TEST_DIR/t.qed: QED table offset is invalid
9 qemu-io: can't open device TEST_DIR/t.qed: Image not in QED format
13 qemu-io: can't open device TEST_DIR/t.qed: QED cluster size is invalid
17 qemu-io: can't open device TEST_DIR/t.qed: QED table size is invalid
21 qemu-io: can't open device TEST_DIR/t.qed: QED table offset is invalid
25 qemu-io: can't open device TEST_DIR/t.qed: QED table offset is invalid
29 qemu-io: can't open device TEST_DIR/t.qed: QED image size is invalid
H A D088.out5 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 0
6 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 0
7 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 128
8 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 128
9 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 305419896
10 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 305419896
/qemu/docs/devel/
H A Dmulti-process.rst22 QEMU can be susceptible to security attacks because it is a large,
24 Many of these features can be configured out of QEMU, but even a reduced
25 configuration QEMU has a large amount of code a guest can potentially
33 QEMU can be broadly described as providing three main services. One is a
34 VM control point, where VMs can be created, migrated, re-configured, and
44 host processes. Each of these processes can be given only the privileges
66 can emulate provides a large surface of interfaces which could potentially
70 can be separated from the QEMU functions that manage the emulation of
94 a couple of existing QEMU features that can run emulation code
100 Virtio guest device drivers can be connected to vhost user applications
[all …]
H A Dlockcnt.rst69 - reclaiming data can be done by a separate thread in the case of RCU;
70 this can improve performance, but also delay reclamation undesirably.
96 Reads, instead, can be done without taking the mutex, as long as the
101 can happen concurrently with the read. The RCU API ensures that the
126 Here, no frees can happen in the code represented by the ellipsis.
141 can also be more efficient in two ways:
146 - on some platforms, one can implement ``QemuLockCnt`` to hold the lock
149 :doc:`atomics`). This can be very helpful if concurrent access to
153 Using the same mutex for frees and writes can still incur some small
154 inefficiencies; for example, a visit can never start if the counter is
[all …]
H A Dkconfig.rst7 QEMU is a very versatile emulator; it can be built for a variety of
8 targets, where each target can emulate various boards and at the same
9 time different targets can share large amounts of code. For example,
10 a POWER and an x86 board can run the same code to emulate a PCI network
12 can run the same code to emulate a SCSI disk while using different
13 SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
24 * new targets and boards can be added without knowing in detail the
28 user can add to that board;
30 * users can easily build reduced versions of QEMU that support only a subset
43 configuration and dependencies can be treated as a black box when building
[all …]
H A Dtcg-plugins.rst19 out-of-tree plugins that can be dynamically linked into a running QEMU
22 your plugin upstream so they can be updated if/when the API changes.
25 version they were built against. This can be done simply by::
43 can usually be further queried to find out information about a
68 automatically expanded when new cores/threads are created and that can be
86 However the following assumptions can be made:
110 can be can be sure the instruction will be dispatched, but you can't
122 instrumentation although the execution side effects can be observed
129 ``qemu_plugin_register_vcpu_resume_cb`` functions can be used to track
150 * Use a recursive lock, since we can get registration calls from
/qemu/include/net/
H A Dcan_emu.h2 * CAN common CAN bus emulation support
34 /* NOTE: the following two structures is copied from <linux/can.h>. */
39 * bit 0-28 : CAN identifier (11/29 bit)
64 #define QEMU_CAN_FRMF_TYPE_FD 0x10 /* internal bit ind. of CAN FD frame */
67 * struct qemu_can_filter - CAN ID based filter in can_register().
68 * @can_id: relevant bits of CAN ID which are not masked out.
69 * @can_mask: CAN mask (see description)
76 * The filter can be inverted (QEMU_CAN_INV_FILTER bit set in can_id) or it can
84 /* QEMU_CAN_INV_FILTER can be set in qemu_can_filter.can_id */
108 #define TYPE_CAN_BUS "can-bus"
/qemu/docs/
H A Dthrottle.txt11 QEMU includes a throttling module that can be used to set limits to
22 Two aspects of the disk I/O can be limited: the number of bytes per
24 them the user can set a global limit or separate limits for read and
27 I/O limits can be set using the throttling.* parameters of -drive, or
43 and for each case we can decide whether to have separate read and
45 iops-read nor iops-write can be set. The same applies to bps-total and
50 In its most basic usage, the user can add a drive to QEMU with a limit
55 We can do the same using QMP. In this case all these parameters are
75 an amount of I/O that can exceed the basic limit. Bursts are useful to
81 I/O they allow. These two can be configured separately for each one of
[all …]
H A Dqcow2-cache.txt11 The QEMU qcow2 driver has two caches that can improve the I/O
45 There can be many L2 tables, depending on how much space has been
49 reading the table for each I/O operation can be expensive, QEMU keeps
52 The size of the L2 cache can be configured, and setting the right
53 value can improve the I/O performance significantly.
69 bits, but a different value can be set using the refcount_bits option:
74 aforementioned L2 cache, and its size can also be configured.
82 The part of the virtual disk that can be mapped by the L2 and refcount
114 Cache sizes can be configured using the -drive option in the
130 value can be modified using the "l2-cache-size" option. QEMU will not use
[all …]
/qemu/include/standard-headers/linux/
H A Dvirtio_mem.h10 * This header is BSD licensed so anyone can use the definitions
48 * space. Each device can belong to a single NUMA node, multiple devices
50 * "resizable DIMM" consisting of small memory blocks that can be plugged
54 * Virtio-mem devices can only operate on their assigned memory region in
58 * The "region_size" corresponds to the maximum amount of memory that can
65 * The "usable_region_size" represents the memory region that can actually
74 * region can be read, to simplify creation of memory dumps.
76 * It can happen that the device cannot process a request, because it is
80 * device driver can start with a clean state. However, in specific
81 * scenarios (if the device is busy) it can happen that the device still
[all …]
/qemu/net/
H A Dtap-linux.h5 * This program is free software; you can redistribute it and/or modify
48 #define TUN_F_CSUM 0x01 /* You can hand me unchecksummed packets. */
49 #define TUN_F_TSO4 0x02 /* I can handle TSO for IPv4 packets */
50 #define TUN_F_TSO6 0x04 /* I can handle TSO for IPv6 packets */
51 #define TUN_F_TSO_ECN 0x08 /* I can handle TSO with ECN bits. */
52 #define TUN_F_UFO 0x10 /* I can handle UFO packets */
53 #define TUN_F_USO4 0x20 /* I can handle USO for IPv4 packets */
54 #define TUN_F_USO6 0x40 /* I can handle USO for IPv6 packets */
H A Dtap-solaris.c89 error_setg(errp, "Can't open /dev/ip (actually /dev/udp)"); in tap_alloc()
95 error_setg(errp, "Can't open /dev/tap"); in tap_alloc()
105 error_report("Can't assign new interface"); in tap_alloc()
109 error_setg(errp, "Can't open /dev/tap (2)"); in tap_alloc()
113 error_setg(errp, "Can't push IP module"); in tap_alloc()
118 error_report("Can't get flags"); in tap_alloc()
127 error_report("Can't set PPA %d", ppa); in tap_alloc()
129 error_report("Can't get flags"); in tap_alloc()
132 error_report("Can't push ARP module (2)"); in tap_alloc()
138 error_report("Can't push ARP module (3)"); in tap_alloc()
[all …]
/qemu/tests/qtest/
H A Dxlnx-can-test.c2 * QTests for the Xilinx ZynqMP CAN controller.
58 /* CAN modes. */
93 /* Read the interrupt on CAN rx. */ in read_data()
98 /* Read the RX register data for CAN. */ in read_data()
113 /* Write the TX register data for CAN. */ in send_data()
119 /* Read the interrupt on CAN for tx. */ in send_data()
130 * initiate the data transfer to can-bus, CAN1 receives the data. Test compares
141 " -object can-bus,id=canbus" in test_can_bus()
169 * each CAN0 and CAN1 are compared with RX register data for respective CAN.
178 " -object can-bus,id=canbus" in test_can_loopback()
[all …]
/qemu/docs/system/arm/
H A Dxlnx-versal-virt.rst55 Users can load firmware or boot-loaders with the ``-device loader`` options.
63 If users want to provide their own DTB, they can use the ``-dtb`` option.
186 BBRAM can have an optional file backend, which must be a seekable
204 eFUSE can have an optional file backend, which must be a seekable
234 Versal CANFD controller is developed based on SocketCAN and QEMU CAN bus
235 implementation. Bus connection and socketCAN connection for each CAN module
236 can be set through command lines.
242 -object can-bus,id=canbus -machine canbus0=canbus -machine canbus1=canbus
248 -object can-bus,id=canbus0 -object can-bus,id=canbus1 \
251 The SocketCAN interface can connect to a Physical or a Virtual CAN interfaces on
[all …]
/qemu/include/hw/net/
H A Dmii.h11 * This program is free software; you can redistribute it and/or
58 #define MII_BMSR_100T4 (1 << 15) /* Can do 100mbps T4 */
59 #define MII_BMSR_100TX_FD (1 << 14) /* Can do 100mbps, full-duplex */
60 #define MII_BMSR_100TX_HD (1 << 13) /* Can do 100mbps, half-duplex */
61 #define MII_BMSR_10T_FD (1 << 12) /* Can do 10mbps, full-duplex */
62 #define MII_BMSR_10T_HD (1 << 11) /* Can do 10mbps, half-duplex */
63 #define MII_BMSR_100T2_FD (1 << 10) /* Can do 100mbps T2, full-duplex */
64 #define MII_BMSR_100T2_HD (1 << 9) /* Can do 100mbps T2, half-duplex */
74 #define MII_ANAR_RFAULT (1 << 13) /* Say we can detect faults */
85 #define MII_ANLPAR_PAUSEASY (1 << 11) /* can pause asymmetrically */
[all …]

12345678910>>...137