qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Bibo Mao" <maobibo@loongson.cn>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	gaosong <gaosong@loongson.cn>,
	"QEMU devel" <qemu-devel@nongnu.org>
Cc: "Huacai Chen" <chenhuacai@kernel.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH v3 1/4] hw/intc: Remove loongarch_ipi.c
Date: Mon, 01 Jul 2024 08:08:11 +0100	[thread overview]
Message-ID: <2b73d23a-4c36-4f0e-9d30-1d1af4c472fd@app.fastmail.com> (raw)
In-Reply-To: <ceebb4ea-a417-0985-d45e-3988d76e2086@loongson.cn>



在2024年7月1日七月 上午2:35,maobibo写道:
[...]
>
> How about split loongson_ipi.c into 
> loongson_ipi_base.c/loongson_ipi_loongson.c/loongson_ipi_loongarch.c,
>
> File loongson_ipi_base.c contains the common code, loongson_ipi_xxx.c 
> contains arch specific. Soon we will submit irqchip in kernel function,
> it will be much different for architectures, since ioctl command is 
> different for two architectures to save/restore ipi registers.

MIPS's in kernel IPI IOCTL interface is non-existent so far, so if you are going
to design something, I think it will be adopted by MIPS if necessary. There is still
no need to create divergence in between.

That being said, You are more than welcomed to draft a patch so we can discuss based
on that.

Thanks
>
> Regards
> Bibo Mao

-- 
- Jiaxun


  parent reply	other threads:[~2024-07-01  7:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  2:15 [PATCH v3 0/4] hw/mips/loongson3_virt: Implement IPI support Jiaxun Yang
2024-06-05  2:15 ` [PATCH v3 1/4] hw/intc: Remove loongarch_ipi.c Jiaxun Yang
2024-06-05  3:32   ` gaosong
2024-06-18 11:09   ` Philippe Mathieu-Daudé
2024-06-26  4:11   ` maobibo
2024-06-26  7:40     ` Jiaxun Yang
2024-06-26  7:51       ` maobibo
2024-06-26 10:03         ` Jiaxun Yang
2024-06-26 12:10     ` Philippe Mathieu-Daudé
2024-06-27  2:44       ` gaosong
2024-06-27 13:02         ` Philippe Mathieu-Daudé
2024-07-01  1:35           ` maobibo
2024-07-01  6:44             ` maobibo
2024-07-01  7:01               ` Jiaxun Yang
2024-07-01  7:22                 ` maobibo
2024-07-01  8:29                   ` Jiaxun Yang
2024-07-01  8:51                     ` maobibo
2024-07-01  7:08             ` Jiaxun Yang [this message]
2024-07-01  7:24               ` maobibo
2024-06-05  2:15 ` [PATCH v3 2/4] hw/intc/loongson_ipi: Provide per core MMIO address spaces Jiaxun Yang
2024-06-05  2:15 ` [PATCH v3 3/4] hw/mips/loongson3_virt: Wire up loongson_ipi device Jiaxun Yang
2024-06-18 11:17   ` Philippe Mathieu-Daudé
2024-06-18 11:24     ` Philippe Mathieu-Daudé
2024-06-05  2:15 ` [PATCH v3 4/4] hw/intc/loongson_ipi: Replace ipi_getcpu with cpu_by_arch_id Jiaxun Yang
2024-06-05  3:33   ` gaosong
2024-06-12 12:09 ` [PATCH v3 0/4] hw/mips/loongson3_virt: Implement IPI support Jiaxun Yang
2024-06-18 11:49   ` 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=2b73d23a-4c36-4f0e-9d30-1d1af4c472fd@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=chenhuacai@kernel.org \
    --cc=gaosong@loongson.cn \
    --cc=maobibo@loongson.cn \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).