> -----Original Message----- > > > From: Dan Carpenter [mailto:dan.carpen...@oracle.com] > > > Sent: Tuesday, July 8, 2014 17:27 PM > > > To: Dexuan Cui > > > Cc: gre...@linuxfoundation.org; linux-ker...@vger.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 VM screen > by > > > force on VM panic > > > > > > Don't use likely/unlikely unless you have benchmark numbers to show > that > > > it makes a speed up. > > > > > > regards, > > > dan carpenter > > > > Hi Dan, > > Here the variable 'synchronous_fb' is only set to true when the system > panics. > > So before the system panics, it's always 'unlikely'. :-) > > Then take advantage of gcc's and your processor's prediction, which > knows that 0 is the "common" case and will choose to do the right thing > here. > > Dan is right, never put those markings in your code unless you can > benchmark the difference. Which means in reality, never put them in > your code. > > gerg k-h
OK, let me send out a v3 patch, which will remove the unlikely. Thanks, -- Dexuan _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
