[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220503173046.fv2aluc34bxhzgq3@treble>
Date: Tue, 3 May 2022 10:30:46 -0700
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Seth Forshee <sforshee@...italocean.com>
Cc: Sean Christopherson <seanjc@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Andy Lutomirski <luto@...nel.org>,
Jiri Kosina <jikos@...nel.org>,
Miroslav Benes <mbenes@...e.cz>,
Petr Mladek <pmladek@...e.com>,
Paolo Bonzini <pbonzini@...hat.com>,
linux-kernel@...r.kernel.org, live-patching@...r.kernel.org,
kvm@...r.kernel.org
Subject: Re: [PATCH] entry/kvm: Make vCPU tasks exit to userspace when a
livepatch is pending
On Tue, May 03, 2022 at 11:18:02AM -0500, Seth Forshee wrote:
> > Can the changelog and comment use terminology other than migration? Maybe "transition"?
> > That seems to be prevelant through the livepatch code and docs. There are already
> > too many meanings for "migration" in KVM, e.g. live migration, page migration, task/vCPU
> > migration, etc...
>
> "Transition" is used a lot, but afaict it refers to the overall state of
> the livepatch. "Migrate" is used a lot less, but it always seems to
> refer to patching a single task, which is why I used that term. But I
> can see the opportunity for confusion, so I'll reword it.
The livepatch code does seem to be guilty of using both terms
interchangeably. I agree "transition" is preferable.
--
Josh
Powered by blists - more mailing lists