On Mon, 27 Jun 2016, Pavel Machek wrote:
> I believe you want "whenever source of function A influenced code in
> function B, I want to be notified", and I believe it should be
> documented as such.
Well, exactly. IPA is a group of optimizations that are, by definition,
intra-prodcedural.
--
On Mon 2016-06-27 10:26:58, Jiri Kosina wrote:
> On Mon, 27 Jun 2016, Pavel Machek wrote:
>
> > > > I thought that in such case, person creating the live patch should
> > > > notice and adjust patch appropriately, at assembly level if
> > > > neccessary..?
> > >
> > > Yes, that still holds; a lot
On Mon, 27 Jun 2016, Pavel Machek wrote:
> > > I thought that in such case, person creating the live patch should
> > > notice and adjust patch appropriately, at assembly level if
> > > neccessary..?
> >
> > Yes, that still holds; a lot of things could be automated though, and
> > creating the a
On Mon 2016-06-27 10:13:28, Jiri Kosina wrote:
> On Mon, 27 Jun 2016, Pavel Machek wrote:
>
> > > Live patching, as we use it, deliberately disrupts the fabric of
> > > compile units; thus all assumptions a compiler can make about the
> > > control flow may be invalid. As an example, it could anal
On Mon, 27 Jun 2016, Pavel Machek wrote:
> > Live patching, as we use it, deliberately disrupts the fabric of
> > compile units; thus all assumptions a compiler can make about the
> > control flow may be invalid. As an example, it could analyse that a
> > callee does not touch a caller-saved regis
On Mon, Jun 27, 2016 at 12:39:56AM +0200, Pavel Machek wrote:
> Would it be possible to document which kind of guarantees live
> patching needs from compiler?
Sure, here you go, all required guarantees:
Stick to the ABI.
> I always assumed that whoever is preparing the patch does manual
> inves
On Thu 2016-06-23 14:47:03, Jiri Kosina wrote:
> On Thu, 23 Jun 2016, Jiri Kosina wrote:
>
> > > I haven't looked at the fentry solution, but the code I'm involved in
> > > saves
> > > the registers so that ftrace, live patch and friends can work freely. But
> > > then it restores all regs and _t
On Wed 2016-06-22 16:24:41, Torsten Duwe wrote:
> Live patching, as we use it, deliberately disrupts the fabric of
> compile units; thus all assumptions a compiler can make about the
> control flow may be invalid. As an example, it could analyse that a
> callee does not touch a caller-saved registe
On Thu, 23 Jun 2016, Jiri Kosina wrote:
> > I haven't looked at the fentry solution, but the code I'm involved in saves
> > the registers so that ftrace, live patch and friends can work freely. But
> > then it restores all regs and _then_ calls the replacement, so ftrace
> > saving all regs is no
On Thu, 23 Jun 2016, Torsten Duwe wrote:
> I haven't looked at the fentry solution, but the code I'm involved in saves
> the registers so that ftrace, live patch and friends can work freely. But
> then it restores all regs and _then_ calls the replacement, so ftrace
> saving all regs is no gain at
On Thu, Jun 23, 2016 at 09:45:48AM +0200, Miroslav Benes wrote:
>
> Hi,
>
> On Wed, 22 Jun 2016, Josh Poimboeuf wrote:
>
> > On Wed, Jun 22, 2016 at 04:24:41PM +0200, Torsten Duwe wrote:
> > > Live patching, as we use it, deliberately disrupts the fabric of
> > > compile units; thus all assumpti
Hi,
On Wed, 22 Jun 2016, Josh Poimboeuf wrote:
> On Wed, Jun 22, 2016 at 04:24:41PM +0200, Torsten Duwe wrote:
> > Live patching, as we use it, deliberately disrupts the fabric of
> > compile units; thus all assumptions a compiler can make about the
> > control flow may be invalid. As an example
On Wed, Jun 22, 2016 at 04:24:41PM +0200, Torsten Duwe wrote:
> Live patching, as we use it, deliberately disrupts the fabric of
> compile units; thus all assumptions a compiler can make about the
> control flow may be invalid. As an example, it could analyse that a
> callee does not touch a caller
Live patching, as we use it, deliberately disrupts the fabric of
compile units; thus all assumptions a compiler can make about the
control flow may be invalid. As an example, it could analyse that a
callee does not touch a caller-saved register at all, so why waste
memory bandwidth saving it? The r
14 matches
Mail list logo
