[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD8Lp45S-0+b4ZjT=1xbq4ijFzQ4eC89QK=TVQn3A0ZKyeE0iA@mail.gmail.com>
Date: Thu, 15 Aug 2019 13:02:07 +0800
From: Daniel Drake <drake@...lessm.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@....com>,
"Li, Aubrey" <aubrey.li@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Endless Linux Upstreaming Team <linux@...lessm.com>,
Jiri Slaby <jslaby@...e.cz>
Subject: Re: [PATCH] x86/apic: Handle missing global clockevent gracefully
On Mon, Aug 12, 2019 at 2:16 PM Daniel Drake <drake@...lessm.com> wrote:
> I can do a bit of testing on other platforms too. Are there any
> specific tests I should run, other than checking that the system boots
> and doesn't have any timer watchdog complaints in the log?
Tested this on 2 AMD platforms that were not affected by the crash here.
In addition to confirming that they boot fine without timer complaints
in the logs, I checked the calibrate_APIC_clock() result before and
after this patch. I repeated each test twice.
Asus E402YA (AMD E2-7015)
Before: 99811, 99811
After: 99812, 99812
Acer Aspire A315-21G (AMD A9-9420e)
Before: 99811, 99811
After: 99807, 99820
Those new numbers seem very close to the previous ones and I didn't
observe any problems.
Thanks
Daniel
Powered by blists - more mailing lists