Re: [Qemu-devel] [RFC PATCH] Implement qemu_thread_yield for posix, use it in mttcg to handle EXCP_YIELD

On 1/21/20 5:26 PM, David Gibson wrote: > However, a more common use of qemu is the "pseries" machine type, > which emulates only a guest (in the cpu architectural sense) with qemu > taking the place of the hypervisor as well as emulating the cpus. In > that case the H_CONFER hypercall goes to

Re: [Qemu-devel] [RFC PATCH] Implement qemu_thread_yield for posix, use it in mttcg to handle EXCP_YIELD

On Tue, Jan 21, 2020 at 02:37:59PM +, Alex Bennée wrote: > > Nicholas Piggin writes: > > > Alex Bennée's on December 20, 2019 11:11 pm: > >> > >> Nicholas Piggin writes: > >> > >>> This is a bit of proof of concept in case mttcg becomes more important > >>> yield could be handled like

Re: [Qemu-devel] [RFC PATCH] Implement qemu_thread_yield for posix, use it in mttcg to handle EXCP_YIELD

Nicholas Piggin writes: > Alex Bennée's on December 20, 2019 11:11 pm: >> >> Nicholas Piggin writes: >> >>> This is a bit of proof of concept in case mttcg becomes more important >>> yield could be handled like this. You can have by accident or deliberately >>> force vCPUs onto the same

Re: [Qemu-devel] [RFC PATCH] Implement qemu_thread_yield for posix, use it in mttcg to handle EXCP_YIELD

Alex Bennée's on December 20, 2019 11:11 pm: > > Nicholas Piggin writes: > >> This is a bit of proof of concept in case mttcg becomes more important >> yield could be handled like this. You can have by accident or deliberately >> force vCPUs onto the same physical CPU and cause inversion issues

Re: [Qemu-devel] [RFC PATCH] Implement qemu_thread_yield for posix, use it in mttcg to handle EXCP_YIELD

Nicholas Piggin writes: > This is a bit of proof of concept in case mttcg becomes more important > yield could be handled like this. You can have by accident or deliberately > force vCPUs onto the same physical CPU and cause inversion issues when the > lock holder was preempted by the waiter.

Re: [Qemu-devel] [RFC PATCH] Implement qemu_thread_yield for posix, use it in mttcg to handle EXCP_YIELD

On Wed, Jul 17, 2019 at 03:46:55PM +1000, Nicholas Piggin wrote: > This is a bit of proof of concept in case mttcg becomes more important > yield could be handled like this. You can have by accident or deliberately > force vCPUs onto the same physical CPU and cause inversion issues when the > lock

[Qemu-devel] [RFC PATCH] Implement qemu_thread_yield for posix, use it in mttcg to handle EXCP_YIELD

This is a bit of proof of concept in case mttcg becomes more important yield could be handled like this. You can have by accident or deliberately force vCPUs onto the same physical CPU and cause inversion issues when the lock holder was preempted by the waiter. This is lightly tested but not to