Searched refs:detail (Results 1 – 22 of 22) sorted by relevance
/qemu/contrib/plugins/ |
H A D | hwprofile.c | 41 GHashTable *detail; member 131 if (rec->detail) { in plugin_exit() 132 GList *accesses = g_hash_table_get_values(rec->detail); in plugin_exit() 162 count->detail = g_hash_table_new(NULL, NULL); in new_count() 231 IOLocationCounts *io_count = g_hash_table_lookup(counts->detail, in vcpu_haddr() 234 io_count = new_location(counts->detail, off); in vcpu_haddr()
|
/qemu/tests/avocado/acpi-bits/bits-tests/ |
H A D | testacpi.py2 | 212 def detail(d, fmt): 218 detail(unique_num_dependencies, 'Dependency count for each processor = {} (Expected 1)') 220 detail(unique_num_entries, 'num_entries = {} (Expected 5)') 222 detail(unique_revision, 'revision = {}') 224 detail(unique_coordination_type, 'coordination_type = {:#x} (Expected 0xFE HW_ALL)') 226 detail(unique_domain, 'domain = {:#x} (Expected a unique value for each processor)') 228 detail(unique_num_processors, 'num_processors = {} (Expected 1)')
|
/qemu/hw/nvram/ |
H A D | xlnx-bbram.c | 91 static void bbram_bdrv_error(XlnxBBRam *s, int rc, gchar *detail) in bbram_bdrv_error() argument 96 blk_name(s->blk), detail); in bbram_bdrv_error() 100 g_free(detail); in bbram_bdrv_error()
|
/qemu/docs/system/ |
H A D | target-riscv.rst | 34 cares much less about the detail of the hardware.)
|
H A D | target-arm.rst | 44 cares much less about the detail of the hardware.)
|
H A D | vnc-security.rst | 170 multiple serious flaws described in detail in RFC 6331 and thus should
|
/qemu/docs/devel/ |
H A D | secure-coding-practices.rst | 25 Instead of describing them in detail here, only the names of the most important
|
H A D | fuzzing.rst | 277 In more detail:
|
H A D | kconfig.rst | 24 * new targets and boards can be added without knowing in detail the
|
H A D | writing-monitor-commands.rst | 517 Another important detail is that HMP's "info" commands go into
|
H A D | tcg-plugins.rst | 66 ``qemu_plugin_install`` method of a plugin will detail the minimum and
|
H A D | qapi-code-gen.rst | 106 These are discussed in detail below.
|
/qemu/qapi/ |
H A D | transaction.json | 235 # additional detail.
|
H A D | cxl.json | 353 # correctable internal error, with additional detail available from
|
/qemu/docs/specs/ |
H A D | ivshmem-spec.rst | 157 The next section describes the protocol in detail.
|
H A D | ppc-spapr-hotplug.rst | 59 location labels is documented in detail in the [LoPAR]_ section 12.3.1.5,
|
/qemu/docs/ |
H A D | COLO-FT.txt | 144 The diagram just shows the main qmp command, you can get the detail
|
H A D | qdev-device-use.txt | 79 The -device argument differs in detail for each type of drive:
|
/qemu/ |
H A D | COPYING | 239 be similar in spirit to the present version, but may differ in detail to
|
H A D | qemu-options.hx | 5549 If you want to know the detail of above command line, you can
|
/qemu/linux-headers/LICENSES/preferred/ |
H A D | GPL-2.0 | 258 be similar in spirit to the present version, but may differ in detail to
|
/qemu/docs/interop/ |
H A D | bitmaps.rst | 163 detail and should not be relevant to external users.
|