[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220307033246.23051-1-yf.wang@mediatek.com>
Date: Mon, 7 Mar 2022 11:32:46 +0800
From: <yf.wang@...iatek.com>
To: <robin.murphy@....com>
CC: <Libo.Kang@...iatek.com>, <Ning.Li@...iatek.com>,
<iommu@...ts.linux-foundation.org>, <joro@...tes.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
<linux-mediatek@...ts.infradead.org>, <matthias.bgg@...il.com>,
<stable@...r.kernel.org>, <will@...nel.org>,
<wsd_upstream@...iatek.com>, <yf.wang@...iatek.com>
Subject: RE: [PATCH] iommu/iova: Free all CPU rcache for retry when iova alloc failure
On Fri, 2022-03-04 at 14:03 +0000, Robin Murphy wrote:
>
> OK, so either there's a mystery bug where IOVAs somehow get freed on
> offline CPUs, or the hotplug notifier isn't working correctly, or
> you've
> contrived a situation where alloc_iova_fast() is actually racing
> against
> iova_cpuhp_dead(). In the latter case, the solution is "don't do
> that".
>
> This change should not be necessary.
>
> Thanks,
> Robin.
Hi Robin,
1.As long as iova domain is not destroyed, the cached iovas will always
exist, the only chance to free the cache is the retry flushing
mechanism when alloc fail, but not free cached iova of not online CPU.
2.Iova rcache mechanism is by cpu, but there is no free rcache
mechanism when the CPU state switch.
3.iova.c does not know about CPU state switching, eg.online <--> offline.
Based on the above basic information, this is not a user bug, it is
more like a defect of the iova rcache mechanism.
Thanks,
Yunfei.
Powered by blists - more mailing lists