From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: Joel Schopp <joel.schopp@amd.com>, Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, David Kaplan <david.kaplan@amd.com>
Subject: Re: [PATCH] kvm: x86: svm: remove SVM_EXIT_READ_CR* intercepts
Date: Fri, 3 Apr 2015 14:19:42 +0200 [thread overview]
Message-ID: <20150403121941.GB28325@potion.brq.redhat.com> (raw)
In-Reply-To: <jpgk2yl9aqr.fsf@redhat.com>
2015-03-12 17:17-0400, Bandan Das:
> Joel Schopp <joel.schopp@amd.com> writes:
> > @@ -2968,29 +2964,10 @@ static int cr_interception(struct vcpu_svm *svm)
> > kvm_queue_exception(&svm->vcpu, UD_VECTOR);
> > return 1;
> > }
> > - } else { /* mov from cr */
> > - [reads of CR 0..8]
> > + } else { /* mov from cr, should never trap in svm */
> > + WARN(1, "unhandled read from CR%d", cr);
> > + kvm_queue_exception(&svm->vcpu, UD_VECTOR);
> > + return 1;
>
> Can we end up here if a nested hypervisor sets cr read interception ?
No. If the nested hypervisor sets intercept bits, we're going to detect
them in 'handle_exit -> nested_svm_exit_handled -> nested_svm_intercept'
and enter L1 before the cr_interception handler.
next prev parent reply other threads:[~2015-04-03 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 20:17 Joel Schopp
2015-03-12 21:17 ` Bandan Das
2015-04-03 12:19 ` Radim Krčmář [this message]
2015-03-12 21:20 ` Radim Krčmář
2015-03-16 16:16 ` Joel Schopp
2015-03-16 17:34 ` Radim Krčmář
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=20150403121941.GB28325@potion.brq.redhat.com \
--to=rkrcmar@redhat.com \
--cc=bp@alien8.de \
--cc=bsd@redhat.com \
--cc=david.kaplan@amd.com \
--cc=gleb@kernel.org \
--cc=joel.schopp@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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
Powered by JetHome