Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758534AbcDHSpc (ORCPT ); Fri, 8 Apr 2016 14:45:32 -0400 Received: from mx2.suse.de ([195.135.220.15]:40577 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752950AbcDHSpa (ORCPT ); Fri, 8 Apr 2016 14:45:30 -0400 Date: Fri, 8 Apr 2016 20:45:23 +0200 From: "Luis R. Rodriguez" To: Boris Ostrovsky Cc: Juergen Gross , "Luis R. Rodriguez" , "H. Peter Anvin" , Borislav Petkov , Thomas Gleixner , Ingo Molnar , Rusty Russell , X86 ML , "linux-kernel@vger.kernel.org" , Andy Lutomirski , David Vrabel , Konrad Rzeszutek Wilk , "xen-devel@lists.xensource.com" , lguest@lists.ozlabs.org, Andy Shevchenko , Joey Lee , Gary Lin , Matt Fleming , Andrew Cooper , "Rafael J. Wysocki" , Len Brown , "Moore, Robert" , Lv Zheng , Toshi Kani , ACPI Devel Maling List , kozerkov@parallels.com, Josh Triplett , Joerg Roedel Subject: Re: [PATCH v4 04/14] x86/rtc: replace paravirt rtc check with platform legacy quirk Message-ID: <20160408184523.GP1990@wotan.suse.de> References: <570658DA.7060509@oracle.com> <20160408003207.GN1990@wotan.suse.de> <57073F0F.400@suse.com> <57075201.5080207@suse.com> <57075A0F.2020303@suse.com> <570764F8.6020902@suse.com> <5707A618.7040608@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5707A618.7040608@oracle.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1214 Lines: 25 On Fri, Apr 08, 2016 at 08:37:44AM -0400, Boris Ostrovsky wrote: > On 04/08/2016 03:59 AM, Juergen Gross wrote: > >On 08/04/16 09:36, Luis R. Rodriguez wrote: > >>On Fri, Apr 8, 2016 at 12:13 AM, Juergen Gross wrote: > >>>On 08/04/16 08:56, Luis R. Rodriguez wrote: > >>>>On Thu, Apr 7, 2016 at 11:38 PM, Juergen Gross wrote: > >>>> > >>>>Okay. Another idea (not sure whether this is really a good one): > >>>> > >>>>Add X86_SUBARCH_XEN_DOM0. As hardware_subarch is 32 bits wide I don't > >>>>think the number of subarchs is a scarce resource. :-) > >>This would mean bumping the x86 boot protocol, we shouldn't take that > >>lightly, but given that in this case the new subarch would really only > >>be set by the kernel (or future loaders for perhaps HVMLite) I'd think > >>this is not such an intrusive alternative. > >I think adding an own subarch for dom0 isn't that bad. It really is > >different from domU as dom0 has per default access to the real hardware > >(or at least to most of it). > > Can we do this (overwrite quirks) in x86_init_ops.arch_setup? I'd > really like to avoid adding a what essentially is a sub-subarch. I'm going with this. Will respin. Luis