search for: eparse

...onfigurations. So PV ticketlock as well as Xen and > >>KVM support was compiled in. I think booting the kernel on bare > >>metal will cause the Xen code to work in HVM mode thus activating > >>the PV spinlock code which has a negative impact on performance. > >Huh? -EPARSE > > > >>That may be why it was disabled so that the bare metal performance > >>will not be impacted. > >I am not following you. > > What I am saying is that when XEN and PV spinlock is compiled into > the current upstream kernel, the PV spinlock jump label is...

...onfigurations. So PV ticketlock as well as Xen and > >>KVM support was compiled in. I think booting the kernel on bare > >>metal will cause the Xen code to work in HVM mode thus activating > >>the PV spinlock code which has a negative impact on performance. > >Huh? -EPARSE > > > >>That may be why it was disabled so that the bare metal performance > >>will not be impacted. > >I am not following you. > > What I am saying is that when XEN and PV spinlock is compiled into > the current upstream kernel, the PV spinlock jump label is...

...kernel for all configurations. So PV ticketlock as well as Xen and >> KVM support was compiled in. I think booting the kernel on bare >> metal will cause the Xen code to work in HVM mode thus activating >> the PV spinlock code which has a negative impact on performance. > Huh? -EPARSE > >> That may be why it was disabled so that the bare metal performance >> will not be impacted. > I am not following you. What I am saying is that when XEN and PV spinlock is compiled into the current upstream kernel, the PV spinlock jump label is turned on when booted on bare...

On Wed, Apr 02, 2014 at 10:10:17PM -0400, Waiman Long wrote: > On 04/02/2014 04:35 PM, Waiman Long wrote: > >On 04/02/2014 10:32 AM, Konrad Rzeszutek Wilk wrote: > >>On Wed, Apr 02, 2014 at 09:27:29AM -0400, Waiman Long wrote: > >>>N.B. Sorry for the duplicate. This patch series were resent as the > >>> original one was rejected by the vger.kernel.org

On Wed, Apr 02, 2014 at 10:10:17PM -0400, Waiman Long wrote: > On 04/02/2014 04:35 PM, Waiman Long wrote: > >On 04/02/2014 10:32 AM, Konrad Rzeszutek Wilk wrote: > >>On Wed, Apr 02, 2014 at 09:27:29AM -0400, Waiman Long wrote: > >>>N.B. Sorry for the duplicate. This patch series were resent as the > >>> original one was rejected by the vger.kernel.org

...s a single > kernel for all configurations. So PV ticketlock as well as Xen and > KVM support was compiled in. I think booting the kernel on bare > metal will cause the Xen code to work in HVM mode thus activating > the PV spinlock code which has a negative impact on performance. Huh? -EPARSE > That may be why it was disabled so that the bare metal performance > will not be impacted. I am not following you. > > BTW, could you send me more information about the configuration of > the machine, like the .config file that you used? Marcos, could you please send that infor...

...s a single > kernel for all configurations. So PV ticketlock as well as Xen and > KVM support was compiled in. I think booting the kernel on bare > metal will cause the Xen code to work in HVM mode thus activating > the PV spinlock code which has a negative impact on performance. Huh? -EPARSE > That may be why it was disabled so that the bare metal performance > will not be impacted. I am not following you. > > BTW, could you send me more information about the configuration of > the machine, like the .config file that you used? Marcos, could you please send that infor...