On 08:59 Mon 20 Jun , Richard Henderson wrote:
> On 6/20/22 07:24, Luc Michel wrote:
> > Hi,
> >
> > This series implements a clean way for semihosted exit syscalls to
> > terminate QEMU with a given return code.
> >
> > Until now, exit syscalls implementations consisted in calling exit()
> >
On Mon, 20 Jun 2022 at 16:10, Luc Michel wrote:
>
> On 15:35 Mon 20 Jun , Peter Maydell wrote:
> > On Mon, 20 Jun 2022 at 15:25, Luc Michel wrote:
> > > This series implements a clean way for semihosted exit syscalls to
> > > terminate QEMU with a given return code.
> > >
> > > Until now, exi
On 6/20/22 07:24, Luc Michel wrote:
Hi,
This series implements a clean way for semihosted exit syscalls to
terminate QEMU with a given return code.
Until now, exit syscalls implementations consisted in calling exit()
with the wanted return code. The problem with this approach is that
other CPUs
On 15:35 Mon 20 Jun , Peter Maydell wrote:
> On Mon, 20 Jun 2022 at 15:25, Luc Michel wrote:
> > This series implements a clean way for semihosted exit syscalls to
> > terminate QEMU with a given return code.
> >
> > Until now, exit syscalls implementations consisted in calling exit()
> > with
On Mon, 20 Jun 2022 at 15:25, Luc Michel wrote:
> This series implements a clean way for semihosted exit syscalls to
> terminate QEMU with a given return code.
>
> Until now, exit syscalls implementations consisted in calling exit()
> with the wanted return code. The problem with this approach is
Hi,
This series implements a clean way for semihosted exit syscalls to
terminate QEMU with a given return code.
Until now, exit syscalls implementations consisted in calling exit()
with the wanted return code. The problem with this approach is that
other CPUs are not properly stopped, leading to
