QEMU-Devel Archive mirror
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: qemu-devel@nongnu.org
Cc: "Huacai Chen" <chenhuacai@kernel.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Song Gao" <gaosong@loongson.cn>,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>
Subject: [PATCH 0/5] hw/mips/loongson3_virt: Implement IPI support
Date: Wed, 08 May 2024 14:06:45 +0100	[thread overview]
Message-ID: <20240508-loongson3-ipi-v1-0-1a7b67704664@flygoat.com> (raw)

Hi all,

This series enabled IPI support for loongson3 virt board, loosely
based on my previous work[1].
It generalized loongarch_ipi device to share among both loongarch
and MIPS machines. 

Thanks

[1]: https://lore.kernel.org/all/20230521102307.87081-1-jiaxun.yang@flygoat.com/

To: qemu-devel@nongnu.org
Cc: Song Gao <gaosong@loongson.cn>

Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
---
Jiaxun Yang (5):
      hw/intc/loongarch_ipi: Remove pointless MAX_CPU check
      hw/intc/loongarch_ipi: Rename as loongson_ipi
      hw/intc/loongson_ipi: Implement IOCSR address space for MIPS
      hw/intc/loongson_ipi: Provide per core MMIO address spaces
      hw/mips/loongson3_virt: Wire up loongson_ipi device

 MAINTAINERS                                        |   4 +
 hw/intc/Kconfig                                    |   2 +-
 hw/intc/loongarch_ipi.c                            |  19 +-
 hw/intc/loongson_ipi.c                             | 411 +++++++++++++++++++++
 hw/intc/meson.build                                |   2 +-
 hw/intc/trace-events                               |   8 +-
 hw/loongarch/Kconfig                               |   2 +-
 hw/loongarch/virt.c                                |   4 +-
 hw/mips/Kconfig                                    |   1 +
 hw/mips/loongson3_bootp.c                          |   2 -
 hw/mips/loongson3_bootp.h                          |   3 +
 hw/mips/loongson3_virt.c                           |  39 +-
 .../hw/intc/{loongarch_ipi.h => loongson_ipi.h}    |  14 +-
 include/hw/loongarch/virt.h                        |   2 +-
 14 files changed, 475 insertions(+), 38 deletions(-)
---
base-commit: 248f6f62df073a3b4158fd0093863ab885feabb5
change-id: 20240508-loongson3-ipi-65e99b47c400

Best regards,
-- 
Jiaxun Yang <jiaxun.yang@flygoat.com>



             reply	other threads:[~2024-05-08 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 13:06 Jiaxun Yang [this message]
2024-05-08 13:06 ` [PATCH 1/5] hw/intc/loongarch_ipi: Remove pointless MAX_CPU check Jiaxun Yang
2024-05-08 16:22   ` Philippe Mathieu-Daudé
2024-05-08 13:06 ` [PATCH 2/5] hw/intc/loongarch_ipi: Rename as loongson_ipi Jiaxun Yang
2024-05-08 16:24   ` Philippe Mathieu-Daudé
2024-05-08 13:06 ` [PATCH 3/5] hw/intc/loongson_ipi: Implement IOCSR address space for MIPS Jiaxun Yang
2024-05-08 16:21   ` Philippe Mathieu-Daudé
2024-05-08 13:06 ` [PATCH 4/5] hw/intc/loongson_ipi: Provide per core MMIO address spaces Jiaxun Yang
2024-05-08 13:06 ` [PATCH 5/5] hw/mips/loongson3_virt: Wire up loongson_ipi device Jiaxun Yang
2024-05-08 21:41 ` [PATCH 0/5] hw/mips/loongson3_virt: Implement IPI support Philippe Mathieu-Daudé
2024-05-16 10:53   ` Jiaxun Yang

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=20240508-loongson3-ipi-v1-0-1a7b67704664@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=chenhuacai@kernel.org \
    --cc=gaosong@loongson.cn \
    --cc=philmd@linaro.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).