Follow-up from PR #600.
dv_log args are currently limited to 32-bit values because the DV monitor consumes 32-bit beats — a 64-bit value would be truncated with today's implementation (#600 (comment)).
Track widening the arg path (log write side + DV monitor beat handling) so callers are not restricted to 32-bit args.
Related: this same 32-bit limitation means dv_log_write cannot log a full 128-bit CHERI capability today — only its address via %x/%p (#600 (comment)). Widening the arg path here would also unblock full capability logging.
Follow-up from PR #600.
dv_logargs are currently limited to 32-bit values because the DV monitor consumes 32-bit beats — a 64-bit value would be truncated with today's implementation (#600 (comment)).Track widening the arg path (log write side + DV monitor beat handling) so callers are not restricted to 32-bit args.
Related: this same 32-bit limitation means
dv_log_writecannot log a full 128-bit CHERI capability today — only its address via %x/%p (#600 (comment)). Widening the arg path here would also unblock full capability logging.