[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y8aTEfpw0Vm6g0hC@hirez.programming.kicks-ass.net>
Date: Tue, 17 Jan 2023 13:22:41 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: "Srivatsa S. Bhat" <srivatsa@...il.mit.edu>
Cc: Juergen Gross <jgross@...e.com>, linux-kernel@...r.kernel.org,
x86@...nel.org, virtualization@...ts.linux-foundation.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
Alexey Makhalov <amakhalov@...are.com>,
VMware PV-Drivers Reviewers <pv-drivers@...are.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
xen-devel@...ts.xenproject.org
Subject: Re: [PATCH] x86/paravirt: merge activate_mm and dup_mmap callbacks
On Sun, Jan 15, 2023 at 08:27:50PM -0800, Srivatsa S. Bhat wrote:
> I see that's not an issue right now since there is no other actual
> user for these callbacks. But are we sure that merging the callbacks
> just because the current user (Xen PV) has the same implementation for
> both is a good idea?
IIRC the pv_ops are part of the PARAVIRT_ME_HARDER (also spelled as
_XXL) suite of ops and they are only to be used by Xen PV, no new users
of these must happen.
The moment we can drop Xen PV (hopes and dreams etc..) all these things
go in the bin right along with it.
Powered by blists - more mailing lists