XenevaOS
Loading...
Searching...
No Matches
Public Attributes | List of all members
hl_info_razwi_event Struct Reference

#include <habanalabs_accel.h>

Public Attributes

__s64 timestamp
 
__u64 addr
 
__u16 engine_id [HL_RAZWI_MAX_NUM_OF_ENGINES_PER_RTR]
 
__u16 num_of_possible_engines
 
__u8 flags
 
__u8 pad [5]
 

Detailed Description

struct hl_info_razwi_event - razwi information. @timestamp: timestamp of razwi. @addr: address which accessing it caused razwi. @engine_id: engine id of the razwi initiator, if it was initiated by engine that does not have engine id it will be set to HL_RAZWI_NA_ENG_ID. If there are several possible engines which caused the razwi, it will hold all of them. @num_of_possible_engines: contains number of possible engine ids. In some asics, razwi indication might be common for several engines and there is no way to get the exact engine. In this way, engine_id array will be filled with all possible engines caused this razwi. Also, there might be possibility in gaudi, where we don't indication on specific engine, in that case the value of this parameter will be zero. @flags: bitmask for additional data: HL_RAZWI_READ - razwi caused by read operation HL_RAZWI_WRITE - razwi caused by write operation HL_RAZWI_LBW - razwi caused by lbw fabric transaction HL_RAZWI_HBW - razwi caused by hbw fabric transaction HL_RAZWI_RR - razwi caused by range register HL_RAZWI_ADDR_DEC - razwi caused by address decode error Note: this data is not supported by all asics, in that case the relevant bits will not be set.

Member Data Documentation

◆ addr

__u64 hl_info_razwi_event::addr

◆ engine_id

__u16 hl_info_razwi_event::engine_id[HL_RAZWI_MAX_NUM_OF_ENGINES_PER_RTR]

◆ flags

__u8 hl_info_razwi_event::flags

◆ num_of_possible_engines

__u16 hl_info_razwi_event::num_of_possible_engines

◆ pad

__u8 hl_info_razwi_event::pad[5]

◆ timestamp

__s64 hl_info_razwi_event::timestamp

The documentation for this struct was generated from the following file: