From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755574AbcKJLjz (ORCPT ); Thu, 10 Nov 2016 06:39:55 -0500 Received: from merlin.infradead.org ([205.233.59.134]:53232 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755391AbcKJLju (ORCPT ); Thu, 10 Nov 2016 06:39:50 -0500 Date: Thu, 10 Nov 2016 12:39:29 +0100 From: Peter Zijlstra To: Thomas Gleixner Cc: "M. Vefa Bicakci" , Sebastian Andrzej Siewior , "Charles (Chas) Williams" , "x86@kernel.org" , LKML , Borislav Petkov , Boris Ostrovsky , David Vrabel , Juergen Gross Subject: Re: [PATCH] x86/cpuid: Deal with broken firmware once more Message-ID: <20161110113929.GV3142@twins.programming.kicks-ass.net> References: <58e229e2-91f4-a97f-1b9f-089f48ef994a@brocade.com> <86609338-2b45-ed7e-fb07-99421e43a2f1@brocade.com> <49fe8cc5-0f0f-6cac-7a5c-803e81f5667d@runbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 10, 2016 at 12:13:04PM +0100, Thomas Gleixner wrote: > What's so wrong with storing the fricking firmware supplied APICid as > everybody else does and report it back when queried? > > This damned attitude of we just hack the code into submission and let > everybody else deal with the outcoming is utterly annoying. At some point I'd recommend just marking things BROKEN and getting on with life. There's only so much crap you can deal with. What Xen does here is completely insane.