kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Xiong Zhang <xiong.y.zhang@intel.com>,
	Wayne Boyer <wayne.boyer@intel.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Weijiang Yang <weijiang.yang@intel.com>
Subject: Re: [PATCH] KVM: x86/mmu: Add capability to zap only sptes for the affected memslot
Date: Mon, 14 Sep 2020 09:49:24 -0700	[thread overview]
Message-ID: <20200914164923.GH6855@sjchrist-ice> (raw)
In-Reply-To: <20200723123544.6268b465@w520.home>

On Thu, Jul 23, 2020 at 12:35:44PM -0600, Alex Williamson wrote:
> On Thu, 23 Jul 2020 08:57:11 -0700
> Sean Christopherson <sean.j.christopherson@intel.com> wrote:
> 
> > On Tue, Jul 21, 2020 at 10:00:36AM -0600, Alex Williamson wrote:
> > > On Mon, 20 Jul 2020 20:03:19 -0700
> > > Sean Christopherson <sean.j.christopherson@intel.com> wrote:
> > >   
> > > > +Weijiang
> > > > 
> > > > On Mon, Jul 13, 2020 at 12:06:50PM -0700, Sean Christopherson wrote:  
> > > > > The only ideas I have going forward are to:
> > > > > 
> > > > >   a) Reproduce the bug outside of your environment and find a resource that
> > > > >      can go through the painful bisection.    
> > > > 
> > > > We're trying to reproduce the original issue in the hopes of biesecting, but
> > > > have not yet discovered the secret sauce.  A few questions:
> > > > 
> > > >   - Are there any known hardware requirements, e.g. specific flavor of GPU?  
> > > 
> > > I'm using an old GeForce GT635, I don't think there's anything special
> > > about this card.  
> > 
> > Would you be able to provide your QEMU command line?  Or at least any
> > potentially relevant bits?  Still no luck reproducing this on our end.

*sigh*

The "good" news is that we were able to reproduce and bisect the "fix".

That bad news is that the "fix" is the fracturing of large pages for the
iTLB multi-hit bug, added by commit b8e8c8303ff2 ("kvm: mmu: ITLB_MULTIHIT
mitigation").  The GPU pass-through failures can be reproduced by loading
KVM with kvm.nx_huge_pages=0.

So, we have another data point, but still no clear explanation of exactly
what is broken.

      reply	other threads:[~2020-09-14 16:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03  2:50 [PATCH] KVM: x86/mmu: Add capability to zap only sptes for the affected memslot Sean Christopherson
2020-07-08 16:08 ` Paolo Bonzini
2020-07-09 21:12   ` Sean Christopherson
2020-07-09 22:18     ` Paolo Bonzini
2020-07-10  4:29       ` Sean Christopherson
2020-07-13 18:22         ` Alex Williamson
2020-07-13 19:06           ` Sean Christopherson
2020-07-21  3:03             ` Sean Christopherson
2020-07-21 16:00               ` Alex Williamson
2020-07-23 15:57                 ` Sean Christopherson
2020-07-23 18:35                   ` Alex Williamson
2020-09-14 16:49                     ` Sean Christopherson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200914164923.GH6855@sjchrist-ice \
    --to=sean.j.christopherson@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=jun.nakajima@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=wayne.boyer@intel.com \
    --cc=weijiang.yang@intel.com \
    --cc=xiong.y.zhang@intel.com \
    --cc=zhenyuw@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).