public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec•com>
To: Jonas Gorski <jogo@openwrt•org>
Cc: MIPS Mailing List <linux-mips@linux-mips•org>,
	"David S. Miller" <davem@davemloft•net>, <netdev@vger•kernel.org>
Subject: Re: [PATCH v2 13/14] MIPS: net: Add BPF JIT
Date: Thu, 10 Apr 2014 08:46:26 +0100	[thread overview]
Message-ID: <53464C52.2060004@imgtec.com> (raw)
In-Reply-To: <CAOiHx=kh3+Xzvyx7PsEfNCiEf6cRP3ucQKDfY3brZ6FR2KwW4Q@mail.gmail.com>

On 04/09/2014 11:28 PM, Jonas Gorski wrote:
>
>> +#ifdef CONFIG_CPU_LITTLE_ENDIAN
>> +                       /* This needs little endian fixup */
>> +                       if (config_enabled(CPU_MIPSR1)) {
>
> Hm, looking at arch/mips/Kconfig, this will falsely identify CPU_BMIPS
> as R2 as it does not select CPU_MIPSR1.
>
> How about "if (cpu_has_mips_r1)"? There are some targets that have
> both R1 and R2 cores (e.g. bcm47xx), and even if we built the kernel
> for R1, it does not prevent us from emitting R2 instructions because
> we do this at runtime when we can check for it.

Sounds about right. Let me have a look


-- 
markos

  reply	other threads:[~2014-04-10  7:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1396957635-27071-14-git-send-email-markos.chandras@imgtec.com>
2014-04-09 16:00 ` [PATCH v2 13/14] MIPS: net: Add BPF JIT Markos Chandras
2014-04-09 22:28   ` Jonas Gorski
2014-04-10  7:46     ` Markos Chandras [this message]
2014-04-10  3:40   ` Alexei Starovoitov
2014-04-10  8:06     ` Markos Chandras
2014-04-24 14:50 ` [PATCH v3 " Markos Chandras
2014-04-24 16:31   ` Paul Burton
2014-04-25 12:06     ` Markos Chandras
2014-04-29 15:58   ` [PATCH v4 " Markos Chandras

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=53464C52.2060004@imgtec.com \
    --to=markos.chandras@imgtec$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=jogo@openwrt$(echo .)org \
    --cc=linux-mips@linux-mips$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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