Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp3701132ybk; Tue, 19 May 2020 10:52:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyrjNXNiUkX0WwaBQ8wPLAPAdLfrMmzzVkDDvuM5aaS1Pp/2q8sg9u5bLCszSmULiBy0c+1 X-Received: by 2002:aa7:cac8:: with SMTP id l8mr105813edt.103.1589910772917; Tue, 19 May 2020 10:52:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589910772; cv=none; d=google.com; s=arc-20160816; b=fTPE4YjxroXkdRKt42eC9oFpCIGKC2G31srE4q3lRQsOSPEIVuDZENX6E33cy2BGeI iZtp6Kq6p6Cj0DjPszybMyaJh7l7YzH0dpdK6INa3/kr1crNB8bul3io1V5K+STg+AbD iJNnmVRwqg2lFapGz6Sfkmxm7WfdL7k6qNLTRy59ZxN2gaoTsANdSeyt6vWqvChbVGsd IRcxKUScuymWhePxj6dOEdvxmcXbJvRnj/ZNmZW0XKnQDxh3eAZ4OC2DDA5KrFU/0DRE l0ujzhxusH+ykTWyfJK5IeeSePuPebgFhOyYhjEZe8NIfWwuzFwpcEEGiLGR13N0tbAd xaGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:mail-followup-to:message-id:subject:cc:to :from:date; bh=Z2HatgWSQDXCIJR1TD/5IkhffwDejm5qyrUotSrbU04=; b=sIuXKpk45H4HWzef8SF7pgRTHPcHI7R9jdztPTydV6CXNnMAvd+YdsPUY6sUIysbdI nLXrZN6L6k7syv2PTqELFClrRUWMfFHqu5Q3hsZJAq25TrMILCwiUjsBXqoMK8EPhvCE U9e9CJVmVVl+SRTKWGp5QndARuh/kiq/WE4cvYz9FZ6LdQrmMsavIesQJsG+xDG8QNuG +bkNhniqfGsLVMn+/n9VIRxpufbeiInLQGjWMdIRaZ0IhupjDySwUXCQiv5f62nzFN7K aiCh6i+vopGqsztBWqhr0fVB/b78r/YjXvSKDdiWVOPQP28dnXEEVKDRZPg9ZEbjnqKl yDjA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=vmware.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ch20si340777ejb.31.2020.05.19.10.52.29; Tue, 19 May 2020 10:52:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=vmware.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729267AbgESRsS (ORCPT + 99 others); Tue, 19 May 2020 13:48:18 -0400 Received: from ex13-edg-ou-002.vmware.com ([208.91.0.190]:35950 "EHLO EX13-EDG-OU-002.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726059AbgESRsS (ORCPT ); Tue, 19 May 2020 13:48:18 -0400 Received: from sc9-mailhost2.vmware.com (10.113.161.72) by EX13-EDG-OU-002.vmware.com (10.113.208.156) with Microsoft SMTP Server id 15.0.1156.6; Tue, 19 May 2020 10:48:15 -0700 Received: from localhost (unknown [10.200.192.41]) by sc9-mailhost2.vmware.com (Postfix) with ESMTP id 912B1B2906; Tue, 19 May 2020 13:48:17 -0400 (EDT) Date: Tue, 19 May 2020 10:48:17 -0700 From: Matt Helsley To: Josh Poimboeuf CC: , Peter Zijlstra , Julien Thierry , Miroslav Benes , Steven Rostedt Subject: Re: [RFC][PATCH 4/5] objtool: Enable compilation of objtool for all architectures Message-ID: <20200519174817.GR9040@rlwimi.vmware.com> Mail-Followup-To: Matt Helsley , Josh Poimboeuf , linux-kernel@vger.kernel.org, Peter Zijlstra , Julien Thierry , Miroslav Benes , Steven Rostedt References: <9f709ea2ae66cc03b3ff3329baa8f670ccd0e368.1588888003.git.mhelsley@vmware.com> <20200515205610.fmdimt7wbafypuqc@treble> <20200518195045.GQ9040@rlwimi.vmware.com> <20200518222754.cp7vh2qp76khfy4r@treble> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20200518222754.cp7vh2qp76khfy4r@treble> Received-SPF: None (EX13-EDG-OU-002.vmware.com: mhelsley@vmware.com does not designate permitted sender hosts) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 18, 2020 at 05:27:54PM -0500, Josh Poimboeuf wrote: > On Mon, May 18, 2020 at 12:50:45PM -0700, Matt Helsley wrote: > > > Why were these moved to arch.h? They're not necessarily arch-specific, > > > but rather "check"-specific, so I think they still belong in check.h, if > > > possible. > > > > Ah, found it. They are arch specific due to struct orc_entry, which is > > presently not defined for any archs besides x86. > > > > Prior to the patch (-> means "includes"): > > check.h -> asm/orc_types.h (defines struct orc_entry) > > orc_gen.c -> check,h > > > > After patch: > > check.c -> asm/orc_types.h > > orc_gen.c -> asm/orc_types.h > > orc_gen.c -> check.h > > orc_gen.c -> arch.h > > { now weak.c } -> check.h > > > > So this prevents the headers, which help us keep the weak definitions > > consistent with the strong definitions, from breaking compiles on archs > > that lack struct orc_entry. > > > > I'm not sure what the best way to remove this dependency is without > > a nasty void * for the orc entry, or some #ifdef games related to > > checking for cpp defines from asm/orc_types.h. This approach neatly > > avoids conditional preprocessor games and type casting though I do > > agree it's surprising. > > > > Do you have any advice here? > > Would it work if we just move the check() and orc_dump() prototypes to > objtool.h? Then weak.c can just include objtool.h. And check.h and > orc.h would only need to be included for arches which implement them. OK, I tested that and it works well. In fact it simplifies the includes a bit so I think it might be the right move. Cheers, -Matt Helsley