From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Hotpatch construction and __LINE__ Date: Wed, 12 Aug 2015 10:55:38 +0100 Message-ID: <55CB181A.4000809@citrix.com> References: <1438024817-26942-1-git-send-email-konrad.wilk@oracle.com> <55C1CF8E.5090907@amazon.com> <55C20EC3.9080102@citrix.com> <55CB1B450200007800099F60@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZPSl5-00018w-Sv for xen-devel@lists.xenproject.org; Wed, 12 Aug 2015 09:55:43 +0000 In-Reply-To: <55CB1B450200007800099F60@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: elena.ufimtseva@oracle.com, jeremy@goop.org, hanweidong@huawei.com, john.liuqiming@huawei.com, paul.voccio@rackspace.com, Konrad Rzeszutek Wilk , daniel.kiper@oracle.com, major.hayden@rackspace.com, liuyingdong@huawei.com, aliguori@amazon.com, xiantao.zxt@alibaba-inc.com, steven.wilson@rackspace.com, peter.huangpeng@huawei.com, msw@amazon.com, xen-devel@lists.xenproject.org, rick.harris@rackspace.com, josh.kearney@rackspace.com, jinsong.liu@alibaba-inc.com, amesserl@rackspace.com, Martin Pohlack , dslutz@verizon.com, fanhenglong@huawei.com, Bjoern Doebel List-Id: xen-devel@lists.xenproject.org On 12/08/15 09:09, Jan Beulich wrote: >>>> On 05.08.15 at 15:25, wrote: >> Jan had a plan to make Xen read its own DWARF symbol table rather than >> using the current cludge we have where we partially link Xen, extract >> the public symbol table, rewrite symbol-offsets.c and relink it onto the >> end. > Either I mis-expressed this, or you mis-remember: I'm in no way > intending to use DWARF information. What I want to use is the > _full_ ELF / COFF symbol table instead of nm output (which has > quite a bit of interesting information discarded). I misremembered. Sorry. > >> Perhaps there is an opportunity to piggy-back onto that and have all >> file/line references coming from the DWARF information. I suspect this >> will be similar to what Linux does, as it already has support for using >> its own DWARF/STABS information. > I'm curious where you found this as I'm unaware of such > functionality. The x86 linker script includes the information (given appropriate CONFIG_ options), and the perf subsystem appears to have code to interpret itself. ~Andrew > Recently they even decided to discard all > .eh_frame / .dwarf_frame generating annotations the > compiler can't itself generate. > > Jan >