[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d6854071-59f2-45a5-a58d-00023a326346@redhat.com>
Date: Mon, 20 Jan 2025 20:47:30 +0100
From: David Hildenbrand <david@...hat.com>
To: Rik van Riel <riel@...riel.com>, x86@...nel.org
Cc: linux-kernel@...r.kernel.org, bp@...en8.de, peterz@...radead.org,
dave.hansen@...ux.intel.com, zhengqi.arch@...edance.com,
nadav.amit@...il.com, thomas.lendacky@....com, kernel-team@...a.com,
linux-mm@...ck.org, akpm@...ux-foundation.org, jannh@...gle.com,
mhklinux@...look.com, andrew.cooper3@...rix.com
Subject: Re: [PATCH v6 02/12] x86/mm: remove pv_ops.mmu.tlb_remove_table call
On 20.01.25 03:40, Rik van Riel wrote:
> Every pv_ops.mmu.tlb_remove_table call ends up calling tlb_remove_table.
>
Indeed, but the !CONFIG_PARAVIRT variant paravirt_tlb_remove_table()
however calls tlb_remove_page().
tlb_remove_page() ends up in
__tlb_remove_page_size()->__tlb_remove_folio_pages_size(), not in
tlb_remove_table()
... but maybe I am looking at the wrong tree, so I wonder if this is
okay an simply not spelled out here explicitly?
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists