From: Avi Kivity <avi@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: Will KVM support "Xen on KVM" type in nested virtualization ?
Date: Sun, 12 Aug 2012 12:49:24 +0300 [thread overview]
Message-ID: <50277C24.2030107@redhat.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A101402EA@SHSMSX101.ccr.corp.intel.com>
On 08/12/2012 12:41 PM, Ren, Yongjie wrote:
>> > #define CPU_BASED_RDTSC_EXITING 0x00001000
>> > #define VM_EXIT_ACK_INTR_ON_EXIT 0x00008000
>> >
>> > Will KVM expose these two features in its vCPU ?
>>
>> Those are two bugs in kvm. The first is trivial to fix, the second is
>> harder. I will take a look.
>>
> That'll be great. Thank you.
> Will these two be fixed in kernel side or qemu side?
kernel side.
> Maybe I can file a bug to track it later.
>
Yes please.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-08-12 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 9:20 Will KVM support "Xen on KVM" type in nested virtualization ? Ren, Yongjie
2012-08-12 8:52 ` Avi Kivity
2012-08-12 9:41 ` Ren, Yongjie
2012-08-12 9:49 ` Avi Kivity [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=50277C24.2030107@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yongjie.ren@intel.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 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.