| /qemu/tests/qapi-schema/ |
| H A D | enum-bad-name.json | 2 # FIXME reports 'not\possible' instead of 'not\\possible'
3 { 'enum': 'MyEnum', 'data': [ 'not\\possible' ] }
|
| H A D | enum-bad-name.err | 2 enum-bad-name.json:3: 'data' member 'not\possible' has an invalid name
|
| H A D | reserved-member-u.json | 4 # This is true even for non-unions, because it is possible to convert a
|
| H A D | union-base-union.json | 2 # TODO: It would be possible to allow a union as a base, as long as all
|
| /qemu/scripts/ |
| H A D | checkpatch.pl | 1260 sub possible { subroutine
1261 my ($possible, $line) = @_;
1280 warn "CHECK<$possible> ($line)\n" if ($dbg_possible > 2);
1281 if ($possible !~ $notPermitted) {
1283 $possible =~ s/\s*$Storage\s*//g;
1284 $possible =~ s/\s*$Sparse\s*//g;
1285 if ($possible =~ /^\s*$/) {
1287 } elsif ($possible =~ /\s/) {
1288 $possible =~ s/\s*(?:$Type|\#\#)\s*//g;
1289 for my $modifier (split(' ', $possible)) {
[all …]
|
| /qemu/hw/ppc/ |
| H A D | spapr_caps.c | 65 SpaprCapPossible *possible; member
107 if (value >= cap->possible->num) { in spapr_cap_get_string()
112 val = g_strdup(cap->possible->vals[value]); in spapr_cap_get_string()
130 error_setg(errp, "%s", cap->possible->help); in spapr_cap_set_string()
133 for (i = 0; i < cap->possible->num; i++) { in spapr_cap_set_string()
134 if (!strcasecmp(val, cap->possible->vals[i])) { in spapr_cap_set_string()
763 .possible = &cap_cfpc_possible,
773 .possible = &cap_sbbc_possible,
785 .possible = &cap_ibs_possible,
|
| /qemu/docs/system/ |
| H A D | secrets.rst | 31 For the convenience of people debugging / developing with QEMU, it is possible
39 Again it is possible to provide the data in base64 encoded format, which is
87 possible to configure a second secret as an AES key to use for decrypting
120 host, it is further possible to pass secrets to QEMU using the Linux keyring:
128 the serial number ``1729``. It is possible to combine use of the keyring with
|
| H A D | target-openrisc.rst | 24 If you intend to boot Linux, it is possible to have a single kernel image that
26 drivers into the kernel. This is possible because QEMU will create a device tree
|
| H A D | target-avr.rst | 17 Following are examples of possible usages, assuming demo.elf is compiled for
|
| H A D | authz.rst | 28 It is possible, however, to enable mutual verification by requiring that
64 A possible use case would be when configuring QEMU for an incoming live
226 here, and it is possible to implement brand new plugins using the PAM API.
|
| H A D | security.rst | 100 Should this not be possible for technical reasons, the security risk must be
117 It is also possible to launch QEMU as a non-root user and configure UNIX groups
121 - SELinux and AppArmor make it possible to confine processes beyond the
|
| /qemu/docs/system/ppc/ |
| H A D | pseries.rst | 120 (virtio-net, virtio-blk/scsi and virtio-rng for instance) if possible instead,
165 possible to switch between the two modes with the ``kvm-type`` parameter:
179 originated, as historically (prior to POWER7) it was not possible to run Linux
209 hypervisor mode of the Power CPU, it wasn't possible to run KVM-HV on a guest.
210 This limitation has been lifted, and now it is possible to run KVM-HV inside
211 pSeries guests as well, making nested virtualization possible with KVM-HV.
215 of the same type as the host CPU this way, e.g. it is not possible to specify an
|
| /qemu/docs/devel/ |
| H A D | rcu.rst | 11 serialize multiple updates, but other approaches are possible (e.g.,
31 How is this possible? The basic idea is to split updates in two phases,
55 starts reclaiming data. This is possible, because the old version of the
82 ``synchronize_rcu``. If this is not possible (for example, because
198 - Waiting on a mutex is possible, though discouraged, within an RCU critical
218 In general, RCU can be used whenever it is possible to create a new
265 is possible to combine this idiom with a "real" reference count::
304 Note that the same idioms would be possible with reader/writer
|
| H A D | clocks.rst | 23 example it is possible to create a clock outside of any device to
96 Note that it is possible to create a static array describing clock inputs and
193 Note that a clock only has one callback: it is not possible to register
260 It is not possible to disconnect a clock or to change the clock connection
318 still possible that the output clock connected to it is disabled
338 It is also possible to register a callback on clock frequency changes.
361 It's also possible to retrieve the clock period from a QTest by
401 possible non-whole-number-of-nanoseconds periods and avoids
423 Then at any time (apart from the cases listed below), it is possible to
453 that it is possible to expose the clock under a different name.
|
| H A D | lockcnt.rst | 31 If however this loop must also be reentrant, i.e. it is possible that
133 Note that it is possible for multiple concurrent accesses to delay
160 - concurrent access is possible but rare
|
| /qemu/docs/ |
| H A D | xen-save-devices-state.txt | 8 however it is also possible to save the state of all devices to file,
|
| /qemu/docs/system/devices/ |
| H A D | usb-u2f.rst | 24 U2F security key with several guest VMs, which is not possible with a
60 there are three possible ways to configure the ``u2f-emulated`` device:
|
| /qemu/qapi/ |
| H A D | audio.json | 208 # @server-name: select from among several possible concurrent server
442 # An enumeration of possible audio formats.
466 # An enumeration of possible audio backend drivers.
497 # possible)
|
| H A D | sockets.json | 50 # @to: If present, this is range of possible addresses, with port
127 # .. note:: String types are used to allow for possible future
|
| H A D | ebpf.json | 16 # Currently, there is a possible eBPF for receive-side scaling (RSS).
|
| H A D | job.json | 139 # The job will pause as soon as possible, which means transitioning
175 # The job will cancel as soon as possible and then emit a
177 # ABORTING, but it is possible that a job successfully completes (e.g.
|
| /qemu/python/tests/ |
| H A D | minreqs.txt | 1 # This file lists the ***oldest possible dependencies*** needed to run
|
| /qemu/docs/system/arm/ |
| H A D | cpu-features.rst | 36 CPU type is possible with the ``query-cpu-model-expansion`` QMP command.
112 It's possible for features to have dependencies on other features. I.e.
113 it may be possible to change one feature at a time without error, but
115 depending on the order they are processed. It's also possible changing
139 expanded. This restriction is necessary as it's not possible to know all
414 is set to the maximum possible length.
445 length is set to the maximum possible length.
461 To aid firmware developers in testing different possible CPU
|
| /qemu/docs/interop/ |
| H A D | vhost-user.json | 177 # It is possible for multiple @VhostUserBackend elements to match the
240 # latter's possible exposure to the end-user. @tags serves
|
| /qemu/tcg/tci/ |
| H A D | README | 16 interpreter for the generated bytecode, it is possible to
116 possible to see where code must be added.
|