[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190724085427.GA10736@apalos>
Date: Wed, 24 Jul 2019 11:54:27 +0300
From: Ilias Apalodimas <ilias.apalodimas@...aro.org>
To: David Miller <davem@...emloft.net>
Cc: jonathanh@...dia.com, robin.murphy@....com,
Jose.Abreu@...opsys.com, lists@...h.nu, Joao.Pinto@...opsys.com,
alexandre.torgue@...com, maxime.ripard@...tlin.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com, wens@...e.org,
mcoquelin.stm32@...il.com, linux-tegra@...r.kernel.org,
peppe.cavallaro@...com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next 3/3] net: stmmac: Introducing support for Page
Pool
Hi David,
> From: Jon Hunter <jonathanh@...dia.com>
> Date: Tue, 23 Jul 2019 13:09:00 +0100
>
> > Setting "iommu.passthrough=1" works for me. However, I am not sure where
> > to go from here, so any ideas you have would be great.
>
> Then definitely we are accessing outside of a valid IOMMU mapping due
> to the page pool support changes.
Yes. On the netsec driver i did test with and without SMMU to make sure i am not
breaking anything.
Since we map the whole page on the API i think some offset on the driver causes
that. In any case i'll have another look on page_pool to make sure we are not
missing anything.
>
> Such a problem should be spotted with swiommu enabled with debugging.
Thanks
/Ilias
Powered by blists - more mailing lists