From: Jason Baron <jbaron@redhat.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Rabin Vincent <rabin@rab.in>,
linux-mips@linux-mips.org, ralf@linux-mips.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] jump label: Add MIPS support.
Date: Mon, 4 Oct 2010 13:50:39 -0400 [thread overview]
Message-ID: <20101004175039.GC2900@redhat.com> (raw)
In-Reply-To: <4CAA122B.40502@caviumnetworks.com>
On Mon, Oct 04, 2010 at 10:43:07AM -0700, David Daney wrote:
> On 10/03/2010 11:15 AM, Rabin Vincent wrote:
>> On Tue, Sep 28, 2010 at 11:40 PM, David Daney<ddaney@caviumnetworks.com> wrote:
>>> +void arch_jump_label_text_poke_early(jump_label_t addr)
>>> +{
>>> + union mips_instruction *insn_p =
>>> + (union mips_instruction *)(unsigned long)addr;
>>> +
>>> + insn_p->word = 0; /* nop */
>>> + flush_icache_range((unsigned long)insn_p,
>>> + (unsigned long)insn_p + sizeof(*insn_p));
>>> +}
>>
>> Can't this function be a no-op on MIPS? This seems to be
>> used on x86 to patch in the optimal nop instruction, but
>> on MIPS the optimal/only nop instruction should already
>> be in place at build time. Same thing for the SPARC
>> implementation.
>>
>
> Yes, I think you are correct.
>
> On MIPS the NOP is already optimal. I will respin the MIPS patch to
> make arch_jump_label_text_poke_early() be empty.
>
> davem wasn't CCed on the original message, so I added him. I would
> defer to him on the SPARC version.
>
>
that's right, arch_jump_label_text_poke_early() can probably be a no-op
for most arches.
We can also look at adding an empty definition into the generic
header. So that arches don't have to provide an empty definition.
thanks,
-Jason
next prev parent reply other threads:[~2010-10-04 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 18:10 [PATCH] jump label: Add MIPS support David Daney
2010-10-01 21:49 ` Steven Rostedt
2010-10-02 1:54 ` Ralf Baechle
2010-10-03 18:15 ` Rabin Vincent
2010-10-04 17:43 ` David Daney
2010-10-04 17:50 ` Jason Baron [this message]
2010-10-04 19:06 ` David Daney
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=20101004175039.GC2900@redhat.com \
--to=jbaron@redhat.com \
--cc=davem@davemloft.net \
--cc=ddaney@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=rabin@rab.in \
--cc=ralf@linux-mips.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox