DepSurf

Struct: `sched_in_data`

Regular

In 4.18: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In 5.0: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In 5.3: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In 5.4: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

Arch

In arm64: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In armhf: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In ppc64el: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In riscv64: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

Flavor

In aws: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In azure: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In gcp: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

In lowlatency: ✅

struct sched_in_data {
    struct perf_event_context *ctx;
    struct perf_cpu_context *cpuctx;
    int can_add_hw;
};

Regular

Arch

Flavor