| /xen-4.10.0-shim-comet/tools/libxl/ |
| A D | test_fdderegrace.c | 6 libxl_asyncop_how how; in main() local
11 how.callback = NULL; in main()
12 how.u.for_event = 1; in main()
17 rc = libxl_test_fdevent(ctx, fd, POLLIN, &how); in main()
22 rc = libxl_ao_abort(ctx, &how); in main()
28 assert(event->for_user == how.u.for_event); in main()
49 how.u.for_event++; in main()
50 rc = libxl_test_fdevent(ctx, fd, POLLIN, &how); in main()
|
| A D | libxl_event.c | 1405 aop->how->callback(CTX, aop->ev, aop->how->for_callback); in egc_run_callbacks()
1419 ao->how.callback(CTX, ao->rc, ao->how.u.for_callback); in egc_run_callbacks()
1940 if (how) { in libxl__ao_create()
1941 ao->how = *how; in libxl__ao_create()
1948 ao, how, ao->how.callback, ao->poller); in libxl__ao_create()
2088 if (how) { in libxl_ao_abort()
2093 if (how->callback != search->how.callback) in libxl_ao_abort()
2095 if (how->callback in libxl_ao_abort()
2096 ? (how->u.for_callback != search->how.u.for_callback) in libxl_ao_abort()
2097 : (how->u.for_event != search->how.u.for_event)) in libxl_ao_abort()
[all …]
|
| /xen-4.10.0-shim-comet/docs/features/ |
| A D | template.pandoc | 35 how to enable the feature (is it enabled by default? If not, how to turn
36 it on?), and how to interact with the feature (typically via `xl`).
50 Information concerning how to properly test changes affecting this feature.
|
| /xen-4.10.0-shim-comet/docs/misc/ |
| A D | coverage.markdown | 4 You can see how many times a line is executed.
46 **This section is just an example on how to use these tools!**
|
| A D | console.txt | 15 This document tries to describe how the whole system works and how the
48 how to use channels and includes a registry of well-known channel names.
107 of emulated serials depends on how many "-serial" command line options
|
| A D | xenmon.txt | 31 This is how much time the domain spent waiting to run, or put another way, the
41 This is how much time the domain spent blocked (or sleeping); Put another way,
51 This is how much cpu time was allocated to the domain by the scheduler; This is
|
| A D | 9pfs.markdown | 253 how much data has been written by the frontend to **out** and how much
258 Consumer and producer indices for responses. They keep track of how
405 the consumer workflow described in [Ring Usage]. The server knows how
412 array. The client knows how much data to read because it is specified in
|
| A D | netif-staging-grants.pandoc | 44 Here we describe how netback and netfront general operate, and where the proposed
117 1) Calculate how many slots are needed for transmitting the packet.
241 mapped at guest request. Guest decides how to distribute or use these premapped
327 [ It's up to the backend to choose how it fills this data. E.g. backend may
410 The idea is to allow guest more controllability on how its grants are mapped or
438 implicitly zero) and how many entries in the list. Each entry in this list
|
| A D | pv-drivers-lifecycle.markdown | 13 handshake mechanism, the ABI, how the protocol works and anything else
|
| A D | crashdb.txt | 17 The next step depends on your individual setup. This is how to do it
|
| A D | amd-ucode-container.txt | 58 Following example shows how to generate a combined initrd
|
| A D | vtd-pi.txt | 227 for more information about how CPU handles it.
232 how to use this new global vector.
322 ways (configurable by BIOS) on how the handle lowest priority interrupts:
|
| A D | pvh.markdown | 5 builder how to load and jump into the kernel entry point:
|
| A D | grant-tables.txt | 43 because an understanding of how they work may be useful. Each of these is a
350 Where it is known in advance how many grant references are required, and
|
| /xen-4.10.0-shim-comet/docs/man/ |
| A D | xenstore.pod.1 | 52 http://wiki.xen.org/xenwiki/ReportingBugs on how to send bug reports.
|
| A D | xenstore-chmod.pod.1 | 62 http://wiki.xen.org/xenwiki/ReportingBugs on how to send bug reports.
|
| A D | xenstore-ls.pod.1 | 62 http://wiki.xen.org/xenwiki/ReportingBugs on how to send bug reports.
|
| A D | xlcpupool.cfg.pod.5 | 132 information on how to submit a patch to Xen.
|
| /xen-4.10.0-shim-comet/m4/ |
| A D | README.source | 18 on how to use this read the pkg-config(1) man page.
|
| /xen-4.10.0-shim-comet/tools/fuzz/ |
| A D | README.oss-fuzz | 36 standalone mode, please refer to oss-fuzz documents on how to do that.
|
| /xen-4.10.0-shim-comet/tools/flask/policy/modules/ |
| A D | xen.te | 45 # Note: don't allow access to these types directly; see below for how to label
|
| A D | xen.if | 141 # Define how a device model domain interacts with its target
|
| /xen-4.10.0-shim-comet/tools/firmware/vgabios/ |
| A D | vbe_display_api.txt | 10 This document does not describe how the VBEBios implements the VBE2/3 spec.
11 This document does not describe how the Bochs display code will display gfx based upon this spec.
|
| /xen-4.10.0-shim-comet/xen/ |
| A D | Kconfig.debug | 89 Lock profiling allows you to see how often locks are taken and blocked.
|
| /xen-4.10.0-shim-comet/docs/designs/ |
| A D | dmop.markdown | 16 memory. The real problem comes down to how you would vet this address -
|