From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Torsten Duwe <duwe@suse.de>, Torsten Duwe <duwe@lst.de>,
Xiao Yang <yangx.jy@cn.fujitsu.com>,
linux-arm-kernel@lists.infradead.org,
Julien Thierry <jthierry@redhat.com>
Subject: Re: Current status about arm64 livepatch support
Date: Fri, 13 Mar 2020 13:09:10 +0000 [thread overview]
Message-ID: <20200313130910.GF5528@sirena.org.uk> (raw)
In-Reply-To: <20200313122244.GI42546@lakrids.cambridge.arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 528 bytes --]
On Fri, Mar 13, 2020 at 12:22:45PM +0000, Mark Rutland wrote:
> For reliable stack tracing we may need to rework some assemvly and/or
> rework the stack tracing code. That will likely depend on the objtool
> bits.
I'm looking a bit at the stack tracing part - most immediately at
converting arm64 over to the newer arch_stack_walk() interfaces.
There's a couple of other bits of work that have higher priority though,
but they're getting to the point where there's gaps for review so I will
hopefully have some time.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-13 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 7:18 Current status about arm64 livepatch support Xiao Yang
2020-03-13 2:27 ` Xiao Yang
2020-03-13 12:22 ` Mark Rutland
2020-03-13 13:09 ` Mark Brown [this message]
2020-03-13 13:30 ` Julien Thierry
2020-03-13 13:30 ` Julien Thierry
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=20200313130910.GF5528@sirena.org.uk \
--to=broonie@kernel.org \
--cc=duwe@lst.de \
--cc=duwe@suse.de \
--cc=jthierry@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=yangx.jy@cn.fujitsu.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.