From: Josh Poimboeuf <jpoimboe@redhat.com>
To: "Madhavan T. Venkataraman" <madvenka@linux.microsoft.com>
Cc: linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>,
Julien Thierry <jthierry@redhat.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Live patching on ARM64
Date: Thu, 14 Jan 2021 17:58:32 -0600 [thread overview]
Message-ID: <20210114235832.lqdrgb3yeeg2n4fg@treble> (raw)
In-Reply-To: <f3fe6a60-9ac2-591d-1b83-9113c50dc492@linux.microsoft.com>
Hi Madhavan,
I'd also recommend subscribing to the live-patching mailing list (Cc'ed).
On Thu, Jan 14, 2021 at 04:07:55PM -0600, Madhavan T. Venkataraman wrote:
> Hi all,
>
> My name is Madhavan Venkataraman.
>
> Microsoft is very interested in Live Patching support for ARM64.
> On behalf of Microsoft, I would like to contribute.
>
> I would like to get in touch with the people who are currently working
> in this area, find out what exactly they are working on and see if they
> could use an extra pair of eyes/hands with what they are working on.
>
> It looks like the most recent work in this area has been from the
> following folks:
>
> Mark Brown and Mark Rutland:
> Kernel changes to providing reliable stack traces.
>
> Julien Thierry:
> Providing ARM64 support in objtool.
>
> Torsten Duwe:
> Ftrace with regs.
>
> I apologize if I have missed anyone else who is working on Live Patching
> for ARM64. Do let me know.
>
> Is there any work I can help with? Any areas that need investigation, any code
> that needs to be written, any work that needs to be reviewed, any testing that
> needs to done? You folks are probably super busy and would not mind an extra
> hand.
>
> I have subscribed to linux-arm-kernel. But if any discussions should happen on
> another mailing list, could you please CC me? Appreciate it.
>
> Thanks! I look forward to working with you.
>
> Madhavan
>
> P.S.:
>
> Julien,
>
> Could you send me a link to your latest RFC submission? Thanks!
--
Josh
next parent reply other threads:[~2021-01-15 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f3fe6a60-9ac2-591d-1b83-9113c50dc492@linux.microsoft.com>
2021-01-14 23:58 ` Josh Poimboeuf [this message]
2021-01-15 12:33 ` Live patching on ARM64 Mark Rutland
2021-01-15 13:44 ` Mark Brown
2021-01-17 17:25 ` Madhavan T. Venkataraman
2021-01-19 7:57 ` Julien Thierry
2021-01-19 15:19 ` Madhavan T. Venkataraman
2021-01-20 18:11 ` Julien Thierry
2021-01-26 18:03 ` Madhavan T. Venkataraman
2021-03-18 22:38 ` Singh, Balbir
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=20210114235832.lqdrgb3yeeg2n4fg@treble \
--to=jpoimboe@redhat.com \
--cc=broonie@kernel.org \
--cc=jthierry@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).