[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57062B90.10401@citrix.com>
Date: Thu, 7 Apr 2016 10:42:40 +0100
From: David Vrabel <david.vrabel@...rix.com>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>, <bp@...en8.de>,
<hpa@...or.com>, <tglx@...utronix.de>, <mingo@...hat.com>,
<rusty@...tcorp.com.au>
CC: <xen-devel@...ts.xensource.com>, <matt@...eblueprint.co.uk>,
<andrew.cooper3@...rix.com>, <x86@...nel.org>,
<linux-kernel@...r.kernel.org>, <luto@...capital.net>,
<jlee@...e.com>, <lguest@...ts.ozlabs.org>, <glin@...e.com>,
<david.vrabel@...rix.com>, <boris.ostrovsky@...cle.com>,
<andriy.shevchenko@...ux.intel.com>
Subject: Re: [Xen-devel] [PATCH v4 04/14] x86/rtc: replace paravirt rtc check
with platform legacy quirk
On 07/04/16 01:06, Luis R. Rodriguez wrote:
> We have 4 types of x86 platforms that disable RTC:
>
> * Intel MID
> * Lguest - uses paravirt
> * Xen dom-U - uses paravirt
> * x86 on legacy systems annotated with an ACPI legacy flag
>
> We can consolidate all of these into a platform specific legacy
> quirk set early in boot through i386_start_kernel() and through
> x86_64_start_reservations(). This deals with the RTC quirks which
> we can rely on through the hardware subarch, the ACPI check can
> be dealt with separately.
Xen parts:
Reviewed-by: David Vrabel <david.vrabel@...rix.com>
David
Powered by blists - more mailing lists