ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] live patching
Date: Wed, 8 Jul 2015 23:21:42 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1507082319250.10183@pobox.suse.cz> (raw)
In-Reply-To: <559D4C35.6070709@hitachi.com>

On Thu, 9 Jul 2015, Masami Hiramatsu wrote:

> > - stack unwinding has so far been deemed purely debugging facility, with 
> >   no correctness guarantees whatsoever. One of the possible aproaches to
> >   improving the coverage of live patching infrastructure would assume
> >   100% reliability of in-kernel stack unwinding.
> > 
> >   Is this something that should be pursued further? Especially opinions 
> >   and comments from various arch maintainers would be welcome
> 
> Yeah, at least the live patch would be better to depend on a frame-pointer
> to improve correctness...

I actually think that Josh is planning to add dwarf2 CFI support as well 
(but yes, first step is getting frame pointer based unwinding to work 
properly).

Thanks,

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2015-07-08 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 20:42 Jiri Kosina
2015-07-08 16:13 ` Masami Hiramatsu
2015-07-08 21:21   ` Jiri Kosina [this message]
2015-07-09  3:26   ` Kamezawa Hiroyuki
2015-07-09  9:56     ` Jiri Kosina
2015-07-09 10:05       ` Kamezawa Hiroyuki
2015-10-12 17:13 ` Theodore Ts'o
2015-10-13  9:29   ` Jiri Kosina
2015-10-16 19:34     ` Jiri Kosina

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=alpine.LNX.2.00.1507082319250.10183@pobox.suse.cz \
    --to=jkosina@suse.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=masami.hiramatsu.pt@hitachi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox