>> > I notice this doesn't seem to have gone in yet -- whose tree is it
>> > going to go via?
>>
>> I'd guess ARM tree (due to almost sole user virt-arm).
>> (there are toy users like microvm and new loongarch)
>
>OK; applied to target-arm.next, thanks.
Thanks, Peter.
Keqian.
On Wed, 21 Sept 2022 at 14:22, Igor Mammedov wrote:
>
> On Tue, 20 Sep 2022 14:15:36 +0100
> Peter Maydell wrote:
>
> > On Wed, 24 Aug 2022 at 16:04, Igor Mammedov wrote:
> > >
> > > On Tue, 16 Aug 2022 17:49:57 +0800
> > > Keqian Zhu wrote:
> > >
> > > > Setup an ARM virtual machine of
On Tue, 20 Sep 2022 14:15:36 +0100
Peter Maydell wrote:
> On Wed, 24 Aug 2022 at 16:04, Igor Mammedov wrote:
> >
> > On Tue, 16 Aug 2022 17:49:57 +0800
> > Keqian Zhu wrote:
> >
> > > Setup an ARM virtual machine of machine virt and execute qmp
> > > "query-acpi-ospm-status"
> > > causes
On Wed, 24 Aug 2022 at 16:04, Igor Mammedov wrote:
>
> On Tue, 16 Aug 2022 17:49:57 +0800
> Keqian Zhu wrote:
>
> > Setup an ARM virtual machine of machine virt and execute qmp
> > "query-acpi-ospm-status"
> > causes segmentation fault with following dumpstack:
> > #1 0xab64235c in
On Tue, 16 Aug 2022 17:49:57 +0800
Keqian Zhu wrote:
> Setup an ARM virtual machine of machine virt and execute qmp
> "query-acpi-ospm-status"
> causes segmentation fault with following dumpstack:
> #1 0xab64235c in qmp_query_acpi_ospm_status
> (errp=errp@entry=0xf030) at
Setup an ARM virtual machine of machine virt and execute qmp
"query-acpi-ospm-status"
causes segmentation fault with following dumpstack:
#1 0xab64235c in qmp_query_acpi_ospm_status
(errp=errp@entry=0xf030) at ../monitor/qmp-cmds.c:312
#2 0xabfc4e20 in
