[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2] tools/xentrace: decode RTDS priority in repl_budget records

To: Ryoji Okamoto <okamoto@xxxxxxxxxxxxx>
From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date: Wed, 22 Jul 2026 17:11:22 +0200
Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=selector1 header.d=vates.tech header.i="@vates.tech" header.h="From:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type:In-Reply-To:References:Feedback-ID"
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx, Ryo Takakura <takakura@xxxxxxxxxxxxx>, Hirokazu Takahashi <taka@xxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>
Delivery-date: Wed, 22 Jul 2026 15:11:40 +0000
Feedback-id: default:8631fc262581453bbf619ec5b2062170:Sweego
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Fri, Jul 10, 2026 at 03:43:52PM +0900, Ryoji Okamoto wrote:
> 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: 463b95831778 ("xen:rtds: towards work conserving RTDS")
> Signed-off-by: Ryoji Okamoto <okamoto@xxxxxxxxxxxxx>

Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>

Thanks,


--
Anthony Perard | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech

References:
- [PATCH v2] tools/xentrace: decode RTDS priority in repl_budget records
  - From: Ryoji Okamoto

Prev by Date: Re: [PATCH v2 07/13] mm/vma: rename vma_get_page_prot to vma_flags_to_page_prot
Next by Date: Re: [PATCH v2 08/13] mm: introduce vma_get_page_prot() and use it
Previous by thread: Re: [PATCH v2] tools/xentrace: decode RTDS priority in repl_budget records
Next by thread: [PATCH for-4.22 0/2] xen/arm: Fix eSPI IRQ indexing issues
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.