Searched refs:record_id (Results 1 – 2 of 2) sorted by relevance
141 of CPER record_id's to efficiently access records in the backend155 | record_id[0] | 0x0018157 | record_id[1] | 0x0020159 | record_id[...] |161 | record_id[N] | 0x1FF8168 The 'record_offset' field points to the first record_id in the array,176 The 'record_id' array fields are the 64-bit record identifiers of the178 location of a CPER record_id in the record_id[] array provides the182 contains the header, so the record_id[0] will never contain a valid183 CPER record_id. Instead slot 1 is the first available slot and thus[all …]
472 uint64_t record_id) in update_map_entry() argument475 s->header->map[index] = cpu_to_le64(record_id); in update_map_entry()