From: Matt Evans <matt@ozlabs.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: netdev@vger.kernel.org, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC PATCH 1/1] BPF JIT for PPC64
Date: Mon, 11 Jul 2011 16:27:27 +1000 [thread overview]
Message-ID: <4E1A97CF.80509@ozlabs.org> (raw)
In-Reply-To: <m2boxmxt45.fsf@igel.home>
On 25/06/11 17:33, Andreas Schwab wrote:
> Matt Evans <matt@ozlabs.org> writes:
>
>> + stdu r1, -128(r1); \
>
>> + addi r5, r1, 128+BPF_PPC_STACK_BASIC+(2*8); \
>
>> + addi r1, r1, 128; \
>
>> + PPC_STD(r_M + i, 1, -128 + (8*i));
>
>> + PPC_LD(r_M + i, 1, -128 + (8*i));
>
> s/128/BPF_PPC_STACK_SAVE/?
Actually, that's a different 128, but that nicely illustrates that I should've
#defined something more recognisable :-) The second set, with -128, is actually
in the save area for non-volatile regs, whereas the first is just a stackframe
size.
Cheers,
Matt
prev parent reply other threads:[~2011-07-11 6:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 6:02 [RFC PATCH 1/1] BPF JIT for PPC64 Matt Evans
2011-06-25 1:58 ` Ben Hutchings
2011-07-11 6:21 ` Matt Evans
2011-06-25 7:33 ` Andreas Schwab
2011-06-25 7:49 ` Eric Dumazet
2011-07-11 7:04 ` Matt Evans
2011-07-11 6:27 ` Matt Evans [this message]
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=4E1A97CF.80509@ozlabs.org \
--to=matt@ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=schwab@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).