Searched full:reasons (Results 1 – 25 of 90) sorted by relevance
1234
41 # For historical reasons, SuperIO devices are created in the board72 # For historical reasons, SuperIO devices are created in the board
22 Applies to the pci variant only for obvious reasons.73 Likewise applies to the pci variant only for obvious reasons.
11 for several reasons:114 added to the core for compatibility reasons. If transport or device specific
63 strList *reasons = info->blocked_reasons; in hmp_info_migrate() local65 while (reasons) { in hmp_info_migrate()66 monitor_printf(mon, " %s\n", reasons->value); in hmp_info_migrate()67 reasons = reasons->next; in hmp_info_migrate()
33 void qemu_savevm_non_migratable_list(strList **reasons);
7 enumeration of possible reasons for that failure.
44 the virtualization use case. However, for historical reasons much of the100 Should this not be possible for technical reasons, the security risk must be
56 * portability reasons in qemu_drm_rendernode_open()
38 int last_vm_running; /* per console for caption reasons */
7 # historical reasons); think twice before you add to them!
50 * TODO: This will be removed for performance reasons.94 * requests. We do the lock here for safety reasons though. However in do_readdir_many()
76 * Please notice that for binary compat reasons MIPS has to
54 When adding a device to PXB it is attached to the bridge for two reasons:
161 /* Reasons of transport reset event */
100 # Some filesystems can fudge allocations for various reasons; rather
209 __u32 flags; /* will stay unused for compatibility reasons */211 __u32 reserved[4]; /* will stay unused for compatibility reasons */
72 * FIXME: Even if the guest can't receive packets for some reasons, in filter_buffer_receive_iov()
209 * inherit from generic_name for two reasons:
82 * in interpreting shutdown requests and reasons for fully-virtualized
82 * reasons, though:
150 * Reasons: in shakti_c_soc_class_init()
85 categories, or using different names for historical reasons
83 /* uint32_t is used here for ids for padding reasons. */
177 * There can be a variety of reasons and stages in which failure
143 * So for compatibility reasons with old BIOSes we are stuck with in fw_cfg_arch_create()