All of lore.kernel.org
 help / color / mirror / Atom feed
From: Song Liu <song@kernel.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Miroslav Benes <mbenes@suse.cz>,
	Joe Lawrence <joe.lawrence@redhat.com>,
	live-patching@vger.kernel.org, jpoimboe@kernel.org,
	jikos@kernel.org, Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH v7] livepatch: Clear relocation targets on a module removal
Date: Fri, 6 Jan 2023 08:51:22 -0800	[thread overview]
Message-ID: <CAPhsuW4xjzcoKorKbOt_PgAF5YtJhJ0ipa=jeBuJGHHgFDQ6jA@mail.gmail.com> (raw)
In-Reply-To: <Y7hLvpHqgY0oJ4GY@alley>

On Fri, Jan 6, 2023 at 8:26 AM Petr Mladek <pmladek@suse.com> wrote:
>
[...]
> > > >
> > > > PS: While we discuss a solution for ppc64, how about we ship the
> > > > fix for other archs first? I think there are only a few small things to
> > > > be addressed.
> > > >
> > >
> > > Yeah, the x86_64 version looks a lot simpler and closer to being done.
> > > Though I believe that Petr would prefer a complete solution, but I'll
> > > let him speak to that.
> >
> > I cannot speak for Petr, but I think it might be easier to split it given
> > the situation. Then we can involve arch maintainers for ppc64le because
> > they might have a preference with respect to a, b, c options above.
> >
> > Petr, what do you think?
>
> I am fine with solving each architecture in a separate patch or
> patchset. It would make it easier, especially, for arch maintainers.

I will send v8 w/o ppc changes after addressing feedback for generic
and x86 code.

Thanks,
Song

  reply	other threads:[~2023-01-06 16:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 17:40 [PATCH v7] livepatch: Clear relocation targets on a module removal Song Liu
2023-01-03 17:00 ` Song Liu
2023-01-03 22:39   ` Joe Lawrence
2023-01-03 23:29     ` Song Liu
2023-01-04 10:26 ` Petr Mladek
2023-01-04 17:34   ` Song Liu
2023-01-04 23:12     ` Joe Lawrence
2023-01-05  5:59       ` Song Liu
2023-01-05 15:05         ` Joe Lawrence
2023-01-05 17:11           ` Song Liu
2023-01-06 13:02           ` Miroslav Benes
2023-01-06 16:26             ` Petr Mladek
2023-01-06 16:51               ` Song Liu [this message]
2023-01-05 11:19     ` Petr Mladek
2023-01-05 16:53       ` Song Liu
2023-01-05 18:09         ` Joe Lawrence
2023-01-05 13:03 ` Petr Mladek

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='CAPhsuW4xjzcoKorKbOt_PgAF5YtJhJ0ipa=jeBuJGHHgFDQ6jA@mail.gmail.com' \
    --to=song@kernel.org \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=pmladek@suse.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.