Re: qemu-system-s390x hang in tcg

On 6/29/22 16:16, Sven Schnelle wrote: Thanks, that was very helpful. I added debugging and it turned out that the TB is left because of a pending irq. The code then calls s390_cpu_exec_interrupt: bool s390_cpu_exec_interrupt(CPUState *cs, int interrupt_request) { if (interrupt_request & CP

Re: qemu-system-s390x hang in tcg

Sven Schnelle writes: > Sven Schnelle writes: > >> Alex Bennée writes: >> >>> Sven Schnelle writes: >>> Hi, David Hildenbrand writes: > On 04.05.22 09:37, Janosch Frank wrote: >> I had a short look yesterday and the boot usually hangs in the raid6 >> code. D

Re: qemu-system-s390x hang in tcg

Alex Bennée writes: > Sven Schnelle writes: > >> Hi, >> >> David Hildenbrand writes: >> >>> On 04.05.22 09:37, Janosch Frank wrote: I had a short look yesterday and the boot usually hangs in the raid6 code. Disabling vector instructions didn't make a difference but a few interr

qemu-system-s390x hang in tcg (was: Re: [PATCH v8 23/70] mm/mmap: change do_brk_flags() to expand existing VMA and add do_brk_munmap())

Hi, David Hildenbrand writes: > On 04.05.22 09:37, Janosch Frank wrote: >> I had a short look yesterday and the boot usually hangs in the raid6 >> code. Disabling vector instructions didn't make a difference but a few >> interruptions via GDB solve the problem for some reason. >> >> CCing Dav

Re: qemu-system-s390x hang in tcg

Sven Schnelle writes: > Alex Bennée writes: > >> Sven Schnelle writes: >> >>> Hi, >>> >>> David Hildenbrand writes: >>> On 04.05.22 09:37, Janosch Frank wrote: > I had a short look yesterday and the boot usually hangs in the raid6 > code. Disabling vector instructions didn't make

Re: qemu-system-s390x hang in tcg (was: Re: [PATCH v8 23/70] mm/mmap: change do_brk_flags() to expand existing VMA and add do_brk_munmap())

Sven Schnelle writes: > Hi, > > David Hildenbrand writes: > >> On 04.05.22 09:37, Janosch Frank wrote: >>> I had a short look yesterday and the boot usually hangs in the raid6 >>> code. Disabling vector instructions didn't make a difference but a few >>> interruptions via GDB solve the probl