[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190115154327.GH26443@infradead.org>
Date: Tue, 15 Jan 2019 07:43:27 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Björn Töpel <bjorn.topel@...il.com>
Cc: linux-riscv@...ts.infradead.org, palmer@...ive.com,
davidlee@...ive.com, daniel@...earbox.net, netdev@...r.kernel.org
Subject: Re: [RFC PATCH 2/3] riscv: add build infra for JIT compiler
> core-y += arch/riscv/kernel/ arch/riscv/mm/
>
> +ifeq ($(CONFIG_ARCH_RV64I),y)
> +core-y += arch/riscv/net/
> +endif
I think this should be core-$(CONFIG_ARCH_RV64I) to get the same result.
Or even better just core-y given that the Kconfig dependencies should
ensure you can't ever enable CONFIG_BPF_JIT for 32-bit builds.
> new file mode 100644
> index 000000000000..b0b6ac13edf5
> --- /dev/null
> +++ b/arch/riscv/net/Makefile
> @@ -0,0 +1,5 @@
> +#
> +# RISCV networking code
> +#
I don't think this comment adds any value. In fact it is highly
confusing given that we use bpf for a lot more than networking these
days.
> diff --git a/arch/riscv/net/bpf_jit_comp.c b/arch/riscv/net/bpf_jit_comp.c
> new file mode 100644
> index 000000000000..7e359d3249ee
> --- /dev/null
> +++ b/arch/riscv/net/bpf_jit_comp.c
> @@ -0,0 +1,4 @@
> +struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *prog)
> +{
> + return prog;
> +}
Please don't just add stubs files. This patch should probably be merged
into the one adding the actual implementation.
Powered by blists - more mailing lists