RE: [PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic

2014-07-08 Thread Dexuan Cui
de...@linuxdriverproject.org; plagn...@jcrosoft.com; > > > tomi.valkei...@ti.com; linux-fb...@vger.kernel.org; o...@aepfle.de; > > > a...@canonical.com; jasow...@redhat.com; Haiyang Zhang > > > Subject: Re: [PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen > by > &

Re: [PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic

2014-07-08 Thread gre...@linuxfoundation.org
.kernel.org; driverdev- > > de...@linuxdriverproject.org; plagn...@jcrosoft.com; > > tomi.valkei...@ti.com; linux-fb...@vger.kernel.org; o...@aepfle.de; > > a...@canonical.com; jasow...@redhat.com; Haiyang Zhang > > Subject: Re: [PATCH v2] video: hyperv: hyperv_fb: refresh the

RE: [PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic

2014-07-08 Thread Dexuan Cui
tomi.valkei...@ti.com; linux-fb...@vger.kernel.org; o...@aepfle.de; > a...@canonical.com; jasow...@redhat.com; Haiyang Zhang > Subject: Re: [PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen by > force on VM panic > > Don't use likely/unlikely unless you have benchmark n

Re: [PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic

2014-07-08 Thread Dan Carpenter
Don't use likely/unlikely unless you have benchmark numbers to show that it makes a speed up. regards, dan carpenter ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

RE: [PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic

2014-07-08 Thread Dexuan Cui
driverdev- > de...@linuxdriverproject.org; plagn...@jcrosoft.com; > tomi.valkei...@ti.com; linux-fb...@vger.kernel.org; o...@aepfle.de; > a...@canonical.com; jasow...@redhat.com > Cc: Haiyang Zhang > Subject: [PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen by force > on VM panic >

[PATCH v2] video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic

2014-06-26 Thread Dexuan Cui
Currently the VSC has no chance to notify the VSP of the dirty rectangle on VM panic because the notification work is done in a workqueue, and in panic() the kernel typically ends up in an infinite loop, and a typical kernel config has CONFIG_PREEMPT_VOLUNTARY=y and CONFIG_PREEMPT is not set, so a