Re: [Xen-devel] [PATCH v3] xen: Make VPMU init message look less scary

2016-08-24 Thread David Vrabel
On 02/08/16 08:22, Juergen Gross wrote: > The default for the Xen hypervisor is to not enable VPMU in order to > avoid security issues. In this case the Linux kernel will issue the > message "Could not initialize VPMU for cpu 0, error -95" which looks > more like an error than a normal state. > >

Re: [Xen-devel] [PATCH v3] xen: Make VPMU init message look less scary

2016-08-17 Thread Juergen Gross
On 02/08/16 09:22, Juergen Gross wrote: > The default for the Xen hypervisor is to not enable VPMU in order to > avoid security issues. In this case the Linux kernel will issue the > message "Could not initialize VPMU for cpu 0, error -95" which looks > more like an error than a normal state. > >

Re: [Xen-devel] [PATCH v3] xen: Make VPMU init message look less scary

2016-08-02 Thread Boris Ostrovsky
On 08/02/2016 03:22 AM, Juergen Gross wrote: The default for the Xen hypervisor is to not enable VPMU in order to avoid security issues. In this case the Linux kernel will issue the message "Could not initialize VPMU for cpu 0, error -95" which looks more like an error than a normal state. Cha

[Xen-devel] [PATCH v3] xen: Make VPMU init message look less scary

2016-08-02 Thread Juergen Gross
The default for the Xen hypervisor is to not enable VPMU in order to avoid security issues. In this case the Linux kernel will issue the message "Could not initialize VPMU for cpu 0, error -95" which looks more like an error than a normal state. Change the message to something less scary in case t