From: Wei Huang <wei.huang2@amd.com>
To: Andy Lutomirski <luto@kernel.org>,
Sean Christopherson <seanjc@google.com>
Cc: kvm list <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Joerg Roedel <joro@8bytes.org>, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, X86 ML <x86@kernel.org>,
Jim Mattson <jmattson@google.com>,
Wanpeng Li <wanpengli@tencent.com>, Bandan Das <bsd@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [PATCH 1/2] KVM: x86: Add emulation support for #GP triggered by VM instructions
Date: Tue, 12 Jan 2021 23:15:03 -0600 [thread overview]
Message-ID: <0d324a3d-8c33-bb6c-13f3-e60310a54b13@amd.com> (raw)
In-Reply-To: <CALCETrXsNBmXg8C4Tmz4YgTSAykKoWFHgXHFFcK-C65LUQ0r4w@mail.gmail.com>
On 1/12/21 12:58 PM, Andy Lutomirski wrote:
> Andrew Cooper points out that there may be a nicer workaround. Make
> sure that the SMRAM and HT region (FFFD00000000 - FFFFFFFFFFFF) are
> marked as reserved in the guest, too.
In theory this proposed solution can avoid intercepting #GP. But in
reality SMRAM regions can be different on different machines. So this
solution can break after VM migration.
next prev parent reply other threads:[~2021-01-13 5:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 6:37 [PATCH 1/2] KVM: x86: Add emulation support for #GP triggered by VM instructions Wei Huang
2021-01-12 6:37 ` [PATCH 2/2] KVM: SVM: Add support for VMCB address check change Wei Huang
2021-01-12 19:18 ` Sean Christopherson
2021-01-14 11:39 ` Maxim Levitsky
2021-01-14 12:04 ` Maxim Levitsky
2021-01-12 11:09 ` [PATCH 1/2] KVM: x86: Add emulation support for #GP triggered by VM instructions Maxim Levitsky
2021-01-12 21:05 ` Wei Huang
2021-01-12 12:15 ` Vitaly Kuznetsov
2021-01-12 15:11 ` Andy Lutomirski
2021-01-12 15:17 ` Maxim Levitsky
2021-01-12 15:22 ` Andy Lutomirski
2021-01-12 15:46 ` Bandan Das
2021-01-12 15:51 ` Andy Lutomirski
2021-01-12 17:56 ` Sean Christopherson
2021-01-13 4:55 ` Wei Huang
2021-01-12 21:50 ` Wei Huang
2021-01-12 14:01 ` Paolo Bonzini
2021-01-12 17:42 ` Sean Christopherson
2021-01-13 12:35 ` Paolo Bonzini
2021-01-15 7:00 ` Wei Huang
2021-01-17 18:20 ` Paolo Bonzini
2021-01-12 17:36 ` Sean Christopherson
2021-01-12 17:59 ` Sean Christopherson
2021-01-12 18:58 ` Andy Lutomirski
2021-01-13 5:15 ` Wei Huang [this message]
2021-01-14 11:42 ` Maxim Levitsky
2021-01-13 5:03 ` Wei Huang
2021-01-13 12:40 ` Paolo Bonzini
2021-01-12 19:40 ` Sean Christopherson
2021-01-12 20:00 ` Bandan Das
2021-01-14 11:47 ` Maxim Levitsky
2021-01-14 17:19 ` Sean Christopherson
2021-01-14 11:55 ` Maxim Levitsky
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=0d324a3d-8c33-bb6c-13f3-e60310a54b13@amd.com \
--to=wei.huang2@amd.com \
--cc=bp@alien8.de \
--cc=bsd@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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).