All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: elena.ufimtseva@oracle.com, jeremy@goop.org,
	hanweidong@huawei.com, john.liuqiming@huawei.com,
	paul.voccio@rackspace.com,
	Konrad Rzeszutek Wilk <konrad@kernel.org>,
	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 <mpohlack@amazon.com>,
	dslutz@verizon.com, fanhenglong@huawei.com,
	Bjoern Doebel <doebel@amazon.de>
Subject: Re: Hotpatch construction and __LINE__
Date: Wed, 12 Aug 2015 10:55:38 +0100	[thread overview]
Message-ID: <55CB181A.4000809@citrix.com> (raw)
In-Reply-To: <55CB1B450200007800099F60@prv-mh.provo.novell.com>

On 12/08/15 09:09, Jan Beulich wrote:
>>>> On 05.08.15 at 15:25, <andrew.cooper3@citrix.com> 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
>

  reply	other threads:[~2015-08-12  9:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 19:20 [RFC PATCH v3.1] xSplice design Konrad Rzeszutek Wilk
2015-07-27 19:20 ` [RFC PATCH v3.1 1/2] xsplice: rfc.v3.1 Konrad Rzeszutek Wilk
2015-07-30 16:47   ` Johannes Erdfelt
2015-07-31 15:46     ` Konrad Rzeszutek Wilk
2015-08-11 14:17       ` Jan Beulich
2015-07-27 19:20 ` [RFC PATCH v3.1 2/2] xsplice: Add hook for build_id Konrad Rzeszutek Wilk
2015-07-28 15:51   ` Andrew Cooper
2015-07-28 16:35     ` Konrad Rzeszutek Wilk
2015-08-05  8:50   ` Martin Pohlack
2015-08-05  8:58     ` Andrew Cooper
2015-08-05 13:27       ` Martin Pohlack
2015-08-05 14:06         ` (no subject) Martin Pohlack
2015-08-05 14:09         ` [PATCH] xsplice: Use ld-embedded build-ids Martin Pohlack
2015-08-11 14:12           ` Jan Beulich
2015-08-14 12:59             ` Martin Pohlack
2015-08-14 13:54               ` Jan Beulich
2015-08-14 13:57                 ` Martin Pohlack
2015-09-15 18:38                   ` Konrad Rzeszutek Wilk
2015-08-11 14:02   ` [RFC PATCH v3.1 2/2] xsplice: Add hook for build_id Jan Beulich
2015-08-05  8:55 ` Hotpatch construction and __LINE__ (was: [RFC PATCH v3.1] xSplice design.) Martin Pohlack
2015-08-05 13:25   ` Hotpatch construction and __LINE__ Andrew Cooper
2015-08-12  8:09     ` Jan Beulich
2015-08-12  9:55       ` Andrew Cooper [this message]
2015-11-03 18:21   ` Ross Lagerwall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55CB181A.4000809@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=aliguori@amazon.com \
    --cc=amesserl@rackspace.com \
    --cc=daniel.kiper@oracle.com \
    --cc=doebel@amazon.de \
    --cc=dslutz@verizon.com \
    --cc=elena.ufimtseva@oracle.com \
    --cc=fanhenglong@huawei.com \
    --cc=hanweidong@huawei.com \
    --cc=jeremy@goop.org \
    --cc=jinsong.liu@alibaba-inc.com \
    --cc=john.liuqiming@huawei.com \
    --cc=josh.kearney@rackspace.com \
    --cc=konrad@kernel.org \
    --cc=liuyingdong@huawei.com \
    --cc=major.hayden@rackspace.com \
    --cc=mpohlack@amazon.com \
    --cc=msw@amazon.com \
    --cc=paul.voccio@rackspace.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=rick.harris@rackspace.com \
    --cc=steven.wilson@rackspace.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xiantao.zxt@alibaba-inc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.