Received: by 10.223.176.5 with SMTP id f5csp167493wra; Thu, 1 Feb 2018 17:46:31 -0800 (PST) X-Google-Smtp-Source: AH8x2263nzKZZDrGZK2EbzP8bMuME+M8x/ceW/yvxPFavBbQuo0/Dn3vUc8S3XIybIBgFt+Pa0nW X-Received: by 10.99.105.72 with SMTP id e69mr31062396pgc.239.1517535991323; Thu, 01 Feb 2018 17:46:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517535991; cv=none; d=google.com; s=arc-20160816; b=YvpSQ/liPub7g2SGbiCZjyDQiC2GdBoeJJycylCf+bAxi4YyvNlIspZlst0zxXwYMs ebyoVRnyPhCOXgyVNSN+yGPciWl/1TmjXyU2DFbRi5W0ZULWjcOeUgQ+KBMehLJC6EC7 j/k5d3t53T5vHU7BWTyIHbZ6Lk4rGy3+mmd50QFBtPLrLEmCLxGYoXr6tpajZkaJwTDN P4Nhx26ICOTJvOwuUoBLZwMEn2ieh19GV1yAPMldHrnozl2/oWCcXDuInszHuglj9xaz KIlfalW4UmJj6s4+9g8tPjAjfSfxcfG/BreP6KfpIrlftQegXpEJyTebJi9+6Y1X2Ajk Qorw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:references:in-reply-to:mime-version :dkim-signature:arc-authentication-results; bh=n1eZaO0yPaK3l7EJAK6fHyDSAIMbI9YLVK+ieKjebFo=; b=VsY8D0qOP1i5NNzfcyZEJT0k718im2TZCP0c8ArmzcU47BHoevA9giLk/TS6xY9xFV 5/5IKP5OY5jWhwRme4zAHW3WADRl/++m3+IdtOVPkPq9nt+w+8aXWb1hFmue83OJsGWn JnyPktqtN06s0VjmPJbzU+3sgFQ5lKEuTPPQj7MWYyqOoo8dvgSY0A0+tqpqV//898ds qEbPg76BjlddIv3GUjiEY+2xKR5i1Z2yaQeJh1BZVb6edl3YQFORJg7B9AUKIAXa+nxb ONfDAVPuexMqowfeSw6QxCCbYBWHz9bu25pdEbUpC3LycyVQMZ1rwfU74jQtaRgVrURm wDhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=AeqVaMJb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o6-v6si779226plk.288.2018.02.01.17.46.06; Thu, 01 Feb 2018 17:46:31 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=AeqVaMJb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752463AbeBBBpK (ORCPT + 99 others); Thu, 1 Feb 2018 20:45:10 -0500 Received: from mail-ot0-f196.google.com ([74.125.82.196]:38475 "EHLO mail-ot0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752151AbeBBBo5 (ORCPT ); Thu, 1 Feb 2018 20:44:57 -0500 Received: by mail-ot0-f196.google.com with SMTP id v5so18862101oth.5; Thu, 01 Feb 2018 17:44:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=n1eZaO0yPaK3l7EJAK6fHyDSAIMbI9YLVK+ieKjebFo=; b=AeqVaMJbJi4bvm/9xnb8WQ8caEwQJGKo59CuNeaaXQbFrSYnxjaZhPFVnljO1RDKam GHv+/npYXlPj54Bnr73CHxd1NVKfv2GISBltcQAZAcWV91ERRu7K7HtdegejI7mG+5tO KWlKreJvi2vGzMgsPFGkOpGTGvW3tLcg3dPMGfrAD7eQUZLE08bBEdnuSgENL3Z+TPUw dUzTwCvAVBcX7DmP3OG8tXYScAcQIHduHh4yjRmbn4RCBW+juN27TAaG8Sn5wT9BC8zI LatL+pB2ft5rC3qt6wUXnLevZDIr3PR0kqoYUaJzysyr2xARonGEsIytuSK389XcrbKZ v9yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=n1eZaO0yPaK3l7EJAK6fHyDSAIMbI9YLVK+ieKjebFo=; b=nwkFt8q1pgBFU74EW3SsStxxDEFhBEqILJPYJI7AnHcDfX+C2kEPQOePURQFBa5T8w N3uCPZ2cGs+oetQmbN6B2zlb9OdIyRhwm1Yl4jUdXIDvFgE7QiVG3NtL8+w27s+12kPM C+tb/45VuWxbRQ7eO9vtKhrU8rd1HgBpWAm7zY10Sl/M9kocyzyWyUWMszJ9w64SzvxH Ll4OBAtnwKCoJj5YDXMHabxT6RQhx2ZW/bjWIQklE6MIJqT5iT9dw9lNQ3EP9nb7GsXb J+KUp+6/YJXAs25NX/hWCcpqffe1zEVNQposKTgELgLI59TQFtZuOYy1Suo8Xl/SEMlo WWIw== X-Gm-Message-State: AKwxytfD9qJ0iV7Cp+E+JMvTV2p1ikSsabgo/i2lCuMmLQU7nQoHxNh3 JAZLzFghCvkb7sKvGTxinwg1wxB/qmY3vH/pU3c= X-Received: by 10.157.3.84 with SMTP id 78mr8991238otv.396.1517535896340; Thu, 01 Feb 2018 17:44:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.10.129 with HTTP; Thu, 1 Feb 2018 17:44:55 -0800 (PST) In-Reply-To: <20180201211621.27371-1-rkrcmar@redhat.com> References: <20180201211621.27371-1-rkrcmar@redhat.com> From: Wanpeng Li Date: Fri, 2 Feb 2018 09:44:55 +0800 Message-ID: Subject: Re: [PATCH v2] KVM: x86: fix backward migration with async_PF To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= Cc: linux-kernel@vger.kernel.org, kvm , Paolo Bonzini , Wanpeng Li , "# v3 . 10+" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2018-02-02 5:16 GMT+08:00 Radim Kr=C4=8Dm=C3=A1=C5=99 : > Guests on new hypersiors might set KVM_ASYNC_PF_DELIVERY_AS_PF_VMEXIT > bit when enabling async_PF, but this bit is reserved on old hypervisors, > which results in a failure upon migration. > > To avoid breaking different cases, we are checking for CPUID feature bit > before enabling the feature and nothing else. > > Fixes: 52a5c155cf79 ("KVM: async_pf: Let guest support delivery of async_= pf from guest mode") > Cc: > Signed-off-by: Radim Kr=C4=8Dm=C3=A1=C5=99 Reviewed-by: Wanpeng Li > --- > v2: > * added documentation [Paolo] > * retained compatibility recent kernels [Paolo] > --- > Documentation/virtual/kvm/cpuid.txt | 4 ++++ > Documentation/virtual/kvm/msr.txt | 3 ++- > arch/x86/include/uapi/asm/kvm_para.h | 1 + > arch/x86/kernel/kvm.c | 8 ++++---- > arch/x86/kvm/cpuid.c | 3 ++- > 5 files changed, 13 insertions(+), 6 deletions(-) > > diff --git a/Documentation/virtual/kvm/cpuid.txt b/Documentation/virtual/= kvm/cpuid.txt > index dcab6dc11e3b..87a7506f31c2 100644 > --- a/Documentation/virtual/kvm/cpuid.txt > +++ b/Documentation/virtual/kvm/cpuid.txt > @@ -58,6 +58,10 @@ KVM_FEATURE_PV_TLB_FLUSH || 9 || guest c= hecks this feature bit > || || before enabling paravirtu= alized > || || tlb flush. > ------------------------------------------------------------------------= ------ > +KVM_FEATURE_ASYNC_PF_VMEXIT || 10 || paravirtualized async PF = VM exit > + || || can be enabled by setting= bit 2 > + || || when writing to msr 0x4b5= 64d02 > +------------------------------------------------------------------------= ------ > KVM_FEATURE_CLOCKSOURCE_STABLE_BIT || 24 || host will warn if no gues= t-side > || || per-cpu warps are expecte= d in > || || kvmclock. > diff --git a/Documentation/virtual/kvm/msr.txt b/Documentation/virtual/kv= m/msr.txt > index 1ebecc115dc6..f3f0d57ced8e 100644 > --- a/Documentation/virtual/kvm/msr.txt > +++ b/Documentation/virtual/kvm/msr.txt > @@ -170,7 +170,8 @@ MSR_KVM_ASYNC_PF_EN: 0x4b564d02 > when asynchronous page faults are enabled on the vcpu 0 when > disabled. Bit 1 is 1 if asynchronous page faults can be injected > when vcpu is in cpl =3D=3D 0. Bit 2 is 1 if asynchronous page fau= lts > - are delivered to L1 as #PF vmexits. > + are delivered to L1 as #PF vmexits. Bit 2 can be set only if > + KVM_FEATURE_ASYNC_PF_VMEXIT is present in CPUID. > > First 4 byte of 64 byte memory location will be written to by > the hypervisor at the time of asynchronous page fault (APF) > diff --git a/arch/x86/include/uapi/asm/kvm_para.h b/arch/x86/include/uapi= /asm/kvm_para.h > index 7a2ade4aa235..6cfa9c8cb7d6 100644 > --- a/arch/x86/include/uapi/asm/kvm_para.h > +++ b/arch/x86/include/uapi/asm/kvm_para.h > @@ -26,6 +26,7 @@ > #define KVM_FEATURE_PV_EOI 6 > #define KVM_FEATURE_PV_UNHALT 7 > #define KVM_FEATURE_PV_TLB_FLUSH 9 > +#define KVM_FEATURE_ASYNC_PF_VMEXIT 10 > > /* The last 8 bits are used to indicate how to interpret the flags field > * in pvclock structure. If no bits are set, all flags are ignored. > diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c > index 4e37d1a851a6..971babe964d2 100644 > --- a/arch/x86/kernel/kvm.c > +++ b/arch/x86/kernel/kvm.c > @@ -341,10 +341,10 @@ static void kvm_guest_cpu_init(void) > #endif > pa |=3D KVM_ASYNC_PF_ENABLED; > > - /* Async page fault support for L1 hypervisor is optional= */ > - if (wrmsr_safe(MSR_KVM_ASYNC_PF_EN, > - (pa | KVM_ASYNC_PF_DELIVERY_AS_PF_VMEXIT) & 0xfff= fffff, pa >> 32) < 0) > - wrmsrl(MSR_KVM_ASYNC_PF_EN, pa); > + if (kvm_para_has_feature(KVM_FEATURE_ASYNC_PF_VMEXIT)) > + pa |=3D KVM_ASYNC_PF_DELIVERY_AS_PF_VMEXIT; > + > + wrmsrl(MSR_KVM_ASYNC_PF_EN, pa); > __this_cpu_write(apf_reason.enabled, 1); > printk(KERN_INFO"KVM setup async PF for cpu %d\n", > smp_processor_id()); > diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c > index 20e491b94f44..7fc04a176c57 100644 > --- a/arch/x86/kvm/cpuid.c > +++ b/arch/x86/kvm/cpuid.c > @@ -604,7 +604,8 @@ static inline int __do_cpuid_ent(struct kvm_cpuid_ent= ry2 *entry, u32 function, > (1 << KVM_FEATURE_PV_EOI) | > (1 << KVM_FEATURE_CLOCKSOURCE_STABLE_BIT) | > (1 << KVM_FEATURE_PV_UNHALT) | > - (1 << KVM_FEATURE_PV_TLB_FLUSH); > + (1 << KVM_FEATURE_PV_TLB_FLUSH) | > + (1 << KVM_FEATURE_ASYNC_PF_VMEXIT); > > if (sched_info_on()) > entry->eax |=3D (1 << KVM_FEATURE_STEAL_TIME); > -- > 2.15.1 >