| /barrelfish-2018-10-04/include/x86emu/ |
| H A D | decode.h | 64 u8 fetch_data_byte_abs (uint segment, uint offset);
66 u16 fetch_data_word_abs (uint segment, uint offset);
68 u32 fetch_data_long_abs (uint segment, uint offset);
70 void store_data_byte_abs (uint segment, uint offset, u8 val);
72 void store_data_word_abs (uint segment, uint offset, u16 val);
74 void store_data_long_abs (uint segment, uint offset, u32 val);
|
| /barrelfish-2018-10-04/usr/pci/ |
| H A D | pcie.c | 31 uint16_t segment; local
36 cl->rpc_tx_vtbl.get_pcie_confspace(cl, &err, &address, &segment, &sbus, &ebus);
60 address, segment, sbus, ebus);
61 int r = pcie_confspace_init(pcie_cap, address, segment, sbus, ebus);
|
| /barrelfish-2018-10-04/lib/openssl-1.0.0d/crypto/bio/ |
| H A D | bss_rtcp.c | 223 int status, i, segment, length; local
229 for ( i = 0; i < inl; i += segment ) {
230 segment = inl - i;
231 if ( segment > sizeof(ctx->msg.data) ) segment = sizeof(ctx->msg.data);
234 ctx->msg.length = segment;
235 memmove ( ctx->msg.data, &in[i], segment );
236 status = put ( b->num, (char *) &ctx->msg, segment + RPC_HDR_SIZE );
|
| /barrelfish-2018-10-04/lib/x86emu/ |
| H A D | decode.c | 234 Value of the default data segment
237 Inline function that returns the default data segment for the current
240 On the x86 processor, the default segment is not always DS if there is
241 no segment override. Address modes such as -3[BP] or 10[BP+SI] all refer to
250 cs segment override
251 ds segment override
252 es segment override
253 fs segment override
254 gs segment override
255 ss segment overrid
362 fetch_data_byte_abs( uint segment, uint offset) argument
383 fetch_data_word_abs( uint segment, uint offset) argument
404 fetch_data_long_abs( uint segment, uint offset) argument
492 store_data_byte_abs( uint segment, uint offset, u8 val) argument
515 store_data_word_abs( uint segment, uint offset, u16 val) argument
538 store_data_long_abs( uint segment, uint offset, u32 val) argument
[all...] |
| H A D | debug.c | 238 int segment; local
268 segment = M.x86.saved_cs;
270 X86EMU_dump_memory(segment,(u16)offset,16);
273 segment = ps[1];
275 X86EMU_dump_memory(segment,(u16)offset,16);
278 segment = M.x86.saved_cs;
279 X86EMU_dump_memory(segment,(u16)offset,16);
|
| /barrelfish-2018-10-04/include/pci/confspace/ |
| H A D | pci_confspace.h | 45 int pcie_confspace_init(struct capref, lpaddr_t pbase, uint16_t segment, uint8_t startbus,
|
| /barrelfish-2018-10-04/lib/openssl-1.0.0d/crypto/perlasm/ |
| H A D | x86masm.pl | 11 $segment="";
89 $segment = ".text\$";
127 push(@out,"$segment ENDS\n");
182 { push(@out,"$segment\tENDS\n_DATA\tSEGMENT\n"); $segment="_DATA"; }
|
| H A D | x86nasm.pl | 116 ${drdecor}segment .bss
154 segment .CRT\$XCU data align=4
|
| /barrelfish-2018-10-04/lib/pci/confspace/ |
| H A D | pcie_confspace.c | 32 int pcie_confspace_init(struct capref ram_cap, lpaddr_t base, uint16_t segment, uint8_t startbusarg, argument
37 assert(segment == 0); // unhandled!
|
| /barrelfish-2018-10-04/doc/021-cpudriver/ |
| H A D | cpudriver.tex | 200 0 & NULL segment \\
201 1 & Kernel code segment \\
202 2 & Kernel stack segment \\
203 3 & User stack segment \\
204 4 & User code segment \\
205 5 & Task state segment \\
206 6 & Task state segment (cont.) \\
285 The local descriptor table segment in the GDT will
297 Segment registers are initialized by the \fnname{gdt\_reset} function during start-up and each of them points to a GDT entry (index of the GDT table slot for each segment is given in brackets).
300 \item[cs] Kernel code segment (
[all...] |
| /barrelfish-2018-10-04/usr/eclipseclp/documents/internal/kernel/ |
| H A D | gc.tex | 37 is the collection segment that the collector works on (figure
50 mark accessible objects inside the collection segment and build
110 collection segment. These objects can be referenced from:
120 The roots are displayed in grey, the collection segment is hatched.
124 \caption{Overview of the stack areas (collection segment hatched,
137 inside the collection segment, called the MARK bit.
158 collection segment, in opposite directions.
191 \item The reachable objects in the {\em collection segment} have
218 bottom end of the collection segment, keeping their order, but removing
225 and a bottom-up pass through the collection segment
[all...] |
| H A D | kernel.tex | 1445 trails within the same choicepoint segment are redundant, and
|
| /barrelfish-2018-10-04/usr/eclipseclp/icparc_solvers/ |
| H A D | eplex_relax.pl | 69 % intersects a segment from the piecewise linear constraint.
276 % We're all in the one segment, which is pretty boring...
279 % XXX - if the segment extends infinitely in either
287 % We're at the very last point in the segment --- simply
322 % If (the upper bound of) this segment slopes upwards and
339 % If (the lower bound of) this segment slopes downwards and
362 % segment XMax is deemed to be in).
395 % If (the lower bound of) this segment slopes upwards and
412 % If (the upper bound of) this segment slopes downwards and
485 % before the endpoint of this segment
[all...] |
| /barrelfish-2018-10-04/usr/acpi/ |
| H A D | intel_vtd.c | 140 // units may reside on the same segment.
141 static struct vtd_unit *vtd_create_unit(void *regset_vbase, uint16_t segment) argument
161 new_unit->pci_seg = segment;
607 static void vtd_parse_dev_scope_structure(int index, int segment, char *begin, char *end, enum AcpiDmarType type) argument
627 index, type, entry->EntryType, segment, bus, dev, func, entry->EnumerationId);
634 index, type, entry->EntryType, segment, bus, dev, func, entry->EnumerationId);
635 VTD_DEBUG("Adding device %d:%d:%d:%d\n", segment, bus, dev, func);
643 // such structure for each PCI segment.
680 // An ATSR structure is provided for each PCI segment supporting Device-TLBs. Currently,
|
| /barrelfish-2018-10-04/tools/arm_boot/ |
| H A D | arm_bootimage.c | 6 * and places the lot into an ELF file with a single loadable segment. Thus,
113 void *segment; member in struct:loaded_image
296 /* Find the first loadable segment, and load it. */
304 /* Record the unrelocated base address of the segment. */
309 * segment has a greater alignment restriction, we use that, but
315 fail("Alignment of segment %u (%u)"
321 DBG("Increasing alignment to %u to match segment %zu\n",
331 DBG("Allocated %zu at VA %08x (PA %08x) for segment %zu\n",
341 DBG("got_base is in segment %zu, "
352 DBG("entry is in segment
[all...] |
| /barrelfish-2018-10-04/lib/devif/backends/net/e10k/ |
| H A D | e10k_devif_vf.c | 59 uint32_t segment; member in struct:vf_state
600 vf->segment = seg;
|
| /barrelfish-2018-10-04/doc/017-arm/ |
| H A D | ARM.tex | 318 data segment of the kernel right after the
335 page table (also 16kB-aligned and located inside its data segment) to
|
| /barrelfish-2018-10-04/doc/022-armv8/ |
| H A D | report.tex | 483 dispatcher's shared segment at a fixed known address, \texttt{dcb\_current},
485 held in a \emph{segment register} (\texttt{fs} on x86-64, and \texttt{gs} on
|
| /barrelfish-2018-10-04/usr/eclipseclp/documents/applications/ |
| H A D | tutorial.tex | 754 We can use multiple {\it foreacharg} keywords to scan multiple vectors at the same time, but we cannot use {\it foreacharg} to create terms\index{create terms} (we do not know the functor of the term). If we want to create a new term, we have to generate it with the right functor and arity before the {\it do} loop. The following code segment performs vector addition\index{vector addition} $\vec{C} = \vec{A}+ \vec{B}$.
1650 Generating data in Prolog format is easy if the receiver of the data is another ECLiPSe program, but may be inconvienient if the receiver is written in another language. In that case a tabular format\index{tabular format} that can be read with routines like {\it scanf}\index{scanf} is easier to handle. The following program segment shows how this is done. For each item in a list we extract the relevant arguments, and write them to the output file separated by white space.
1878 The line profiling\footnote{The profiling facility is now available as one of the ECLiPSe libraries in the library coverage. The actual output looks slightly different.}\index{line profiling}\index{profiling} tool that we already mentioned above can be used to check the coverage\index{coverage} of the program with some query. We can easily find lines that are not executed at all, indicating the need for another test case. If we cannot construct a test which executes a program segment, then this indicates some problem.
|
| /barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/ |
| H A D | asm.pl | 1285 valid_reflab(I) :- integer(I), !. % Code segment index (new compiler)
|
| /barrelfish-2018-10-04/doc/002-mackerel/ |
| H A D | Mackerel.tex | 1103 cluttering up the data segment with multiple copies of constants if
|