On Fri, Feb 27, 2015 at 04:56:06PM +0800, Wincy Van wrote:
On Sun, Feb 15, 2015 at 2:27 PM, Yong Wang yong.y.w...@linux.intel.com
wrote:
Wincy, our QA found regressions with this patch that 64bit L2 linux guest
fails to boot up when running nested kvm on kvm.
Environment:
On Sun, Feb 15, 2015 at 2:27 PM, Yong Wang yong.y.w...@linux.intel.com wrote:
Wincy, our QA found regressions with this patch that 64bit L2 linux guest
fails to boot up when running nested kvm on kvm.
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS
Cc Rongrong,
On Fri, Feb 27, 2015 at 04:56:06PM +0800, Wincy Van wrote:
On Sun, Feb 15, 2015 at 2:27 PM, Yong Wang yong.y.w...@linux.intel.com wrote:
Wincy, our QA found regressions with this patch that 64bit L2 linux guest
fails to boot up when running nested kvm on kvm.
Environment:
On Sun, Feb 15, 2015 at 2:27 PM, Yong Wang yong.y.w...@linux.intel.com wrote:
On Tue, Feb 03, 2015 at 11:58:17PM +0800, Wincy Van wrote:
If vcpu has a interrupt in vmx non-root mode, we will
kick that vcpu to inject interrupt timely. With posted
interrupt processing, the kick intr is not
On Tue, Feb 03, 2015 at 11:58:17PM +0800, Wincy Van wrote:
If vcpu has a interrupt in vmx non-root mode, we will
kick that vcpu to inject interrupt timely. With posted
interrupt processing, the kick intr is not needed, and
interrupts are fully taken care of by hardware.
In nested vmx, this
If vcpu has a interrupt in vmx non-root mode, we will
kick that vcpu to inject interrupt timely. With posted
interrupt processing, the kick intr is not needed, and
interrupts are fully taken care of by hardware.
In nested vmx, this feature avoids much more vmexits
than non-nested vmx.
This patch
