tools/xentrace: decode RTDS priority in repl_budget records

The RTDS repl_budget trace record now contains the vCPU priority
level. Update xenalyze to account for the additional field and print
it when dumping the trace event.

Without this change, xenalyze interprets the record using the old
layout, causing the deadline and budget fields to be decoded from the
wrong offsets.

Fixes: 463b958317 ("xen:rtds: towards work conserving RTDS")
Signed-off-by: Ryoji Okamoto <okamoto@valinux.co.jp>
Reviewed-by: Teddy Astie <teddy.astie@vates.tech>
Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>
This commit is contained in:
Ryoji Okamoto authored and Jan Beulich committed 2026-07-23 10:20:08 +02:00
1 parent 14c05f26f8
commit 2fe6a869da
1 file changed
+3 -2
+3 -2
View File
@@ -8039,12 +8039,13 @@ void sched_process(struct pcpu_info *p)
if(opt.dump_all) {
struct {
unsigned int vcpuid:16, domid:16;
uint32_t priority_level;
uint64_t cur_dl, cur_bg;
} __attribute__((packed)) *r = (typeof(r))ri->d;
printf(" %s rtds:repl_budget d%uv%u, deadline = %"PRIu64", "
"budget = %"PRIu64"\n", ri->dump_header,
r->domid, r->vcpuid, r->cur_dl, r->cur_bg);
"budget = %"PRIu64", priority = %u\n", ri->dump_header,
r->domid, r->vcpuid, r->cur_dl, r->cur_bg, r->priority_level);
}
break;
case TRC_SCHED_CLASS_EVT(RTDS, 5): /* SCHED_TASKLET */
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.