From: "Alex Bennée" <alex.bennee@linaro.org>
To: Shashi Mallela <shashi.mallela@linaro.org>
Cc: peter.maydell@linaro.org, leif@nuviainc.com,
qemu-devel@nongnu.org, qemu-arm@nongnu.org, rad@semihalf.com
Subject: Re: [PATCH] hw/intc: cannot clear GICv3 ITS CTLR[Enabled] bit
Date: Thu, 25 Nov 2021 15:18:45 +0000 [thread overview]
Message-ID: <87v90gfejs.fsf@linaro.org> (raw)
In-Reply-To: <20211124182246.67691-1-shashi.mallela@linaro.org>
Shashi Mallela <shashi.mallela@linaro.org> writes:
> When Enabled bit is cleared in GITS_CTLR,ITS feature continues
> to be enabled.This patch fixes the issue.
>
> Signed-off-by: Shashi Mallela <shashi.mallela@linaro.org>
Tested-by: Alex Bennée <alex.bennee@linaro.org>
in so far as it doesn't break the kvm-unit-tests but it also doesn't
solve the:
irq 55: nobody cared (try booting with the "irqpoll" option)
CPU: 0 PID: 9 Comm: ksoftirqd/0 Not tainted 5.15.1-ajb #67
Hardware name: linux,dummy-virt (DT)
Call trace:
dump_backtrace+0x0/0x1ac
show_stack+0x18/0x24
dump_stack_lvl+0x68/0x84
dump_stack+0x18/0x34
__report_bad_irq+0x4c/0x168
note_interrupt+0x278/0x420
handle_irq_event+0x84/0x1a0
handle_fasteoi_irq+0x148/0x214
handle_domain_irq+0x60/0x90
gic_handle_irq+0xb0/0x120
call_on_irq_stack+0x2c/0x5c
do_interrupt_handler+0x40/0x58
el1_interrupt+0x30/0x50
el1h_64_irq_handler+0x18/0x24
el1h_64_irq+0x78/0x7c
finish_task_switch.isra.0+0x174/0x290
__schedule+0x5e0/0x674
__cond_resched+0x24/0x50
run_ksoftirqd+0x44/0x5c
smpboot_thread_fn+0x154/0x180
kthread+0x118/0x130
ret_from_fork+0x10/0x20
handlers:
[<0000000050cdc74a>] vring_interrupt
Disabling IRQ #55
that is being seen on newer kernels.
--
Alex Bennée
next prev parent reply other threads:[~2021-11-25 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 18:22 [PATCH] hw/intc: cannot clear GICv3 ITS CTLR[Enabled] bit Shashi Mallela
2021-11-25 15:18 ` Alex Bennée [this message]
2021-11-25 15:48 ` Peter Maydell
2021-11-25 15:47 ` Peter Maydell
2021-11-26 16:54 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v90gfejs.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=leif@nuviainc.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rad@semihalf.com \
--cc=shashi.mallela@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).