public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Jim Mattson <jmattson@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Joerg Roedel <joro@8bytes.org>, kvm list <kvm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Oliver Upton <oupton@google.com>, Peter Shier <pshier@google.com>
Subject: Re: [PATCH] KVM: x86: Don't attempt to load PDPTRs when 64-bit mode is enabled
Date: Tue, 4 Aug 2020 12:09:49 -0700	[thread overview]
Message-ID: <20200804190949.GA25586@linux.intel.com> (raw)
In-Reply-To: <CALMp9eQb32UB_tLowkr5T+Rt9SBdJbTkjHWyWFg+6ruJ_OuaKw@mail.gmail.com>

On Tue, Aug 04, 2020 at 11:46:58AM -0700, Jim Mattson wrote:
> On Tue, Aug 4, 2020 at 11:41 AM Sean Christopherson
> <sean.j.christopherson@intel.com> wrote:
> 
> > Ping.  This really needs to be in the initial pull for 5.9, as is kvm/queue
> > has a 100% fatality rate for me.
> 
> I agree completely, but I am curious what guest you have that toggles
> CD/NW in 64-bit mode.

It's my OVMF build.  I assume it's MTRR programming, but I haven't bothered
to debug that far.  Nor do I want to, the EDKII build framework makes my
head explode :-).

  reply	other threads:[~2020-08-04 19:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14  1:57 [PATCH] KVM: x86: Don't attempt to load PDPTRs when 64-bit mode is enabled Sean Christopherson
2020-07-14 12:00 ` Vitaly Kuznetsov
2020-07-14 13:21   ` Sean Christopherson
2020-07-14 14:11     ` Vitaly Kuznetsov
2020-07-14 18:55 ` Jim Mattson
2020-07-14 18:58   ` Sean Christopherson
2020-07-14 19:02     ` Jim Mattson
2020-08-04 18:41 ` Sean Christopherson
2020-08-04 18:46   ` Jim Mattson
2020-08-04 19:09     ` Sean Christopherson [this message]
2020-08-05  7:04 ` Maxim Levitsky
2020-08-06 21:32   ` Jim Mattson

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=20200804190949.GA25586@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oupton@google.com \
    --cc=pbonzini@redhat.com \
    --cc=pshier@google.com \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.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