From: Daniel Borkmann <daniel@iogearbox•net>
To: Sandipan Das <sandipan@linux•vnet.ibm.com>, mpe@ellerman•id.au
Cc: naveen.n.rao@linux•vnet.ibm.com, ast@fb•com,
netdev@vger•kernel.org, linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH 1/1] bpf: take advantage of stack_depth tracking in powerpc JIT
Date: Fri, 01 Sep 2017 21:15:33 +0200 [thread overview]
Message-ID: <59A9B1D5.7030307@iogearbox.net> (raw)
In-Reply-To: <20170901185301.17978-1-sandipan@linux.vnet.ibm.com>
On 09/01/2017 08:53 PM, Sandipan Das wrote:
> Take advantage of stack_depth tracking, originally introduced for
> x64, in powerpc JIT as well. Round up allocated stack by 16 bytes
> to make sure it stays aligned for functions called from JITed bpf
> program.
>
> Signed-off-by: Sandipan Das <sandipan@linux•vnet.ibm.com>
Awesome, thanks for following up! :)
next prev parent reply other threads:[~2017-09-01 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 18:53 [PATCH 1/1] bpf: take advantage of stack_depth tracking in powerpc JIT Sandipan Das
2017-09-01 19:03 ` Naveen N. Rao
2017-09-01 19:15 ` Daniel Borkmann [this message]
2017-11-07 23:30 ` [1/1] " Michael Ellerman
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=59A9B1D5.7030307@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=ast@fb$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=naveen.n.rao@linux$(echo .)vnet.ibm.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sandipan@linux$(echo .)vnet.ibm.com \
/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