directory (full) in projects: openbmc - OpenGrok search results

Searched full:directory (Results 1 – 25 of 5863) sorted by relevance

/openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z16/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 97 "BriefDescription": "Directory Write Level 1 Data Cache from Cache", 98 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 104 "BriefDescription": "Directory Write Level 1 Data Cache from Cache with Intervention", 105 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 111 "BriefDescription": "Directory Write Level 1 Data Cache from Cache with Chip HP Hit", 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 118 "BriefDescription": "Directory Write Level 1 Data Cache from Cache with Drawer HP Hit", 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 125 "BriefDescription": "Directory Write Level 1 Data Cache from On-Chip Cache", [all …]
/openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z13/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/openbmc/linux/Documentation/filesystems/ext4/
H A D	directory.rst	3 Directory Entries 6 In an ext4 filesystem, a directory is more or less a flat file that maps 8 filesystem. There can be many directory entries across the filesystem 11 such, directory entries are found by reading the data block(s) 12 associated with a directory file for the particular directory entry that 18 By default, each directory lists its entries in an “almost-linear” 20 sense because directory entries are not split across filesystem blocks. 21 Therefore, it is more accurate to say that a directory is a series of 22 data blocks and that each block contains a linear array of directory 26 directory is of course signified by reaching the end of the file. Unused [all …]
/openbmc/openbmc/poky/documentation/ref-manual/
H A D	structure.rst	4 Source Directory Structure 7 The :term:`Source Directory` consists of numerous files, 10 describes the Source Directory and gives information about those files 13 For information on how to establish a local Source Directory on your 20 The OpenEmbedded build system does not support file or directory 21 names that contain spaces. Be sure that the Source Directory you use 29 This section describes the top-level components of the :term:`Source Directory`. 36 This directory includes a copy of BitBake for ease of use. The copy 44 resides in the ``bitbake/bin/`` directory) starts. Sourcing the 57 This directory contains user configuration files and the output [all …]
H A D	terms.rst	62 :term:`Build Directory` 65 script that is found in the Source Directory 67 :term:`TOPDIR` variable points to the :term:`Build Directory`. 69 You have a lot of flexibility when creating the :term:`Build Directory`. 70 Here are some examples that show how to create the directory. The 71 examples assume your :term:`Source Directory` is named ``poky``: 73 - Create the :term:`Build Directory` inside your Source Directory and let 74 the name of the :term:`Build Directory` default to ``build``: 81 - Create the :term:`Build Directory` inside your home directory and 88 - Provide a directory path and specifically name the [all …]
/openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z14/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/openbmc/linux/Documentation/filesystems/
H A D	directory-locking.rst	2 Directory Locking 6 Locking scheme used for directory operations is based on two 10 When taking the i_rwsem on multiple non-directory objects, we 16 1) read access. Locking rules: caller locks directory we are accessing. 25 4) rename() that is _not_ cross-directory. Locking rules: caller locks 28 non-directory; target - if it's a non-directory or about to be removed. 32 and the target because mixing directory and non-directory is allowed 39 * check that source is not a directory 45 6) cross-directory rename. The trickiest in the whole bunch. Locking 66 If no directory is its own ancestor, the scheme above is deadlock-free. [all …]
H A D	overlayfs.rst	26 non-directory objects may report an st_dev from the lower filesystem or 29 over the lifetime of a non-directory object. Many applications and 92 It would be more correct to refer to an upper and lower 'directory 94 directory trees to be in the same filesystem and there is no 113 upper and lower filesystems and refers to a non-directory in either, 117 Where both upper and lower objects are directories, a merged directory 121 "upperdir" are combined into a merged directory: 126 The "workdir" needs to be an empty directory on the same filesystem 129 Then whenever a lookup is requested in such a merged directory, the 130 lookup is performed in each actual directory and the combined result [all …]
H A D	dnotify.rst	4 Linux Directory Notification 9 The intention of directory notification is to allow user applications 10 to be notified when a directory, or any of the files in it, are changed. 12 on a directory using a fcntl(2) call and the notifications themselves 19 DN_ACCESS A file in the directory was accessed (read) 20 DN_MODIFY A file in the directory was modified (write,truncate) 21 DN_CREATE A file was created in the directory 22 DN_DELETE A file was unlinked from directory 23 DN_RENAME A file in the directory was renamed 24 DN_ATTRIB A file in the directory had its attributes [all …]
/openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z15/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/s390/cf_zec12/
H A D	extended.json	21 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 28 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 35 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 49 …"PublicDescription": "A directory write to the Level-1 Data cache where the installed cache line w… 56 …"PublicDescription": "A directory write to the Level-1 Instruction cache where the installed cache… 63 …"PublicDescription": "A directory write to the Level-1 Data Cache where the line was originally in… 105 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z196/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cac… 14 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the retur… 42 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cac… 49 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cac… 56 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the retur… 63 …"PublicDescription": "A directory write to the Level-1 Data Cache where the line was originally in… 70 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cac… 77 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the retur… 91 …"PublicDescription": "A directory write to the Level-1 Data Cache where the installed cache line w… 98 …"PublicDescription": "A directory write to the Level-1 Instruction Cache where the installed cache… [all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Smbios/
H A D	MDR_V2.interface.yaml	`6 Get the directory with directory index. 11 Directory index of SMBIOS. 16 Directory of agent. 27 Index of SMBIOS directory. 38 Send directory information to SMBIOS directory. 43 A counter which increments each time directory updated. 47 Directory index of SMBIOS. 51 Indicates number of directory entries. 64 Need to continue directory transmission or not. 81 Send data information with directory index. [all …]`
/openbmc/openbmc/poky/documentation/sdk-manual/
H A D	appendix-obtain.rst	31 #. Go to the Installers Directory: Go to 70 directory:: 76 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`" 78 ":ref:`sdk-manual/appendix-obtain:installed extensible sdk directory structure`" 94 Yocto Project :term:`Source Directory` 103 #. Initialize the Build Environment: While in the root directory of 104 the Source Directory (i.e. ``poky``), run the 111 Among other things, the script creates the :term:`Build Directory`, which 112 is ``build`` in this case and is located in the Source Directory. After 113 the script runs, your current working directory is set to the ``build`` [all …]
/openbmc/u-boot/include/
H A D	fs.h	52 * in directory "dirname". 103 * Directory entry types, matches the subset of DT_x in posix readdir() 106 #define FS_DT_DIR 4 /* directory / 111 A directory entry, returned by fs_readdir(). Returns information 112 * about the file/directory at the current directory entry position. 128 * fs_opendir - Open a directory 130 * @filename: the path to directory to open 131 * @return a pointer to the directory stream or NULL on error and errno 137 * fs_readdir - Read the next directory entry in the directory stream. 140 * directory entry is no longer valid after calling fs_readdir() again. [all …]
/openbmc/linux/fs/isofs/
H A D	isofs.h	154 /* Every directory can have many redundant directory entries scattered 155 * throughout the directory tree. First there is the directory entry 156 * with the name of the directory stored in the parent directory. 157 * Then, there is the "." directory entry stored in the directory 158 * itself. Finally, there are possibly many ".." directory entries 164 * the many redundant entries for each directory. We normalize the 165 * block and offset by always making them point to the "." directory. 167 * Notice that we do not use the entry for the directory with the name 168 * that is located in the parent directory. Even though choosing this 169 * first directory is more natural, it is much easier to find the "." [all …]
/openbmc/linux/Documentation/PCI/endpoint/
H A D	pci-endpoint-cfs.rst	17 The PCI Endpoint Core layer creates pci_ep directory in the mounted configfs 18 directory. configfs can be mounted using the following command:: 22 Directory Structure 27 the controllers directory and every EPF driver present in the system 28 will have an entry in the functions directory. 38 Every registered EPF driver will be listed in controllers directory. The 52 user has to create a directory inside <EPF DriverN>. 54 Every <EPF device> directory consists of the following entries that can be 80 interface should be added in 'primary' directory and symlink of endpoint 82 directory. [all …]
/openbmc/linux/scripts/clang-tools/
H A D	gen_compile_commands.py	24 # The tools/ directory adopts a different build system, and produces .cmd 33 directory: The work directory where the objects were built. 41 directory_help = ('specify the output directory used for the kernel build ' 42 '(defaults to the working directory)') 43 parser.add_argument('-d', '--directory', type=str, default='.', 61 'If nothing is specified, the current directory is searched') 67 os.path.abspath(args.directory), 70 args.paths if len(args.paths) > 0 else [args.directory]) 73 def cmdfiles_in_dir(directory): argument 74 """Generate the iterator of .cmd files found under the directory. [all …]
/openbmc/linux/Documentation/admin-guide/mm/damon/
H A D	usage.rst	42 creates multiple directories and files under its sysfs directory, 44 from the files under the directory. 61 directory is having ``/`` suffix, and files in each directory are separated by 101 has one directory named ``admin``. The directory contains the files for 103 having the root permission could use this directory. 112 Under the ``admin`` directory, one directory, ``kdamonds``, which has files for 113 controlling the kdamonds exist. In the beginning, this directory has only one 115 of child directories named ``0`` to ``N-1``. Each directory represents each 121 In each kdamond directory, two files (``state`` and ``pid``) and one directory 133 DAMON-based operation scheme action tried regions directory for each [all …]
/openbmc/linux/fs/freevxfs/
H A D	vxfs_dir.h	9 * Veritas filesystem driver - directory structure. 11 * This file contains the definition of the vxfs directory format. 16 * VxFS directory block header. 18 * This entry is the head of every filesystem block in a directory. 20 * a hash for speeding up directory search (lookup). 33 * of an VxFS directory entry. 38 * VxFS directory entry. 49 * VXFS_DIRPAD defines the directory entry boundaries, is _must_ be 51 * VXFS_NAMEMIN is the length of a directory entry with a NULL d_name. 53 * usable for directory sizes. [all …]
/openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z10/
H A D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the retur… 14 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed ca… 21 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the insta… 28 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed ca… 35 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the insta… 42 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed ca… 49 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed ca… 56 …"PublicDescription": "A directory write to the Level-1 Instruction Cache where the installed cache… 63 …"PublicDescription": "A directory write to the Level-1 Data Cache where the line was originally in…
/openbmc/linux/drivers/thunderbolt/
H A D	property.c	214 * Upon success returns the parsed directory. In case of error returns 218 * The @block is expected to be root directory. 236 * tb_property_create_dir() - Creates new property directory 237 * @uuid: UUID used to identify the particular directory 239 * Creates new, empty property directory. If @uuid is %NULL then the 240 * directory is assumed to be root directory. 286 * tb_property_free_dir() - Release memory allocated for property directory 287 * @dir: Directory to release 289 * This will release all the memory the directory occupies including all 329 /* Reserve dword padding after each directory */ in tb_property_dir_length() [all …]
/openbmc/phosphor-fan-presence/docs/presence/
H A D	README.md	36 ### Supported Directory 41 directory location as part of the firmware image install. This is where the 47 file can be located at the base of the supported directory. 57 A system type sub-directory can be obtained from the 67 directory, appending each compatible system type entry as a sub-directory on 73 - (directory/config file does not exist) 81 ### Override Directory 86 writable directory location. This avoids the need to build and install a new 90 The override directory may not exist on the BMC, therefore to be able to use an 98 the directory locations in the following order: [all …]
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/
H A D	bitbake-user-manual-hello.rst	23 your machine, the BitBake directory appears as follows:: 48 At this point, you should have BitBake cloned to a directory that 55 directory to where your local BitBake files are and run the following 64 The recommended method to run BitBake is from a directory of your 65 choice. To be able to run BitBake from any directory, you need to add 72 Next, add the directory location 74 ``/home/scott-lenovo/bitbake/bin`` directory to the front of the 80 line while working from any directory. 121 #. Create a Project Directory: First, set up a directory for the 123 directory:: [all …]
/openbmc/u-boot/tools/patman/
H A D	tools.py	17 # True to keep the output directory around after exiting 35 """Select an output directory, ensuring it exists. 37 This either creates a temporary directory or checks that the one supplied 38 by the user is valid. For a temporary directory, it makes a note to 42 dirname: a string, name of the output directory to use to store 44 directory. 46 created temporary directory will be destroyed on exit. 49 OSError: If it cannot create the output directory. 60 raise CmdError("Cannot make output directory '%s': '%s'" % 62 tout.Debug("Using output directory '%s'" % outdir) [all …]

12 3 4 5 6 7 8 9 10 >>...235

Project(s)

Full Search
Definition
Symbol
File Path
History
Type