[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <71f7d41b-1822-d0b5-a28a-b10172bc5746@oracle.com>
Date: Wed, 16 Jan 2019 10:07:54 -0500
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: Juergen Gross <jgross@...e.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 1/16/19 9:33 AM, Juergen Gross wrote:
> 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?
>
I can add this while committing, I don't think it's worth a whole new patch.
One outstanding question I have is whether anything needs to be added to
the commit message (Thomas had some questions)
-boris
Powered by blists - more mailing lists