From: Hanjun Guo <guohanjun@huawei.com>
To: "Kazuhiro Abe (Fujitsu)" <fj1078ii@fujitsu.com>,
'Ilkka Koskinen' <ilkka@os.amperecomputing.com>,
'Sudeep Holla' <sudeep.holla@arm.com>
Cc: 'Lorenzo Pieralisi' <lpieralisi@kernel.org>,
"'Rafael J. Wysocki'" <rafael@kernel.org>,
'Len Brown' <lenb@kernel.org>,
"'linux-acpi@vger.kernel.org'" <linux-acpi@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] ACPI: AGDI: Add interrupt signaling mode support
Date: Sat, 27 Sep 2025 10:55:47 +0800 [thread overview]
Message-ID: <3bbdc50e-a55c-96ed-a8db-6bbce1760ee4@huawei.com> (raw)
In-Reply-To: <TY3PR01MB9983025D434CAA2CDF83656BD511A@TY3PR01MB9983.jpnprd01.prod.outlook.com>
On 2025/9/19 13:05, Kazuhiro Abe (Fujitsu) wrote:
> Hi Hanjun & Sudeep
>
>> Hi Ilkka
>>
>>> Hi Kazuhiro,
>>>
>>> On Fri, 5 Sep 2025, Kazuhiro Abe wrote:
>>>> AGDI has two types of signaling modes: SDEI and interrupt.
>>>> Currently, the AGDI driver only supports SDEI.
>>>> Therefore, add support for interrupt signaling mode The interrupt
>>>> vector is retrieved from the AGDI table, and call panic function
>>>> when an interrupt occurs.
>>>>
>>>> Signed-off-by: Kazuhiro Abe <fj1078ii@aa.jp.fujitsu.com>
>>>
>>>
>>> Looks good to me.
>>>
>>> Reviewed-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
>>>
>>
>> Thanks for your review.
>>
>> Best Regards,
>> Kazuhiro Abe
>>
>>>
>>> Hanjun & Sudeep, what's your thought on enabling the use of regular
>>> interrupts here? I do agree the spec talks about non-maskable ones and
>>> to my understanding that's what the idea was indeed.
>
> Do you have any thoughts on this matter?
For the real use case, if the system is in failure state, for example,
the system is panic, the CPU will not handle regular interrupts, so
what's the use case do you have to use regular interrupt?
Thanks
Hanjun
next prev parent reply other threads:[~2025-09-27 2:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 4:27 Kazuhiro Abe
2025-09-08 19:02 ` Ilkka Koskinen
2025-09-11 6:57 ` Kazuhiro Abe (Fujitsu)
2025-09-19 5:05 ` Kazuhiro Abe (Fujitsu)
2025-09-27 2:55 ` Hanjun Guo [this message]
2025-09-29 7:32 ` Kazuhiro Abe (Fujitsu)
2025-09-29 9:03 ` Hanjun Guo
2025-09-29 9:31 ` Kazuhiro Abe (Fujitsu)
2025-09-27 2:45 ` Hanjun Guo
2025-09-29 7:23 ` Kazuhiro Abe (Fujitsu)
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=3bbdc50e-a55c-96ed-a8db-6bbce1760ee4@huawei.com \
--to=guohanjun@huawei.com \
--cc=fj1078ii@fujitsu.com \
--cc=ilkka@os.amperecomputing.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.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 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®