Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp907490ima; Fri, 1 Feb 2019 12:55:49 -0800 (PST) X-Google-Smtp-Source: ALg8bN7FadX4M8S6Q9qtNEY/7si62m5w6nOM6NU0p1tWjf4ryPDnfp3UI2pqSed9q8n968Lq3nhm X-Received: by 2002:a17:902:5601:: with SMTP id h1mr42131512pli.160.1549054549733; Fri, 01 Feb 2019 12:55:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549054549; cv=none; d=google.com; s=arc-20160816; b=U5vtKOEOO42f5vNiNBlP1wol4YiORRkkw4OGhQxZ+mjPCuWb7s1FRm1tU6/wjVa6Tg 1lTMZ4Q1Z9qX3wI5iZbav0+Bs32To+s+PvB1bfQNNnfyYMA1caTUdB+zE4SLpry+SAWJ mzxS+Wpy7Pr1qQTLf001zozvRUtGWLyXWfgVDJ5uFoCDhmRV/5UYayaWXidOAbFkzoI2 igyVqhrAau64e+wNgqAEOkI45qjIf4OBpembuBNnQRxUiZ9t6r8/dGnbf9OlzrM7EerW lmScuvrJwG9qV6beWNuwi2DErLwSaPwEvr3HlOX/rOapicK4DfTAnFllbNlY6PbAe3be 8QUQ== 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:in-reply-to:references:mime-version :dkim-signature; bh=NtpgDq2Gw8aN0PaOjgpjgTZu/UHnpQMFSYsy8Ia28Bw=; b=wofZngawXmkCFzr6TRsfASVeTbfpSYk2gdyENqTiAbE0WfL1n5aGcy4oidAfmRvi59 m8+ji6eL/fDLv84dBCT/2q8+9vtKfECx2HZhwInKZ8AentomyfUxSjvsg4K+9hT2RvEc DpdD1sgvHsly05Tywu8zJilfGTUoCt3TGL8aHeA7j1NiQqPkBROwsFj3SSAs+NS2rXmD gcfRfk96CjKs/+ATg5fUGeIdJtX/5Nx1fbCSsRqrpWHlJIjU28kC9t+OwOBp11Hj0sEo 2sQmLeUsz53lpElkGQZ2x+gcaeC3/93Sac74TdF5r8MJgbeeGQF4pKpqzbfHdz6F3nMq cXhg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=s3ZBIVAA; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 11si7827327pgs.126.2019.02.01.12.55.34; Fri, 01 Feb 2019 12:55:49 -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=@google.com header.s=20161025 header.b=s3ZBIVAA; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730975AbfBAUVb (ORCPT + 99 others); Fri, 1 Feb 2019 15:21:31 -0500 Received: from mail-it1-f195.google.com ([209.85.166.195]:52455 "EHLO mail-it1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728326AbfBAUVb (ORCPT ); Fri, 1 Feb 2019 15:21:31 -0500 Received: by mail-it1-f195.google.com with SMTP id d11so11238491itf.2 for ; Fri, 01 Feb 2019 12:21:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=NtpgDq2Gw8aN0PaOjgpjgTZu/UHnpQMFSYsy8Ia28Bw=; b=s3ZBIVAAHyq3QJqxqSHc97aPvm1Owqm3SASatBZ7G7gR3r/93luNbWfRG80lfHLzii T+Ybs7Ua5lQTD/O91xLUaDbpaqH4bqHX57cT1aTDdvV1RzTsuIv9WGGLNORTCD7uLIWe 0i9E2xJXmvSL7aFtmbfid5RhEOcTH/s+WVwuMqSHn2Dk4XmYHnwrSN/7YBLyF1RY4K2m OUgQTDWcFS9JrqMiwDu6Bnypn0m0JdilMvJCziBHLLzyB3VjIChyKtGU1dWg9bsce8Fd 68uaYsDrSp6m8EezD93J8r7EJAdrWy3jhR/Qp+NEYKbnwV+YhfAQK2hEyrdxvdEkw4BJ BVFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=NtpgDq2Gw8aN0PaOjgpjgTZu/UHnpQMFSYsy8Ia28Bw=; b=dg/V1xX4RHgMn8COCWdzFH1x2LujDX3SRTqdzaSMEpto7q8HeYs9BrfIVbTb8hHgFY MEUUJUHIeFiiZ3ZWh3v5Km2rIo/pK+5qHwEUARhKX+4r09oHJsADMK6LqUoy/Ofwv8gr hPbYu6Ux5BPBaQhLH1BJ/pU7Sgmr6NzOHQwy4BbzWK4yROBXWpqU0B26vYehxEhp559s DTXv6Myhmmphuqvor+16PUKjaq66sJJ//ujjRwsuWNY1tixlhMA7iezMuZmtiUTndhRC f7ht480EMvsBjk/0p58z2HRKjVZa7PsmOPpkoE/nwpsQJx59L91+FiOUDrBU2c0Ez1y0 pwcg== X-Gm-Message-State: AHQUAua625JzmJcWu2/UgCM2Fs/SXsSaAzI03wetnVtQWhZK78gvVpRK NtfGoLWn8PBZlgFaIWN2mMtsmbaoTtkizaX5XvSplg== X-Received: by 2002:a24:4a95:: with SMTP id k143mr2490160itb.77.1549052490154; Fri, 01 Feb 2019 12:21:30 -0800 (PST) MIME-Version: 1.0 References: <20171205010616.5958-1-brijesh.singh@amd.com> <20171205010616.5958-9-brijesh.singh@amd.com> In-Reply-To: <20171205010616.5958-9-brijesh.singh@amd.com> From: Jim Mattson Date: Fri, 1 Feb 2019 12:21:18 -0800 Message-ID: Subject: Re: [Part2 PATCH v9 38/38] KVM: X86: Restart the guest when insn_len is zero and SEV is enabled To: Brijesh Singh Cc: kvm list , LKML , "the arch/x86 maintainers" , Borislav Petkov , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Joerg Roedel , Borislav Petkov , Tom Lendacky 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 On Mon, Dec 4, 2017 at 5:07 PM Brijesh Singh wrote: > > On AMD platforms, under certain conditions insn_len may be zero on #NPF. > This can happen if a guest gets a page-fault on data access but the HW > table walker is not able to read the instruction page (e.g instruction > page is not present in memory). > > Typically, when insn_len is zero, x86_emulate_instruction() walks the > guest page table and fetches the instruction bytes from guest memory. > When SEV is enabled, the guest memory is encrypted with guest-specific > key hence hypervisor will not able to fetch the instruction bytes. > In those cases we simply restart the guest. > > I have encountered this issue when running kernbench inside the guest. > > Cc: Thomas Gleixner > Cc: Ingo Molnar > Cc: "H. Peter Anvin" > Cc: Paolo Bonzini > Cc: "Radim Kr=C4=8Dm=C3=A1=C5=99" > Cc: Joerg Roedel > Cc: Borislav Petkov > Cc: Tom Lendacky > Cc: x86@kernel.org > Cc: kvm@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Signed-off-by: Brijesh Singh > --- > arch/x86/kvm/mmu.c | 10 ++++++++++ > arch/x86/kvm/svm.c | 6 ++++-- > 2 files changed, 14 insertions(+), 2 deletions(-) > > diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c > index e5e66e5c6640..d5e5dbd0e5ad 100644 > --- a/arch/x86/kvm/mmu.c > +++ b/arch/x86/kvm/mmu.c > @@ -4950,6 +4950,16 @@ int kvm_mmu_page_fault(struct kvm_vcpu *vcpu, gva_= t cr2, u64 error_code, > if (mmio_info_in_cache(vcpu, cr2, direct)) > emulation_type =3D 0; > emulate: > + /* > + * On AMD platforms, under certain conditions insn_len may be zer= o on #NPF. > + * This can happen if a guest gets a page-fault on data access bu= t the HW > + * table walker is not able to read the instruction page (e.g ins= truction > + * page is not present in memory). In those cases we simply resta= rt the > + * guest. > + */ > + if (unlikely(insn && !insn_len)) > + return 1; > + How does this work, for instance, with MMIO at CPL3 with SMAP enabled?