From: Greg Edwards <gedwards@ddn.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Huang, Kai" <kai.huang@linux.intel.com>,
kvm@vger.kernel.org, "Sasha Levin" <alexander.levin@verizon.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Jim Mattson" <jmattson@google.com>,
pfeiner@google.com
Subject: Re: [4.1.y] vmwrite error: reg 401e value a9 (err 1)
Date: Thu, 17 Nov 2016 09:12:54 -0700 [thread overview]
Message-ID: <20161117161254.GA3425@psuche> (raw)
In-Reply-To: <5dce69ed-3f0d-95af-10bc-b91b3a5f711f@redhat.com>
On Thu, Nov 17, 2016 at 01:41:12PM +0100, Paolo Bonzini wrote:
> On 09/11/2016 04:10, Huang, Kai wrote:
>> Hi Greg,
>>
>> Thanks for reporting this issue.
>>
>> I don't have 4.1.y source code tree at hand but after taking a glance
>> looks the commit a3eaa8649e4c6a6afdafaa04b9114fb230617bb1 ("KVM: VMX:
>> Fix commit which broke PML") fixes this by removing vmwrite to
>> SECONDARY_VM_EXEC_CONTROL in vmx_disable_pml, so yes I think this commit
>> can fix this issue.
>>
>> But I think you probably need another commit to fix potential vmwrite
>> error when creating vcpu: 4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec (kvm:
>> vmx: ensure VMCS is current while enabling PML). Peter found and fixed
>> this issue, so I also added him to cc-list.
>>
>> Paolo/Radim, please comment if I made mistake here.
>
> Yes, we should backport both of them. Greg, can you test it? Then I'll
> send the two patches to linux-stable.
Yes, we've been running with both patches internally without problems
for a week or so.
Greg
prev parent reply other threads:[~2016-11-17 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 0:17 [4.1.y] vmwrite error: reg 401e value a9 (err 1) Greg Edwards
2016-11-09 3:10 ` Huang, Kai
2016-11-17 12:41 ` Paolo Bonzini
2016-11-17 16:12 ` Greg Edwards [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=20161117161254.GA3425@psuche \
--to=gedwards@ddn.com \
--cc=alexander.levin@verizon.com \
--cc=jmattson@google.com \
--cc=kai.huang@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=pfeiner@google.com \
--cc=rkrcmar@redhat.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).