Live Patching
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <mpdesouza@suse.com>
To: laokz <laokz@foxmail.com>, live-patching@vger.kernel.org
Subject: Re: RFC: another way to make livepatch
Date: Wed, 10 Jan 2024 08:52:49 -0300	[thread overview]
Message-ID: <761e2fc21e72576a4704572b50d9fc5b4a1cb9e1.camel@suse.com> (raw)
In-Reply-To: <tencent_8B36A9FCE07A8CA645DC6F3C3F039C52E407@qq.com>

On Thu, 2023-12-21 at 22:06 +0800, laokz wrote:
> Hi,
> 
> Is it off-topic talking about livepatch making tool? I tried another
> way and
> want to get your expert opinion if there any fatal pitfall.

I don't think it's out of scope, but what exactly you mean by "another
way to make livepatch"? You would like to know about different
approaches like source-based livepatch compared to kpatch, or you mean
something different?

Thanks!

> 
> Thanks.
> 
> laokz
> 
> 


  reply	other threads:[~2024-01-10 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 14:06 RFC: another way to make livepatch laokz
2024-01-10 11:52 ` Marcos Paulo de Souza [this message]
2024-01-10 14:06   ` pizza
2024-01-10 16:28     ` Marcos Paulo de Souza
2024-01-11 14:52       ` laokz

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=761e2fc21e72576a4704572b50d9fc5b4a1cb9e1.camel@suse.com \
    --to=mpdesouza@suse.com \
    --cc=laokz@foxmail.com \
    --cc=live-patching@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox