/qemu/scripts/qapi/ |
H A D | gen.py | 237 what: str, 241 self._what = what 255 what: str, 261 self._what = what 295 def _module_basename(self, what: str, name: str) -> str: 299 ret += what 304 ret += re.sub(r'-', '-' + name[2:] + '-', what) 307 def _module_filename(self, what: str, name: str) -> str: 309 self._module_basename(what, name))
|
H A D | schema.py | 1182 what: Union[None, str, Callable[[QAPISourceInfo], str]], 1186 assert info and what # built-in types must not fail lookup 1187 if callable(what): 1188 what = what(info) 1190 info, "%s uses unknown type '%s'" % (what, name))
|
H A D | parser.py | 745 args: Dict[str, QAPIDoc.ArgSection], what: str 753 what,
|
/qemu/contrib/plugins/ |
H A D | howvec.c | 45 CountType what; member 185 switch (class->what) { in plugin_exit() 276 switch (class->what) { in find_counter() 382 class_table[j].what = type; in qemu_plugin_install()
|
/qemu/docs/system/devices/ |
H A D | canokey.rst | 34 inspect what happens inside a secure key 42 they can see what happens inside the secure key 113 If you want to trace what happens inside the secure key, when compiling
|
/qemu/target/m68k/ |
H A D | translate.c | 348 if (what == EA_STORE) { in gen_ldst() 792 if (what == EA_STORE) { in gen_ea_mode() 800 if (what == EA_STORE) { in gen_ea_mode() 812 if (what == EA_STORE || !addrp) { in gen_ea_mode() 824 if (addrp && what == EA_STORE) { in gen_ea_mode() 843 if (addrp && what == EA_STORE) { in gen_ea_mode() 866 if (what == EA_LOADS) { in gen_ea_mode() 873 if (what == EA_LOADS) { in gen_ea_mode() 1027 if (what == EA_STORE) { in gen_ldst_fp() 1044 if (what == EA_STORE) { in gen_ea_mode_fp() [all …]
|
/qemu/hw/s390x/ |
H A D | s390-stattrib.c | 63 uint64_t what = qdict_get_int(qdict, "mode"); in hmp_migrationmode() local 67 r = sac->set_migrationmode(sas, what, &local_err); in hmp_migrationmode()
|
/qemu/docs/devel/migration/ |
H A D | compatibility.rst | 63 idea of what the pc-5.1 machine is. 110 that array to see what value it needs to get for that feature. And 111 what are we going to put in that array, the value of a property. 116 property, and that is what it is going to get in the latest released 173 Think what happens if we do one of this double migrations: 322 it. The problem is what happens when we detect after we have done a 409 Now we see how the fix is done. This is going to depend on what kind
|
/qemu/docs/specs/ |
H A D | ppc-spapr-numa.rst | 204 discretion of what would be (somewhat) sensible considering the user input. 329 Note that this is not what the user wanted - the desired distance between 330 0 and 3 is 40, we calculated it as 20. This is what the current logic and 336 is to keep expectations up to par with what we are capable of provide at this 391 on what QEMU users can expect when doing NUMA tuning. As of QEMU 5.1, this is
|
H A D | ppc-spapr-hcalls.rst | 9 which is what PowerVM, the IBM proprietary hypervisor, adheres to.
|
/qemu/docs/system/ |
H A D | guest-loader.rst | 17 This is what is typically done by a boot-loader like grub using its
|
H A D | target-mips.rst | 84 what the proprietary MIPS emulator uses for running Linux. It supports:
|
/qemu/contrib/gitdm/ |
H A D | aliases | 10 # "...is an author name, probably not what you want"
|
/qemu/docs/sphinx/ |
H A D | qapidoc.py | 163 def _nodes_for_members(self, doc, what, base=None, branches=None): argument 194 section = self._make_section(what)
|
/qemu/ |
H A D | COPYING | 46 want its recipients to know that what they have is not the original, so 77 Whether that is true depends on what the Program does. 226 This section is intended to make thoroughly clear what is believed to 293 <one line to give the program's name and a brief idea of what it does.> 338 library. If this is what you want to do, use the GNU Lesser General
|
/qemu/linux-headers/LICENSES/preferred/ |
H A D | GPL-2.0 | 65 want its recipients to know that what they have is not the original, so 96 Whether that is true depends on what the Program does. 245 This section is intended to make thoroughly clear what is believed to 312 <one line to give the program's name and a brief idea of what it does.> 358 library. If this is what you want to do, use the GNU Library General
|
/qemu/qapi/ |
H A D | introspect.json | 20 # SchemaInfo. This lets QMP clients figure out what commands and 25 # what's there), not interface specification. The specification is in
|
/qemu/docs/system/arm/ |
H A D | sbsa.rst | 70 what kind of ``sbsa-ref`` board it is running on. It is neither
|
/qemu/docs/devel/ |
H A D | docs.rst | 56 of the file to see what the expected usage is, because this
|
H A D | submitting-a-patch.rst | 210 what tests are available. 364 entire series; potential reviewers know what files they are interested 391 - in the cover letter, be clear about why a patch is an RFC, what areas 504 committed. This part should be a self-contained description of what this 514 reviewers on what changed between revisions. 591 from others as what you submit. Don't worry if you don't know the code
|
H A D | reset.rst | 35 from what is a real hardware cold reset. It differs from other resets (like 84 its registers back to what reset state was as well as reset everything on the 131 must provide and what functions it has access to. It is intended for people
|
H A D | acpi-bits.rst | 19 hide them from the end user. We have more control of what we wanted to test and 116 This is the biosbits config file that determines what tests
|
/qemu/block/ |
H A D | ssh.c | 1213 static void unsafe_flush_warning(BDRVSSHState *s, const char *what) in unsafe_flush_warning() argument 1218 if (what) { in unsafe_flush_warning() 1219 error_report("to support fsync, you need %s", what); in unsafe_flush_warning()
|
/qemu/docs/interop/ |
H A D | qmp-spec.rst | 113 required. Each command documents what contents will be considered 381 this, a Client should be "conservative in what they send, and liberal in 382 what they accept".
|
/qemu/docs/ |
H A D | memory-hotplug.txt | 13 hotpluggable memory slots to create and what is the maximum amount of
|