-
由 Benjamin Herrenschmidt 提交于
So we tried to speed things up a bit using flush_hash_pages() directly but that falls over on 603 of course meaning we fail to flush the TLB properly and we may even end up having it corrupt memory randomly by accessing a hash table that doesn't exist. This removes the "optimization" by always going through flush_tlb_page() for now at least. Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
75c1d539