From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751796AbcAVA2N (ORCPT <rfc822;w@1wt.eu>);
	Thu, 21 Jan 2016 19:28:13 -0500
Received: from mx2.suse.de ([195.135.220.15]:34045 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750876AbcAVA2L (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 21 Jan 2016 19:28:11 -0500
Date: Fri, 22 Jan 2016 01:28:06 +0100
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
        Michael Brown <mcb30@ipxe.org>,
        Peter Senna Tschudin <peter.senna@gmail.com>,
        Andrey Ryabinin <ryabinin.a.a@gmail.com>,
        Jan Beulich <JBeulich@suse.com>, qiuxishi@huawei.com,
        Boris Ostrovsky <boris.ostrovsky@oracle.com>,
        "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
        joro@8bytes.org, X86 ML <x86@kernel.org>,
        Ingo Molnar <mingo@redhat.com>, aryabinin@virtuozzo.com,
        Michael Matz <matz@suse.de>,
        Mauro Carvalho Chehab <mchehab@osg.samsung.com>, andreyknvl@google.com,
        Rusty Russell <rusty@rustcorp.com.au>, Michal Marek <mmarek@suse.com>,
        Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>,
        Valentin Rothberg <valentinrothberg@gmail.com>,
        Juergen Gross <jgross@suse.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Andy Lutomirski <luto@amacapital.net>, long.wanglong@huawei.com
Subject: Re: [Xen-devel] [RFC v1 0/8] x86/init: Linux linker tables
Message-ID: <20160122002805.GH20964@wotan.suse.de>
References: <1450217797-19295-1-git-send-email-mcgrof@do-not-panic.com>
 <56731D32.4040900@zytor.com>
 <20151217234625.GM20409@wotan.suse.de>
 <56738AAF.2080601@zytor.com>
 <56738E29.3070605@zytor.com>
 <56A13D42.7040500@zytor.com>
 <CAB=NE6Ueg4C=FVWGtXSHOcWKBJt1ihS0c_LQnuf7KjhyJBDE6A@mail.gmail.com>
 <20160121213732.GG15622@localhost.localdomain>
 <CAB=NE6WxMqiqQ30JzOemTACm_X2DHMy=ba37sOrOZZDVntoCMQ@mail.gmail.com>
 <56A17033.4090709@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <56A17033.4090709@zytor.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Jan 21, 2016 at 03:56:35PM -0800, H. Peter Anvin wrote:
> On 01/21/16 14:25, Luis R. Rodriguez wrote:
> > On Thu, Jan 21, 2016 at 1:37 PM, Konrad Rzeszutek Wilk
> > <konrad.wilk@oracle.com> wrote:
> >>> Sure, do we know if that ICC compatible? Do we care? There are a
> >>> series of ICC hacks put in place on ipxe's original solution which
> >>> I've folded in, it seems that works but if we care about ICC those
> >>> folks should perhaps help review as well.
> >>
> >> I didn't know the kernel could even be compiled with ICC? Thought
> >> only GCC worked?
> > 
> > I'm happy with that, just wanted to make sure I raise the flag concern
> > given the icc hacks on the linker tables.
> > 
> >> Anyhow - it may be that those fixes were for quite old ICC versions.
> >> Does the latest one manifest these oddities?
> > 
> > I am not sure, I yield to Michael as the author of the original ICC
> > compatibility pieces. If we don't care about ICC let me know and I'll
> > just drop the stuff. In lack of such statements I'll just keep the
> > work arounds in place, but I'm more than trilled to drop it.
> > 
> 
> In general we let the ICC and Clang/LLVM teams communicate with out a
> post facto.  We can't just guess what their requirements are, especially
> since they are likely to change between revisions.

Great. I'm going to drop ICC hacks.

  Luis