From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Bibo Mao <maobibo@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: <linux-mips@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lvjianmin@loongson.cn>
Subject: Re: [PATCH v2] irqchip/loongson-eiointc: Refine irq affinity setting during resume
Date: Tue, 16 Jan 2024 11:17:24 +0300 [thread overview]
Message-ID: <58b05897-8d06-52fa-8cde-ca7caa591200@omp.ru> (raw)
In-Reply-To: <20240116080555.409215-1-maobibo@loongson.cn>
On 1/16/24 11:05 AM, Bibo Mao wrote:
> During suspend and resume, other CPUs are hot-unpluged and IRQs are
> migrated to CPU0. So it is not necessary to restore irq affinity for
> eiointc irq controller.
>
> Also there is some optimization for the interrupt dispatch function
> eiointc_irq_dispatch. There are 256 IRQs supported for eiointc, eiointc
> irq handler reads the bitmap and find pending irqs when irq happens.
> So there are four times of consecutive iocsr_read64 operations for the
> total 256 bits to find all pending irqs. If the pending bitmap is zero,
> it means that there is no pending irq for the this irq bitmap range,
> we can skip handling to avoid some useless operations sush as clearing
s/sush/such/?
> hw ISR.
This sounds like you need 2 patches to deal with 2 separate issues...
> Signed-off-by: Bibo Mao <maobibo@loongson.cn>
[...]
MBR, Sergey
next prev parent reply other threads:[~2024-01-16 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 8:05 Bibo Mao
2024-01-16 8:17 ` Sergey Shtylyov [this message]
2024-01-16 8:26 ` maobibo
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=58b05897-8d06-52fa-8cde-ca7caa591200@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®