mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Wang <unicorn_wang@outlook.com>
To: Inochi Amaoto <inochiama@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Anup Patel <anup@brainfault.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Samuel Holland <samuel.holland@sifive.com>,
	Marc Zyngier <maz@kernel.org>, Nam Cao <namcao@linutronix.de>
Subject: Re: Affinity setting problem for emulated MSI on PLIC
Date: Thu, 21 Aug 2025 14:32:37 +0800	[thread overview]
Message-ID: <MAUPR01MB110721C4A0C82AD2A8348CEF0FE32A@MAUPR01MB11072.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <236be1b9-58a6-4d4d-9faf-9cbd38f63162@outlook.com>


On 8/20/2025 3:40 PM, Chen Wang wrote:

[......]
> So it might be worth investigating why the two different processing 
> paths in `irq_startup()` cause this problem. I saw that Inochi 
> submitted a patch titled "irqchip/sifive-plic: Respect mask state when 
> setting affinity." Can we assume that simply applying this patch will 
> resolve the current issues with the SG2044? Do we also need to 
> consider introducing changes to the startup/shutdown functions of the 
> plic?

Sorry, please ignore my question. I looked at the patch again today and 
it is still necessary to introduce startup/shutdown for plic.

Thanks,

Chen

[......]

  parent reply	other threads:[~2025-08-21  6:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 22:45 Inochi Amaoto
2025-07-23 22:50 ` Thomas Gleixner
2025-07-24  1:34   ` Inochi Amaoto
2025-07-24 11:07     ` Thomas Gleixner
2025-07-24 22:25       ` Inochi Amaoto
2025-08-20  7:40         ` Chen Wang
     [not found]         ` <236be1b9-58a6-4d4d-9faf-9cbd38f63162@outlook.com>
2025-08-21  6:32           ` Chen Wang [this message]
2025-07-24  1:35   ` Inochi Amaoto
2025-08-08  5:56   ` Nam Cao

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=MAUPR01MB110721C4A0C82AD2A8348CEF0FE32A@MAUPR01MB11072.INDPRD01.PROD.OUTLOOK.COM \
    --to=unicorn_wang@outlook.com \
    --cc=anup@brainfault.org \
    --cc=inochiama@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=namcao@linutronix.de \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@sifive.com \
    --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®