From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: maobibo <maobibo@loongson.cn>,
Paolo Bonzini <pbonzini@redhat.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Song Gao <gaosong@loongson.cn>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/4] Reconstruct loongson ipi driver
Date: Tue, 16 Jul 2024 08:40:31 +0200 [thread overview]
Message-ID: <4061a31e-1cd8-4cd7-96f3-3e5208e12a87@linaro.org> (raw)
In-Reply-To: <b4a9e1e9-467c-2d50-0d24-174fc9e5c5fe@loongson.cn>
On 16/7/24 03:29, maobibo wrote:
>
>
> On 2024/7/16 上午9:04, maobibo wrote:
>>
>>
>> On 2024/7/15 下午11:17, Philippe Mathieu-Daudé wrote:
>>> On 4/7/24 05:37, Bibo Mao wrote:
>>>> Now loongson ipi and loongarch ipi share the same code with different
>>>> macro, loongson ipi has its separate function such mmio region,
>>>> loongarch ipi has other requirement such as irqchip in kernel.
>>>>
>>>> Interrupt irqchip has strong relationship with architecture, since
>>>> it sends irq to vcpu and interfaces to get irqchip register is also
>>>> architecture specific.
>>>>
>>>> Here like other architectures, base class TYPE_LOONGSON_IPI_COMMON
>>>> is added, it comes from loongson ipi mostly. And it defined four
>>>> abstract
>>>> interfaces which can be used for MIPS 3A4000 and Loongarch 3A5000
>>>> machine,
>>>> also can be used for 3A5000 irqchip in kernel mode soon.
>>>>
>>>> Also Loongarch ipi and loongson ipi device are added here, it inherits
>>>> from base class TYPE_LOONGSON_IPI_COMMON. Loongarch ipi is tested,
>>>> loongson ipi device only passes to compile and make check, it is not
>>>> tested.
>>>>
>>>> Bibo Mao (4):
>>>> hw/intc/loongson_ipi_common: Add loongson ipi common class
>>>> hw/intc/loongarch_ipi: Add loongarch ipi support
>>>> hw/loongarch/virt: Replace loongson ipi with loongarch ipi
>>>> hw/intc/loongson_ipi: reconstruct driver inherit from common class
>>>
>>> I'll try to respin a clearer v3.
>> I am ok with it since it solve the problem, and it is suitable for 9.1
>> release. Only that in the long time we hope that intc emulation driver
>> has common base class + tcg/kvm driver, similar with other architecture.
>>
> Sorry for the confusion, I had thought it was another topic.
>
> Thanks for pointing out the problem and welcome the v3 version.
Please do not post v3, let me post it.
next prev parent reply other threads:[~2024-07-16 6:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 3:37 [PATCH v2 0/4] Reconstruct loongson ipi driver Bibo Mao
2024-07-04 3:37 ` [PATCH v2 1/4] hw/intc/loongson_ipi_common: Add loongson ipi common class Bibo Mao
2024-07-15 15:31 ` Philippe Mathieu-Daudé
2024-07-16 1:11 ` maobibo
2024-07-04 3:38 ` [PATCH v2 2/4] hw/intc/loongarch_ipi: Add loongarch ipi support Bibo Mao
2024-07-04 3:38 ` [PATCH v2 3/4] hw/loongarch/virt: Replace loongson ipi with loongarch ipi Bibo Mao
2024-07-04 3:38 ` [PATCH v2 4/4] hw/intc/loongson_ipi: reconstruct driver inherit from common class Bibo Mao
2024-07-09 12:04 ` [PATCH v2 0/4] Reconstruct loongson ipi driver maobibo
2024-07-10 4:00 ` Jiaxun Yang
2024-07-10 6:08 ` maobibo
2024-07-15 15:17 ` Philippe Mathieu-Daudé
2024-07-16 1:04 ` maobibo
2024-07-16 1:29 ` maobibo
2024-07-16 6:40 ` Philippe Mathieu-Daudé [this message]
2024-07-17 9:22 ` maobibo
2024-07-17 11:53 ` Jiaxun Yang
2024-07-17 21:41 ` Philippe Mathieu-Daudé
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=4061a31e-1cd8-4cd7-96f3-3e5208e12a87@linaro.org \
--to=philmd@linaro.org \
--cc=gaosong@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=maobibo@loongson.cn \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).