From: Ruslan Bilovol <rbilovol@cisco.com>
To: Torsten Duwe <duwe@suse.de>, Ruslan Bilovol <ruslan.bilovol@gmail.com>
Cc: Li Bin <huawei.libin@huawei.com>, Jessica Yu <jeyu@redhat.com>,
Miroslav Benes <mbenes@suse.cz>,
zhouchengming <zhouchengming1@huawei.com>,
live-patching@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jpoimboe@redhat.com, jikos@kernel.org, pmladek@suse.com,
Zefan Li <lizefan@huawei.com>, Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH] reduce the time of finding symbols for module
Date: Tue, 17 Oct 2017 15:44:21 +0300 [thread overview]
Message-ID: <da67dde1-19ba-f1d0-db2b-6e874cf591b0@cisco.com> (raw)
In-Reply-To: <20171013131841.en3yuwtl3wedei5t@suse.de>
Hi,
On 10/13/2017 04:18 PM, Torsten Duwe wrote:
> On Fri, Oct 13, 2017 at 03:54:46PM +0300, Ruslan Bilovol wrote:
>> Hi Li,
>>
>> On Wed, Mar 29, 2017 at 4:50 AM, Li Bin <huawei.libin@huawei.com> wrote:
>>> Hi,
>> [snip]
>>>
>>> Yeah, from 2014, we started to work on livepatch support on aarch64, and
>>> in May 2015, we pushed the solution to the livepatch community[1] and gcc
>>> community (mfentry feature on aarch64)[2]. And then, there were an another
>>> gcc solution from linaro [3], which proposes to implement a new option
>>> -fprolog-pad=N that generate a pad of N nops at the beginning of each
>>> function, and AFAIK, Torsten Duwe from SUSE is still discussing this method
>>> with gcc community.
>>>
>>> At this stage, we are validating the livepatch support on aarch64 based on
>>> aarch64 mfentry feature. When the community has a clear plan, we are happy
>>> to make adaptation and contribute our related work to the community, including
>>> the kpatch-build support :-)
>>>
>>> [1] livepatch: add support on arm64
>>> https://lkml.org/lkml/2015/5/28/54
>>> [2] [AArch64] support -mfentry feature for arm64
>>> https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00756.html
>>> [3] Kernel livepatching support in GCC
>>> https://gcc.gnu.org/ml/gcc/2015-05/msg00267.html
>>> [4] arm64: ftrace with regs for livepatch support
>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/401352.html
>>>
>>
>> Since there is already -fpatchable-function-entry option committed by Torsten
>> to gcc on 25 Jul [1], have you restarted your activities with AArch64 livepatch
>> support?
>> If yes, I'm interested in testing of that feature/patches on our hardware
>
> I also have the coresponding kernel patch(es) here. IIRC I already sent
> tham to LKML. I'll re-send them once there are more gcc's with -fpatchable-function-entry
> support out there.
Do you mean "[PATCH v3 0/2] arm64 live patching" [1] series?
I'm going to play with them and see how it works.
Another question: have you tested livepatching on Big Endian systems?
[1] https://lwn.net/Articles/697050
Thanks,
Ruslan
next prev parent reply other threads:[~2017-10-17 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 2:02 [PATCH] reduce the time of finding symbols for module Zhou Chengming
2017-03-28 9:00 ` Miroslav Benes
2017-03-28 10:58 ` zhouchengming
2017-03-28 11:16 ` Miroslav Benes
2017-03-28 12:50 ` zhouchengming
2017-03-29 0:03 ` Jessica Yu
2017-03-29 1:50 ` Li Bin
2017-03-29 19:09 ` Jessica Yu
2017-10-13 12:54 ` Ruslan Bilovol
2017-10-13 13:18 ` Torsten Duwe
2017-10-17 12:44 ` Ruslan Bilovol [this message]
2017-10-17 13:06 ` Torsten Duwe
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=da67dde1-19ba-f1d0-db2b-6e874cf591b0@cisco.com \
--to=rbilovol@cisco.com \
--cc=duwe@suse.de \
--cc=guohanjun@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=ruslan.bilovol@gmail.com \
--cc=zhouchengming1@huawei.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.