[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <efaf168e-feca-2c09-96e1-3f58be9853bf@suse.com>
Date: Wed, 16 Jan 2019 15:33:24 +0100
From: Juergen Gross <jgross@...e.com>
To: Boris Ostrovsky <boris.ostrovsky@...cle.com>
Cc: Hans van Kranenburg <hans@...rrie.org>,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
x86@...nel.org, sstabellini@...nel.org, hpa@...or.com,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
stable@...r.kernel.org
Subject: Re: [PATCH v3] xen: Fix x86 sched_clock() interface for xen
On 16/01/2019 14:17, Boris Ostrovsky wrote:
> On Wed, Jan 16, 2019 at 08:50:13AM +0100, Juergen Gross wrote:
>
>> @@ -1650,13 +1650,14 @@ void xen_callback_vector(void)
>> xen_have_vector_callback = 0;
>> return;
>> }
>> - pr_info("Xen HVM callback vector for event delivery is
>> enabled\n");
>> + if (!silent)
>> + pr_info("Xen HVM callback vector for event
>> delivery is enabled\n");
>
> How about replacing pr_info() with pr_info_once()?
What a nice and simple idea!
Extra patch or V4?
Juergen
Powered by blists - more mailing lists