All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>, roger.pau@citrix.com
Cc: Julien Grall <julien.grall@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Jan Beulich <JBeulich@suse.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen/common: Drop function calls for Xen compile/version information
Date: Tue, 17 Jan 2017 15:46:30 -0500	[thread overview]
Message-ID: <20170117204630.GC21336@char.us.oracle.com> (raw)
In-Reply-To: <17c9a588-f3fd-04b4-1843-9ae5c5d9c6cf@citrix.com>

> > Is this patch of yours that neccessary? Could at least some of the
> > functions still exist?
> 
> Well.  This patch is manually doing what LTO would do automatically when
> it has a cross-translation-unit view of things, and come to the
> conclusion that in all cases, inlining cross-unit will make the calling
> code shorter, and allow the functions to be elided entirely.
> 
> I take it from this that noone has tried livepatching an LTO build of Xen.

Roger did build it (FreeBSD uses it), but I don't think he tried
the test-cases.

Wait, I think he may have as his patch: f8c66c2ad2efdb281e4ebf15bf329d73c4f02ce7
Author: Roger Pau Monne <roger.pau@citrix.com>
Date:   Tue May 3 12:55:09 2016 +0200

    xen/xsplice: add ELFOSABI_FREEBSD as a supported OSABI for payloads

implies that he did build an payload (and I remember us trying to figure
out if the issues he had been hitting were due to LTO or something else).


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-01-17 20:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 13:04 [PATCH] xen/common: Drop function calls for Xen compile/version information Andrew Cooper
2017-01-16 13:18 ` Jan Beulich
2017-01-16 13:26   ` Andrew Cooper
2017-01-16 18:23 ` Stefano Stabellini
2017-01-16 19:44 ` Doug Goldstein
2017-01-17 18:05 ` Konrad Rzeszutek Wilk
2017-01-17 18:16   ` Andrew Cooper
2017-01-17 18:42     ` Konrad Rzeszutek Wilk
2017-01-17 19:00       ` Konrad Rzeszutek Wilk
2017-01-17 20:39         ` Andrew Cooper
2017-01-17 20:46           ` Konrad Rzeszutek Wilk [this message]
2017-01-18 10:13             ` Roger Pau Monné
2017-01-18 16:10               ` Konrad Rzeszutek Wilk
2017-01-18 16:21                 ` Roger Pau Monné
2017-01-18 16:30                   ` Wei Liu
2017-01-18 17:04                     ` Andrew Cooper
2017-01-18 19:01                       ` Doug Goldstein

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=20170117204630.GC21336@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.org \
    /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.