/barrelfish-2018-10-04/tools/aarch64_gem5/ |
H A D | CacheConfig.py | 37 def config_cache(options, system): 40 # system.l2 = O3_ARM_v7aL2(size = options.l2_size, assoc = options.l2_assoc) 43 system.l2 = L2Cache(size = options.l2_size, assoc = options.l2_assoc) 44 system.tol2bus = L2XBar() 45 system.l2.cpu_side = system.tol2bus.master 46 system.l2.mem_side = system.membus.slave 48 system.voltage_domain = VoltageDomain() 49 system [all...] |
H A D | gem5script.py | 67 # Check that we are running on a full-system arm simulator 114 system = ArmSystem() variable 115 #system = LinuxArmSystem() 117 system.kernel = options.kernel 119 #memory system 120 system.iobus = IOXBar() 121 #system.iobus = NoncoherentXBar() 122 #system.iobus.forward_latency = 0 123 #system.iobus.frontend_latency = 0 124 #system [all...] |
/barrelfish-2018-10-04/tools/molly/ |
H A D | m5script.py | 19 # Check that we are running on a full-system X86 simulator 41 system = X86System() variable 44 system.kernel = options.kernel 47 system.membus = Bus() 48 system.physmem = PhysicalMemory(range = AddrRange('512MB')) 49 system.physmem.port = system.membus.port 54 system.cpu = [CPUClass(cpu_id=i) for i in xrange(options.num_cpus)] 55 system.mem_mode = 'atomic' 57 system [all...] |
/barrelfish-2018-10-04/lib/acpica/tests/aslts/bin/bugstate/ |
H A D | bdemossum | 27 # arg2 - the name of system and modeid (system:modeid) the tests were run on 85 # arg2 - the name of system the tests were run on 90 local path0 path1 modepart0 modename0 system 97 system="$2" 99 echo "Extracting bdemo-results of <$system, $modename0>:" 108 get_summary "$path0" "$system:$modeid" > "$path1" 154 system=`get_name_of_system "$COMMONLOGFILE"` 157 do_summary "$DIR0" "$system" $NORM32 158 do_summary "$DIR0" "$system" [all...] |
/barrelfish-2018-10-04/lib/openssl-1.0.0d/apps/ |
H A D | CA.pl.bak | 71 system ("$REQ -new -x509 -keyout newkey.pem -out newcert.pem $DAYS"); 76 system ("$REQ -new -keyout newkey.pem -out newreq.pem $DAYS"); 81 system ("$REQ -new -nodes -keyout newkey.pem -out newreq.pem $DAYS"); 114 system ("$REQ -new -keyout " . 116 system ("$CA -create_serial " . 127 system ("$PKCS12 -in newcert.pem -inkey newkey.pem " . 134 system ("$CA -policy policy_anything -infiles newreq.pem"); 137 system ("$CA -policy policy_anything -out newcert.pem " . 142 system ("$CA -policy policy_anything -out newcert.pem " . 147 system (" [all...] |
H A D | CA.pl.in | 71 system ("$REQ -new -x509 -keyout newkey.pem -out newcert.pem $DAYS"); 76 system ("$REQ -new -keyout newkey.pem -out newreq.pem $DAYS"); 81 system ("$REQ -new -nodes -keyout newkey.pem -out newreq.pem $DAYS"); 114 system ("$REQ -new -keyout " . 116 system ("$CA -create_serial " . 127 system ("$PKCS12 -in newcert.pem -inkey newkey.pem " . 134 system ("$CA -policy policy_anything -infiles newreq.pem"); 137 system ("$CA -policy policy_anything -out newcert.pem " . 142 system ("$CA -policy policy_anything -out newcert.pem " . 147 system (" [all...] |
/barrelfish-2018-10-04/lib/tommath/ |
H A D | pretty.build | 47 !system("make $tmp > /dev/null 2>/dev/null") or die "\nERROR: Failed to make $tmp!!!\n"; 65 !system("make > /dev/null 2>/dev/null") or die "\nERROR: Failed to perform last make command!!!\n";
|
/barrelfish-2018-10-04/lib/libc/stdlib/ |
H A D | system.c | 31 static char sccsid[] = "@(#)system.c 8.1 (Berkeley) 6/4/93"; 49 #pragma weak system macro 51 system(const char *command) function
|
H A D | Makefile.inc | 17 strtoumax.c strtouq.c system.c tdelete.c tfind.c tsearch.c twalk.c 31 realpath.3 strfmon.3 strtod.3 strtol.3 strtonum.3 strtoul.3 system.3 \
|
/barrelfish-2018-10-04/lib/libc/sys/barrelfish/ |
H A D | syscalls.c | 20 int system(const char *cmd) function
|
/barrelfish-2018-10-04/lib/lwip2/src/apps/httpd/makefsdata/ |
H A D | makefsdata | 43 system("cat /tmp/header $file > /tmp/file"); 45 system("cp $file /tmp/file");
|
/barrelfish-2018-10-04/tools/ds5/configdb/ |
H A D | bootPanda.py | 26 os.system('Barrelfish/tools/bin/usbboot Barrelfish/armv7_omap44xx_image')
|
H A D | kernelPanda.py | 26 os.system('Barrelfish/tools/bin/usbboot Barrelfish/armv7_omap44xx_image')
|
/barrelfish-2018-10-04/doc/012-services/ |
H A D | Services.tex | 105 The binding service facilitates communication in the system, allowing 135 manipulate system memory, and control execution of the system. It may 137 services that allow control of system abstractions such as 157 devices in the system. Its responsibilities include collecting such 225 The power management services monitors power usage in the system, 226 reacts to power-related events, and can manipulate system resources to 227 control power usage. It also manages system sleep and wakeup, and 235 system (e.g., accounts, users, process ids, etc.). The principals are used for 287 manipulating system task [all...] |
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/ |
H A D | umscmdlineopts.tex | 29 The {\eclipse} system has several parameters which may be specified on the 43 The file name is expected to be in the operating system's syntax. 51 Instead of starting an interactive toplevel, the system will execute the 66 is compulsory because a runtime system does not have an interactive 92 directory, i.e., the directory in which the system tries to find 93 the {\eclipse} runtime system and libraries. This option overrides 107 created by the system, which serves as the context for \notation{-f} and 113 The {\eclipse} system will ignore this argument and everything that follows on 127 The system will first search for these files in the current directory,
|
H A D | umsintro.tex | 39 is an open-source software system whose aim is to serve as a platform 60 code \cite{warren83}, and a runtime system comprising an emulator of 61 this abstract code, automatic memory management, I/O system and 71 The {\eclipse} logic programming system was originally an integration of 73 It was then further developed into a Constraint Logic Programming system 86 from the development system's help/1 command and the tkeclipse library 102 %The system calls user-definable event handlers 124 %{\eclipse} enables the user to modify most of the system features, 142 %an atom or functor followed by \verb.^.D, the system will try to 166 %search. {\eclipse} offers a complete system fo [all...] |
H A D | umsusing.tex | 49 \section{How do I install the {\eclipse} system?} 56 are available in the installed system. 63 user interface to the {\eclipse} compiler and system. 76 operating system command-line prompt, or select {\tkeclipse} from the 141 (For more information about the module system, please see chapter 315 {\eclipse} system, updated at regular intervals. 362 operating system command-line prompt. 379 of the running system, i.e., the language extensions that are present. 405 The {\eclipse} system may be exited by typing \notation{CTRL-D} (UNIX) or 430 the system look [all...] |
H A D | umsopsys.tex | 37 {\eclipse}'s operating system interface consists of a collection of built-in 47 useful information from the operating system environment. 78 When {\eclipse} is exited, it can give a return code to the operating system. 81 argument to the operating system. 119 cpu time, the system cpu time and the elapsed real time since 133 the system is running can be obtained by the two global flags 144 linked to the Prolog system. 157 It can be read and changed within the {\eclipse} system by using 210 (as defined by the UNIX system call \notation{stat(2)}; not all entries are 276 \bipref{system/ [all...] |
H A D | umserrors.tex | 48 Unless otherwise specified, the arguments that the system passes 214 operating system & undefined \\ 259 accidental exits from the system. Failure of the handler is ignored. 343 When a stack overflows, the system performs a 369 When they occur, the system performs a warm restart. 377 This signals an inconsistency in the system's internal data structures. 378 The reason can be either a bug in the {\eclipse} system itself or in an 396 %the {\eclipse} system. If those are redefined by the user, this may have 408 %prevents system stream from being closed. 409 %If an attempt is made to close a stream that a system strea [all...] |
/barrelfish-2018-10-04/usr/eclipseclp/documents/megalog/ |
H A D | intro-sec.tex | 38 \eclipse integrates all the functionality of the MegaLog system 39 (\cite{BOC90}, \cite{BDH90}) and the Sepia system 40 (\cite{SP91}) in a single system. 79 of \eclipse to view the system as either a pure 94 advanced users, e.g.\ as target language for a deductive database system 117 MegaLog system 125 are present in the system by default.
|
/barrelfish-2018-10-04/doc/000-overview/ |
H A D | Overview.tex | 61 system~\cite{barrelfish:sosp09}: it consists of a small kernel running on each core (one kernel per core), and while rest of the 62 OS is structured as a distributed system of single-core processes atop 103 In a heterogeneous Barrelfish system, CPU drivers will be different 112 exception handlers for events such as interrupts, faults, and system 160 Operating system tasks in Barrelfish are always single-core by design, 250 model~\cite{sel4:iies08}, with a considerably larger type system and 257 can only manipulate capabilities using kernel system calls (to which 258 it passes capability references). In processing a system call the 263 used in system calls (see \texttt{include/barrelfish/caddr.h}). Valid bits are 278 hierarchy (e.g. Figure~\ref{fig:cap_hierarchy}). The type system fo [all...] |
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/ |
H A D | ecoptions.tex | 47 system specific pagesizes. On machines where initially only virtual memory 50 operating system swap file is taken immediately (SunOS), their default 117 \item[Parallel system parameters]\ \\ 124 worker in a parallel system. They should not be altered.
|
/barrelfish-2018-10-04/tools/ |
H A D | qemu-wrapper.sh | 45 echo " QEMU_PATH (Path for qemu-system-* binary)" 53 ${QEMU_PATH}qemu-system-x86_64 -device help 2>&1 | grep \"$1\" > /dev/null 157 #QEMU_CMD="${QEMU_PATH}qemu-system-x86_64 \ 170 QEMU_CMD="${QEMU_PATH}qemu-system-x86_64 \ 185 QEMU_CMD="${QEMU_PATH}qemu-system-arm \ 193 QEMU_CMD="${QEMU_PATH}qemu-system-aarch64 \ 207 QEMU_CMD="${QEMU_PATH}qemu-system-arm \
|
/barrelfish-2018-10-04/doc/004-virtual_memory/ |
H A D | VirtualMemory.tex | 42 This document describes the virtual memory system of Barrelfish. 43 It tries to describe the setup and the design decisions made in the construction of the system. 47 The virtual memory system is made up of four user space components listed 48 below and utilizes the capability system to create hardware page tables. 102 This is the only architecture specific portion of the virtual memory system. 121 In order for this system to make it possible to remove mappings when the 128 The map invocation can create multi-page mappings in one system call, as long 138 Detail some of the known issues with the system.
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/libman/ |
H A D | mp.tex | 49 Another point worth noting is that the parallel \eclipse system 52 the parallel system, but is not accessible from the \eclipse 151 The system makes sure that there is no nested notification on the same port, 176 communication services used in the parallel \eclipse system. 212 complete implementation basis. Integration into the system should be easy since \eclipsetwo 216 the current \eclipse system with a slightly extended library \cite{vass}
|