From: Marc Zyngier <maz@kernel.org>
To: "zhangjianhua (E)" <chris.zjh@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Gowans, James" <jgowans@amazon.com>,
zouyipeng@huawei.com, "Raslan, KarimAllah" <karahmed@amazon.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irq: fasteoi handler re-runs on concurrent invoke
Date: Mon, 03 Apr 2023 14:19:29 +0100 [thread overview]
Message-ID: <546fbd173aec3b7fc07d253393920bf5@kernel.org> (raw)
In-Reply-To: <1a974f41-83ec-9c7f-ddf1-cb093ae95046@huawei.com>
On 2023-04-03 14:17, zhangjianhua (E) wrote:
> Hi Thomas
>
> I have the same problem as James and Yipeng, while modify the irq
> affinity
>
> concurrently during LPI interrupt processing, it does cause interrupt
> loss.
>
> Fortunately, James and Yipeng give their patches separately with the
> similar
>
> solutions, and hope you'll take this issue seriously, thanks.
Neither solutions are remotely acceptable.
I'll look at something a bit more palatable.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2023-04-03 13:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 9:53 [PATCH] irq: fasteoi handler re-runs on concurrent invoke James Gowans
2023-03-17 10:12 ` Yipeng Zou
2023-03-17 11:49 ` Gowans, James
2023-03-22 6:26 ` Yipeng Zou
2023-03-22 7:48 ` Gowans, James
2023-03-22 10:37 ` Thomas Gleixner
2023-04-03 13:17 ` zhangjianhua (E)
2023-04-03 13:19 ` Marc Zyngier [this message]
2023-04-03 13:39 ` Gowans, James
2023-03-22 10:38 ` Yipeng Zou
2023-04-09 11:41 ` Marc Zyngier
2023-04-11 10:27 ` Gowans, James
2023-04-12 13:32 ` Marc Zyngier
2023-04-18 2:39 ` Yipeng Zou
2023-04-18 10:56 ` Gowans, James
2023-04-19 3:08 ` Yipeng Zou
2023-05-02 8:43 ` Gowans, James
2023-05-23 3:16 ` liaochang (A)
2023-05-25 10:04 ` Gowans, James
2023-05-29 2:47 ` Liao, Chang
2023-05-30 21:47 ` Gowans, James
[not found] ` <86sfcfghqh.wl-maz@kernel.org>
2023-05-23 12:47 ` Gowans, James
2023-05-25 12:31 ` Liao, Chang
2023-05-02 10:28 ` Marc Zyngier
2023-05-23 3:16 ` liaochang (A)
2023-05-23 3:15 ` liaochang (A)
2023-05-23 11:59 ` Gowans, James
2023-05-25 12:31 ` Liao, Chang
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=546fbd173aec3b7fc07d253393920bf5@kernel.org \
--to=maz@kernel.org \
--cc=chris.zjh@huawei.com \
--cc=dwmw@amazon.co.uk \
--cc=jgowans@amazon.com \
--cc=karahmed@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zouyipeng@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.