mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
	boris.ostrovsky@oracle.com, david.vrabel@citrix.com
Subject: Re: [Xen-devel] [PATCH] xen: Make VPMU init message look less scary
Date: Mon, 1 Aug 2016 17:48:52 +0200	[thread overview]
Message-ID: <66c1313f-655b-a65e-a84c-05b0e81aed12@suse.com> (raw)
In-Reply-To: <20160801141139.GE21356@char.us.oracle.com>

On 01/08/16 16:11, Konrad Rzeszutek Wilk wrote:
> On Mon, Aug 01, 2016 at 01:41:20PM +0200, 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.
>>
>> Change the message to something less scary in case the hypervisor
>> returns EOPNOTSUPP when trying to activate VPMU.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>>  arch/x86/xen/pmu.c | 7 +++++--
>>  1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/xen/pmu.c b/arch/x86/xen/pmu.c
>> index 32bdc2c..e9d66fa 100644
>> --- a/arch/x86/xen/pmu.c
>> +++ b/arch/x86/xen/pmu.c
>> @@ -547,8 +547,11 @@ void xen_pmu_init(int cpu)
>>  	return;
>>  
>>  fail:
>> -	pr_info_once("Could not initialize VPMU for cpu %d, error %d\n",
>> -		cpu, err);
>> +	if (err == -EOPNOTSUPP)
>> +		pr_info_once("VPMU usage disabled due to Xen settings\n");
> 
> How about 'VPMU disabled by hypevisor.'

Hmm, why not. Boris, are you okay with this message, too?


Juergen

  reply	other threads:[~2016-08-01 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 11:41 Juergen Gross
2016-08-01 14:11 ` Boris Ostrovsky
2016-08-01 14:11 ` [Xen-devel] " Konrad Rzeszutek Wilk
2016-08-01 15:48   ` Juergen Gross [this message]
2016-08-01 15:50     ` Boris Ostrovsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=66c1313f-655b-a65e-a84c-05b0e81aed12@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®