From: Gregory Haskins <gregory.haskins@gmail.com>
To: "Kumar, Venkat" <Venkat.Kumar@lsi.com>
Cc: Avi Kivity <avi@redhat.com>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM_HYPERCALL
Date: Mon, 18 May 2009 07:58:34 -0400 [thread overview]
Message-ID: <4A114D6A.2030508@gmail.com> (raw)
In-Reply-To: <3D9CB4061D1EB3408D4A0B910433453C030BCA8A1A@inbmail01.lsi.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Kumar, Venkat wrote:
> Hi Avi - Yes the control is not coming to neither " kvm_handle_exit " nor "handle_vmcall" after the hypercall is made from the guest.
> If I am not wrong, the "KVM_HYPERCALL" instruction is expected to work, isn't it?
>
Hi Venkat,
I have used this method of IO many times, so I can attest it does work
in general. I suspect that there may be some issue in either the
configuration of your environment or perhaps your particular usage of it.
What version guest and host are you running? Can you confirm that your
guest has the proper pv-ops support enabled? If so, do you check the
cpuid for the presence of your HC feature (or at least check for the
presence of others if you are not explicitly advertising your own, like
MMU_OP). See kvm_para_has_feature(). If that returns 'true' then you
at least know the hypercall patching has been performed on your guest.
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]
next prev parent reply other threads:[~2009-05-18 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 3:44 KVM_HYPERCALL Kumar, Venkat
2009-05-17 20:25 ` KVM_HYPERCALL Avi Kivity
2009-05-18 11:28 ` KVM_HYPERCALL Kumar, Venkat
2009-05-18 11:58 ` Gregory Haskins [this message]
2009-05-18 11:28 ` KVM_HYPERCALL Kumar, Venkat
2009-05-18 11:33 ` KVM_HYPERCALL Avi Kivity
2009-05-18 12:26 ` KVM_HYPERCALL Kumar, Venkat
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=4A114D6A.2030508@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=Venkat.Kumar@lsi.com \
--cc=avi@redhat.com \
--cc=kvm@vger.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 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.