From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: "Nadav Har'El" <nyh@math.technion.ac.il>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] KVM: Introduce VCPU-wide notion of guest-mode V2
Date: Wed, 1 Dec 2010 14:20:20 +0100 [thread overview]
Message-ID: <20101201132020.GA11986@amd.com> (raw)
In-Reply-To: <20101201113830.GA5469@fermat.math.technion.ac.il>
On Wed, Dec 01, 2010 at 06:38:30AM -0500, Nadav Har'El wrote:
> Can you please say a few words why you'd want to move this nested-exit
> request bit to x86.c?
I don't want to move the actual exit-code itself into generic code. This
code is different between svm and vmx. I think we could implement a
call-back in kvm_x86_ops which is called when a vmexit is requested.
The benefit is that we have a single and well-defined place where we
emulate a vmexit.
SVM already as a similar mechanism internally because nested_svm_vmexit
may sleep and can't be called from certain places. Another reason is
that emulating a vmexit at a wrong plase may have side-effects (for
example when called from within the instruction emulator).
With a generic request-bit I can remove the SVM internal implementation
and nested vmx could use it too. I am certain you will need something
similar in nested-vmx too.
> Do you want to move some of the exit logic to x86.c - e.g., for the
> injection logic?
Thats another and probably more complex topic. I need a better
understanding of (nested-)vmx before we discuss how this can be done.
But a vmexit-callback may be helpful there as well.
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-12-01 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 15:38 [PATCH 0/3] KVM: Introduce VCPU-wide notion of guest-mode Joerg Roedel
2010-11-29 15:38 ` [PATCH 1/3] KVM: X86: Introduce generic guest-mode representation Joerg Roedel
2010-11-29 16:10 ` Avi Kivity
2010-11-29 15:38 ` [PATCH 2/3] KVM: SVM: Make Use of the generic guest-mode functions Joerg Roedel
2010-11-29 15:38 ` [PATCH 3/3] KVM: X86: Don't report L2 emulation failures to user-space Joerg Roedel
2010-11-29 16:10 ` [PATCH 0/3] KVM: Introduce VCPU-wide notion of guest-mode Avi Kivity
2010-11-29 16:25 ` Roedel, Joerg
2010-11-29 16:51 ` [PATCH 0/3] KVM: Introduce VCPU-wide notion of guest-mode V2 Joerg Roedel
2010-12-01 8:01 ` Nadav Har'El
2010-12-01 10:03 ` Roedel, Joerg
2010-12-01 11:38 ` Nadav Har'El
2010-12-01 13:20 ` Roedel, Joerg [this message]
2010-12-02 2:42 ` Marcelo Tosatti
2010-11-29 16:51 ` [PATCH 1/3] KVM: X86: Introduce generic guest-mode representation Joerg Roedel
2010-11-29 16:51 ` [PATCH 2/3] KVM: SVM: Make Use of the generic guest-mode functions Joerg Roedel
2010-11-29 16:51 ` [PATCH 3/3] KVM: X86: Don't report L2 emulation failures to user-space Joerg Roedel
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=20101201132020.GA11986@amd.com \
--to=joerg.roedel@amd.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nyh@math.technion.ac.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.