[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <hzCmjmGwkKFxQBCFWB4lo3HRGK-vWCBZq1DQNcNEuYkTOT8r5cw_K4ir7gDnGl0REqjD_hnExw9Mkbra0_uObLzMXdRwOb7l8dNuAx_ddvA=@pm.me>
Date: Fri, 20 Dec 2024 19:26:37 +0000
From: Ihor Solodrai <ihor.solodrai@...me>
To: Tejun Heo <tj@...nel.org>
Cc: David Vernet <void@...ifault.com>, sched-ext@...a.com, kernel-team@...a.com, linux-kernel@...r.kernel.org, bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH sched_ext/for-6.13-fixes] sched_ext: Fix invalid irq restore in scx_ops_bypass()
On Thursday, December 19th, 2024 at 2:51 PM, Ihor Solodrai <ihor.solodrai@...me> wrote:
> [...]
>
> Tejun, can you elaborate on what you're looking for in the logs?
> My understanding is that QEMU prints some of the dmesg messages.
> QEMU output is available in raw logs.
I made changes to the CI scripts to explicitly dump dmesg in case of a failure.
It looks like most of that log was already printed.
Job: https://github.com/kernel-patches/bpf/actions/runs/12436924307/job/34726070343
Raw log: https://productionresultssa11.blob.core.windows.net/actions-results/a10f57cb-19e3-487a-9fb0-69742cfbef1b/workflow-job-run-4c580b44-6466-54d8-b922-6f707064e5ca/logs/job/job-logs.txt?rsct=text%2Fplain&se=2024-12-20T19%3A34%3A55Z&sig=kQ09k9r01VtP4p%2FgYvvCmm2FUuOHfsLjU3ARzks4xmE%3D&ske=2024-12-21T07%3A00%3A50Z&skoid=ca7593d4-ee42-46cd-af88-8b886a2f84eb&sks=b&skt=2024-12-20T19%3A00%3A50Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2024-11-04&sp=r&spr=https&sr=b&st=2024-12-20T19%3A24%3A50Z&sv=2024-11-04
Search for "dmesg start".
> [...]
Powered by blists - more mailing lists