[v1] loongarch queue

[PULL 0/3] loongarch queue

Posted by Song Gao 1 month ago

The following changes since commit fe11f459f640cd08f35c21f9d403517951bfd671:

  Merge tag 'fixes-pr-v1' of https://gitlab.com/marcandre.lureau/qemu into staging (2026-08-25 06:48:55 -0700)

are available in the Git repository at:

  https://github.com/gaosong715/qemu.git tags/pull-loongarch-20260826

for you to fetch changes up to dd9641cb140d6e2c297f8d87c7875409e42319b2:

  target/loongarch: Fix SWI interrupt delivery via CSR_ESTAT (2026-08-26 21:40:19 -0400)

----------------------------------------------------------------
pull-loongarch-20260826

----------------------------------------------------------------
Bibo Mao (3):
      hw/loongarch/boot: Check memory boundary in init_boot_rom()
      hw/loongarch/virt: Add bootargs and initrd to device-tree
      target/loongarch: Fix SWI interrupt delivery via CSR_ESTAT

 hw/loongarch/boot.c               | 68 +++++++++++++++++++++++++++++++--------
 hw/loongarch/virt-fdt-build.c     | 27 ++++++++++++++++
 target/loongarch/cpu.c            | 26 +++++++++++----
 target/loongarch/internals.h      |  1 +
 target/loongarch/tcg/csr_helper.c | 10 ++++++
 5 files changed, 113 insertions(+), 19 deletions(-)

Re: [PULL 0/3] loongarch queue

Posted by Michael Tokarev 1 month ago

On 8/27/26 04:28, Song Gao wrote:

> Bibo Mao (3):
>        hw/loongarch/boot: Check memory boundary in init_boot_rom()
>        hw/loongarch/virt: Add bootargs and initrd to device-tree
>        target/loongarch: Fix SWI interrupt delivery via CSR_ESTAT

Is it qemu-stable material?
(Currently active stable branches: 10.0, 11.0, 11.1).

Thanks,

/mjt

Re: [PULL 0/3] loongarch queue

Posted by Bibo Mao 4 weeks, 1 day ago


On 2026/8/28 上午1:25, Michael Tokarev wrote:
> On 8/27/26 04:28, Song Gao wrote:
> 
>> Bibo Mao (3):
>>        hw/loongarch/boot: Check memory boundary in init_boot_rom()
>>        hw/loongarch/virt: Add bootargs and initrd to device-tree
>>        target/loongarch: Fix SWI interrupt delivery via CSR_ESTAT
> 
> Is it qemu-stable material?
> (Currently active stable branches: 10.0, 11.0, 11.1).
I think it should be applied to qemu-stable, currently it can apply to 
11.0 and later, there is big conflict on 10.0.

Regards
Bibo Mao
> 
> Thanks,
> 
> /mjt

Re: [PULL 0/3] loongarch queue

Posted by Michael Tokarev 2 weeks, 3 days ago

On 8/28/26 04:58, Bibo Mao wrote:

>>>        target/loongarch: Fix SWI interrupt delivery via CSR_ESTAT
>>
>> Is it qemu-stable material?
>> (Currently active stable branches: 10.0, 11.0, 11.1).
> I think it should be applied to qemu-stable, currently it can apply to 11.0 and later, there is big conflict on 10.0.

It also conflicts with 11.0, due to v11.0.0-1700-gce969fa50bf
"target/loongarch: Use sys_state in cpu.c when accessing CSR registers".
I think I can apply ce969fa50bf to 11.0 too, but I don't see big value
there, - 11.0.x will have a single last update before reaching end-of-line.
So 11.1.x it is, only, for now.

Thanks,

/mjt

Re: [PULL 0/3] loongarch queue

Posted by Michael Tokarev 2 weeks, 5 days ago

On 8/28/26 04:58, Bibo Mao wrote:
> On 2026/8/28 上午1:25, Michael Tokarev wrote:
>> On 8/27/26 04:28, Song Gao wrote:
>>
>>> Bibo Mao (3):
>>>        hw/loongarch/boot: Check memory boundary in init_boot_rom()
>>>        hw/loongarch/virt: Add bootargs and initrd to device-tree
>>>        target/loongarch: Fix SWI interrupt delivery via CSR_ESTAT
>>
>> Is it qemu-stable material?
>> (Currently active stable branches: 10.0, 11.0, 11.1).
> I think it should be applied to qemu-stable, currently it can apply to 11.0 and later, there is big conflict on 10.0.

I'm sorry for not being explicit here.

My question was about this whole pull request, not about this
particular change :)

Should I pick all 3 or just one (or two)? :)

Thanks,

/mjt

Re: [PULL 0/3] loongarch queue

Posted by Bibo Mao 2 weeks, 5 days ago


On 2026/9/7 下午3:14, Michael Tokarev wrote:
> On 8/28/26 04:58, Bibo Mao wrote:
>> On 2026/8/28 上午1:25, Michael Tokarev wrote:
>>> On 8/27/26 04:28, Song Gao wrote:
>>>
>>>> Bibo Mao (3):
>>>>        hw/loongarch/boot: Check memory boundary in init_boot_rom()
>>>>        hw/loongarch/virt: Add bootargs and initrd to device-tree
>>>>        target/loongarch: Fix SWI interrupt delivery via CSR_ESTAT
>>>
>>> Is it qemu-stable material?
>>> (Currently active stable branches: 10.0, 11.0, 11.1).
>> I think it should be applied to qemu-stable, currently it can apply to 
>> 11.0 and later, there is big conflict on 10.0.
> 
> I'm sorry for not being explicit here.
> 
> My question was about this whole pull request, not about this
> particular change :)
> 
> Should I pick all 3 or just one (or two)? :)
I think that just the single patch3 need be applied to qemu-stable since 
there is Fixes tag.

Regards
Bibo Mao
> 
> Thanks,
> 
> /mjt

Re: [PULL 0/3] loongarch queue

Posted by Richard Henderson 1 month ago

On 8/26/26 18:28, Song Gao wrote:
> The following changes since commit fe11f459f640cd08f35c21f9d403517951bfd671:
> 
>    Merge tag 'fixes-pr-v1' ofhttps://gitlab.com/marcandre.lureau/qemu into staging (2026-08-25 06:48:55 -0700)
> 
> are available in the Git repository at:
> 
>    https://github.com/gaosong715/qemu.git tags/pull-loongarch-20260826
> 
> for you to fetch changes up to dd9641cb140d6e2c297f8d87c7875409e42319b2:
> 
>    target/loongarch: Fix SWI interrupt delivery via CSR_ESTAT (2026-08-26 21:40:19 -0400)
> 
> ----------------------------------------------------------------
> pull-loongarch-20260826
Applied, thanks.

r~