From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH/RFC 01/09] iommu/ipmmu-vmsa: Disable IPMMU when address expansion is not needed
Date: Wed, 20 Feb 2019 17:09:54 +0100 [thread overview]
Message-ID: <CAMuHMdU0ncCg7MXS7XTmiDX42bXE0Wj6RLvd0GddNA3R+Bawaw@mail.gmail.com> (raw)
In-Reply-To: <155067455863.15971.400236990712480655.sendpatchset@octo>
Hi Magnus,
On Wed, Feb 20, 2019 at 3:55 PM Magnus Damm <magnus.damm@gmail.com> wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> Add a memory bank location check to the whitelist handling.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
Thanks for your patch!
> --- 0001/drivers/iommu/ipmmu-vmsa.c
> +++ work/drivers/iommu/ipmmu-vmsa.c 2019-02-20 22:59:28.589893396 +0900
> @@ -797,6 +798,12 @@ static bool ipmmu_slave_whitelist(struct
> if (!soc_device_match(soc_rcar_gen3_whitelist))
> return false;
>
> + /* In case all system memory fits within 32 bits of physical space
> + * then assume the IPMMU will not be needed for address expansion.
> + */
> + if (memblock_end_of_DRAM() <= SZ_4G)
Can this give a compiler warning on arm32 when CONFIG_ARM_LPAE=n?
> + return false;
> +
> /* Check whether this slave device can work with the IPMMU */
> for (i = 0; i < ARRAY_SIZE(rcar_gen3_slave_whitelist); i++) {
> if (!strcmp(dev_name(dev), rcar_gen3_slave_whitelist[i]))
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2019-02-20 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 14:55 [PATCH/RFC 00/09] IPMMU address translation enablement prototype Magnus Damm
2019-02-20 14:55 ` [PATCH/RFC 01/09] iommu/ipmmu-vmsa: Disable IPMMU when address expansion is not needed Magnus Damm
2019-02-20 16:09 ` Geert Uytterhoeven [this message]
2019-03-19 13:45 ` Magnus Damm
2019-03-19 14:07 ` Geert Uytterhoeven
2019-02-20 14:56 ` [PATCH/RFC 02/09] iommu/ipmmu-vmsa: Display system memory informationn during boot Magnus Damm
2019-02-20 14:56 ` [PATCH/RFC 03/09] iommu/ipmmu-vmsa: Introduce keepipmmu boot parameter Magnus Damm
2019-02-20 19:54 ` Geert Uytterhoeven
2019-02-20 14:56 ` [PATCH/RFC 04/09] arm64: dts: renesas: ulcb: " Magnus Damm
2019-02-20 14:56 ` [PATCH/RFC 05/09] arm64: dts: renesas: salvator: " Magnus Damm
2019-02-20 14:56 ` [PATCH/RFC 06/09] arm64: dts: renesas: draak: " Magnus Damm
2019-02-20 14:56 ` [PATCH/RFC 07/09] arm64: dts: renesas: ebisu: " Magnus Damm
2019-02-20 14:57 ` [PATCH/RFC 08/09] arm64: dts: renesas: eagle: " Magnus Damm
2019-02-20 14:57 ` [PATCH/RFC 09/09] arm64: dts: renesas: cat874: " Magnus Damm
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=CAMuHMdU0ncCg7MXS7XTmiDX42bXE0Wj6RLvd0GddNA3R+Bawaw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).