From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC V2] arm64:use set_fixmap_offset to make it more clear
Date: Tue, 28 Jul 2015 09:47:40 +0100 [thread overview]
Message-ID: <20150728084740.GC29209@arm.com> (raw)
In-Reply-To: <21A5B6D3-B813-4DC3-B392-009991B9CA00@gmail.com>
On Tue, Jul 28, 2015 at 07:31:20AM +0100, yalin wang wrote:
>
> > On Jul 24, 2015, at 19:52, yalin wang <yalin.wang2010@gmail.com> wrote:
> >
> > A little change to patch_map() function,
> > use set_fixmap_offset() to make code more clear.
> >
> > Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
> > ---
> > arch/arm64/kernel/insn.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm64/kernel/insn.c b/arch/arm64/kernel/insn.c
> > index dd9671c..f341866 100644
> > --- a/arch/arm64/kernel/insn.c
> > +++ b/arch/arm64/kernel/insn.c
> > @@ -101,9 +101,8 @@ static void __kprobes *patch_map(void *addr, int fixmap)
> > return addr;
> >
> > BUG_ON(!page);
> > - set_fixmap(fixmap, page_to_phys(page));
> > -
> > - return (void *) (__fix_to_virt(fixmap) + (uintaddr & ~PAGE_MASK));
> > + return (void *)set_fixmap_offset(fixmap, page_to_phys(page) +
> > + (uintaddr & ~PAGE_MASK));
> > }
> >
> > static void __kprobes patch_unmap(int fixmap)
> > --
> > 1.9.1
> >
> Marinas,
> this V2 patch can build without warning even CONFIG_DEBUG_SET_MODULE_RONX enabled,
> could you review it.
> Thanks.
I queued this already for 4.3. There's a (benign) sparse warning about the
addr parameter to patch_map being overridden by the local scope of
set_fixmap_offset which could be solved with a healthy portion of
underscores in the core code.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: yalin wang <yalin.wang2010@gmail.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
"zlim.lnx@gmail.com" <zlim.lnx@gmail.com>,
Punit Agrawal <Punit.Agrawal@arm.com>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
"wcohen@redhat.com" <wcohen@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC V2] arm64:use set_fixmap_offset to make it more clear
Date: Tue, 28 Jul 2015 09:47:40 +0100 [thread overview]
Message-ID: <20150728084740.GC29209@arm.com> (raw)
In-Reply-To: <21A5B6D3-B813-4DC3-B392-009991B9CA00@gmail.com>
On Tue, Jul 28, 2015 at 07:31:20AM +0100, yalin wang wrote:
>
> > On Jul 24, 2015, at 19:52, yalin wang <yalin.wang2010@gmail.com> wrote:
> >
> > A little change to patch_map() function,
> > use set_fixmap_offset() to make code more clear.
> >
> > Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
> > ---
> > arch/arm64/kernel/insn.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm64/kernel/insn.c b/arch/arm64/kernel/insn.c
> > index dd9671c..f341866 100644
> > --- a/arch/arm64/kernel/insn.c
> > +++ b/arch/arm64/kernel/insn.c
> > @@ -101,9 +101,8 @@ static void __kprobes *patch_map(void *addr, int fixmap)
> > return addr;
> >
> > BUG_ON(!page);
> > - set_fixmap(fixmap, page_to_phys(page));
> > -
> > - return (void *) (__fix_to_virt(fixmap) + (uintaddr & ~PAGE_MASK));
> > + return (void *)set_fixmap_offset(fixmap, page_to_phys(page) +
> > + (uintaddr & ~PAGE_MASK));
> > }
> >
> > static void __kprobes patch_unmap(int fixmap)
> > --
> > 1.9.1
> >
> Marinas,
> this V2 patch can build without warning even CONFIG_DEBUG_SET_MODULE_RONX enabled,
> could you review it.
> Thanks.
I queued this already for 4.3. There's a (benign) sparse warning about the
addr parameter to patch_map being overridden by the local scope of
set_fixmap_offset which could be solved with a healthy portion of
underscores in the core code.
Will
next prev parent reply other threads:[~2015-07-28 8:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 11:45 [RFC] arm64:use set_fixmap_offset to make it more clear yalin wang
2015-07-23 11:45 ` yalin wang
2015-07-23 13:03 ` Catalin Marinas
2015-07-23 13:03 ` Catalin Marinas
2015-07-24 3:56 ` yalin wang
2015-07-24 3:56 ` yalin wang
2015-07-24 9:56 ` Mark Rutland
2015-07-24 9:56 ` Mark Rutland
2015-07-24 10:07 ` Mark Rutland
2015-07-24 10:07 ` Mark Rutland
2015-07-24 11:53 ` yalin wang
2015-07-24 11:53 ` yalin wang
2015-07-23 15:29 ` Laura Abbott
2015-07-23 15:29 ` Laura Abbott
2015-07-24 11:52 ` [RFC V2] " yalin wang
2015-07-28 6:31 ` yalin wang
2015-07-28 6:31 ` yalin wang
2015-07-28 8:47 ` Will Deacon [this message]
2015-07-28 8:47 ` Will Deacon
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=20150728084740.GC29209@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.