Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-05 Thread Jan Kiszka
On 2011-12-05 14:35, Marcelo Tosatti wrote: > On Sat, Dec 03, 2011 at 12:45:51PM +0100, Jan Kiszka wrote: I was referring to the relation between the IOCTL and kvmclock, but IOCTL vs. kvm_run. Jan >>> >>> Ah, OK. Yes, we better characterize it as KVMCLOCK specific (a generic >>>

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-05 Thread Marcelo Tosatti
On Sat, Dec 03, 2011 at 12:45:51PM +0100, Jan Kiszka wrote: > >> I was referring to the relation between the IOCTL and kvmclock, but > >> IOCTL vs. kvm_run. > >> > >> Jan > > > > Ah, OK. Yes, we better characterize it as KVMCLOCK specific (a generic > > "guest is paused" command is not the scope o

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-05 Thread Eric B Munson
On Sat, 03 Dec 2011, Jan Kiszka wrote: > On 2011-12-02 22:27, Eric B Munson wrote: > > On Fri, 02 Dec 2011, Jan Kiszka wrote: > > > >> On 2011-12-02 20:19, Eric B Munson wrote: > >>> Often when a guest is stopped from the qemu console, it will report > >>> spurious > >>> soft lockup warnings on

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-03 Thread Jan Kiszka
On 2011-12-03 12:42, Marcelo Tosatti wrote: > On Sat, Dec 03, 2011 at 12:25:37PM +0100, Jan Kiszka wrote: >> On 2011-12-03 12:19, Marcelo Tosatti wrote: >>> On Sat, Dec 03, 2011 at 10:06:56AM +0100, Jan Kiszka wrote: On 2011-12-02 22:27, Eric B Munson wrote: > On Fri, 02 Dec 2011, Jan Kisz

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-03 Thread Marcelo Tosatti
On Sat, Dec 03, 2011 at 12:25:37PM +0100, Jan Kiszka wrote: > On 2011-12-03 12:19, Marcelo Tosatti wrote: > > On Sat, Dec 03, 2011 at 10:06:56AM +0100, Jan Kiszka wrote: > >> On 2011-12-02 22:27, Eric B Munson wrote: > >>> On Fri, 02 Dec 2011, Jan Kiszka wrote: > >>> > On 2011-12-02 20:19, Eri

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-03 Thread Jan Kiszka
On 2011-12-03 12:19, Marcelo Tosatti wrote: > On Sat, Dec 03, 2011 at 10:06:56AM +0100, Jan Kiszka wrote: >> On 2011-12-02 22:27, Eric B Munson wrote: >>> On Fri, 02 Dec 2011, Jan Kiszka wrote: >>> On 2011-12-02 20:19, Eric B Munson wrote: > Often when a guest is stopped from the qemu cons

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-03 Thread Marcelo Tosatti
On Sat, Dec 03, 2011 at 10:06:56AM +0100, Jan Kiszka wrote: > On 2011-12-02 22:27, Eric B Munson wrote: > > On Fri, 02 Dec 2011, Jan Kiszka wrote: > > > >> On 2011-12-02 20:19, Eric B Munson wrote: > >>> Often when a guest is stopped from the qemu console, it will report > >>> spurious > >>> soft

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-03 Thread Jan Kiszka
On 2011-12-02 22:27, Eric B Munson wrote: > On Fri, 02 Dec 2011, Jan Kiszka wrote: > >> On 2011-12-02 20:19, Eric B Munson wrote: >>> Often when a guest is stopped from the qemu console, it will report spurious >>> soft lockup warnings on resume. There are kernel patches being discussed >>> that

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-02 Thread Eric B Munson
On Fri, 02 Dec 2011, Jan Kiszka wrote: > On 2011-12-02 20:19, Eric B Munson wrote: > > Often when a guest is stopped from the qemu console, it will report spurious > > soft lockup warnings on resume. There are kernel patches being discussed > > that > > will give the host the ability to tell the

Re: [Qemu-devel] [PATCH V3] Guest stop notification

2011-12-02 Thread Jan Kiszka
On 2011-12-02 20:19, Eric B Munson wrote: > Often when a guest is stopped from the qemu console, it will report spurious > soft lockup warnings on resume. There are kernel patches being discussed that > will give the host the ability to tell the guest that it is being stopped and > should ignore t

[Qemu-devel] [PATCH V3] Guest stop notification

2011-12-02 Thread Eric B Munson
Often when a guest is stopped from the qemu console, it will report spurious soft lockup warnings on resume. There are kernel patches being discussed that will give the host the ability to tell the guest that it is being stopped and should ignore the soft lockup warning that generates. Signed-off