On 2015/7/7 20:21, Igor Mammedov wrote:
On Tue, 7 Jul 2015 19:43:35 +0800
zhanghailiang wrote:
On 2015/7/7 19:23, Igor Mammedov wrote:
On Mon, 6 Jul 2015 17:59:10 +0800
zhanghailiang wrote:
On 2015/7/6 16:45, Paolo Bonzini wrote:
On 06/07/2015 09:54, zhanghailiang wrote:
From host
On 2015/7/7 19:23, Igor Mammedov wrote:
On Mon, 6 Jul 2015 17:59:10 +0800
zhanghailiang wrote:
On 2015/7/6 16:45, Paolo Bonzini wrote:
On 06/07/2015 09:54, zhanghailiang wrote:
From host, we found that QEMU vcpu1 thread and vcpu7 thread were not
consuming any cpu (Should be in idle
On 2015/7/6 16:45, Paolo Bonzini wrote:
On 06/07/2015 09:54, zhanghailiang wrote:
From host, we found that QEMU vcpu1 thread and vcpu7 thread were not
consuming any cpu (Should be in idle state),
All of VCPUs' stacks in host is like bellow:
[] kvm_vcpu_block+0x65/0xa0 [kvm]
[] __vcp
roduce this problem, we are not quite sure.
Is there any possible that the cupid emulation in kvm/qemu has some bug ?
Has anyone come across these problem before? Or any idea?
Thanks,
zhanghailiang
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a mes
On 2015/3/2 14:22, Amit Shah wrote:
On (Fri) 27 Feb 2015 [12:09:20], zhanghailiang wrote:
On 2015/2/27 3:26, Luiz Capitulino wrote:
Hello,
Reproducer:
1. Start QEMU with balloon and memory hotplug support:
# qemu [...] -m 1G,slots=2,maxmem=2G -balloon virtio
2. Check balloon size:
(qemu
ddition to reading ram_size, the balloon device in QEMU
could scan pc-dimm devices to account for hotplugged memory.
This solution was already implemented by zhanghailiang:
http://lists.gnu.org/archive/html/qemu-devel/2014-11/msg02362.html
It works, except that on Linux memory hotplu
On 2014/12/18 6:17, Stefan Fritsch wrote:
On Thursday 11 December 2014 18:15:39, Paolo Bonzini wrote:
On 11/12/2014 13:53, zhanghailiang wrote:
I think it's a Windows bug---it should prefer x2apic to hv-vapic
if both are available.
No, i don't think it is a windows bug, it has not
On 2014/12/11 19:48, Paolo Bonzini wrote:
On 11/12/2014 09:07, zhanghailiang wrote:
User space (i.e. QEMU) should be able to check whether KVM
supports apic-v. User space will use this to decide whether enable
emulated MSR-based APIC (i.e. hyperv-vapic).
Did you see an improvement in some
User space (i.e. QEMU) should be able to check whether KVM
supports apic-v. User space will use this to decide whether enable
emulated MSR-based APIC (i.e. hyperv-vapic).
Signed-off-by: zhanghailiang
---
arch/x86/kvm/x86.c | 6 ++
include/uapi/linux/kvm.h | 1 +
2 files changed, 7
On 2014/11/21 1:38, Andrea Arcangeli wrote:
Hi,
On Thu, Nov 20, 2014 at 10:54:29AM +0800, zhanghailiang wrote:
Yes, you are right. This is what i really want, bypass all non-present faults
and only track strict wrprotect faults. ;)
So, do you plan to support that in the userfault API?
Yes I
On 2014/11/20 2:49, Andrea Arcangeli wrote:
Hi Zhang,
On Fri, Oct 31, 2014 at 09:26:09AM +0800, zhanghailiang wrote:
On 2014/10/30 20:49, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2014/10/30 1:46, Andrea Arcangeli wrote:
Hi Zhanghailiang,
On
Hi Andrea,
Is there any new about this discussion? ;)
Will you plan to support 'only wrprotect fault' in the userfault API?
Thanks,
zhanghailiang
On 2014/10/30 19:31, zhanghailiang wrote:
On 2014/10/30 1:46, Andrea Arcangeli wrote:
Hi Zhanghailiang,
On Mon, Oct 27, 2014 at 05:32:
On 2014/11/1 3:39, Peter Feiner wrote:
On Fri, Oct 31, 2014 at 11:29:49AM +0800, zhanghailiang wrote:
Agreed, but for doing live memory snapshot (VM is running when do snapsphot),
we have to do this (block the write action), because we have to save the page
before it
is dirtied by writing
On 2014/10/31 13:17, Andres Lagar-Cavilla wrote:
On Thu, Oct 30, 2014 at 9:38 PM, zhanghailiang
wrote:
On 2014/10/31 11:29, zhanghailiang wrote:
On 2014/10/31 10:23, Peter Feiner wrote:
On Thu, Oct 30, 2014 at 07:31:48PM +0800, zhanghailiang wrote:
On 2014/10/30 1:46, Andrea Arcangeli
On 2014/10/31 11:29, zhanghailiang wrote:
On 2014/10/31 10:23, Peter Feiner wrote:
On Thu, Oct 30, 2014 at 07:31:48PM +0800, zhanghailiang wrote:
On 2014/10/30 1:46, Andrea Arcangeli wrote:
On Mon, Oct 27, 2014 at 05:32:51PM +0800, zhanghailiang wrote:
I want to confirm a question:
Can we
On 2014/10/31 10:23, Peter Feiner wrote:
On Thu, Oct 30, 2014 at 07:31:48PM +0800, zhanghailiang wrote:
On 2014/10/30 1:46, Andrea Arcangeli wrote:
On Mon, Oct 27, 2014 at 05:32:51PM +0800, zhanghailiang wrote:
I want to confirm a question:
Can we support distinguishing between writing and
On 2014/10/30 20:49, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2014/10/30 1:46, Andrea Arcangeli wrote:
Hi Zhanghailiang,
On Mon, Oct 27, 2014 at 05:32:51PM +0800, zhanghailiang wrote:
Hi Andrea,
Thanks for your hard work on userfault;)
This
On 2014/10/30 1:46, Andrea Arcangeli wrote:
Hi Zhanghailiang,
On Mon, Oct 27, 2014 at 05:32:51PM +0800, zhanghailiang wrote:
Hi Andrea,
Thanks for your hard work on userfault;)
This is really a useful API.
I want to confirm a question:
Can we support distinguishing between writing and
pshot, if we support configuring
userfault for writing memory only.
Thanks,
zhanghailiang
On 2014/10/4 1:07, Andrea Arcangeli wrote:
Hello everyone,
There's a large To/Cc list for this RFC because this adds two new
syscalls (userfaultfd and remap_anon_pages) and
MADV_USERFAULT/MADV_NOUSE
em >= 32M, so is it a bug of guest OS?
Any help will be appreciated.;)
Thanks,
zhanghailiang
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
booms.
The size of the PCI address space region should be fixed anyway
For it works fine when we use VFIO way, i don't know if it is really a QEMU's
bug or KVM's bug.
Any help will be appreciated.
Thanks,
zhanghailiang
--
To unsubscribe from this list: send the line "
The third parameter of kvm_iommu_put_pages is wrong,
It should be 'gfn-slot->base_gfn'
Signed-off-by: zhanghailiang
---
virt/kvm/iommu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virt/kvm/iommu.c b/virt/kvm/iommu.c
index 0df7d4b..c02f9a3 100644
--- a/vir
offset value of vCPUs' TSC will be worse when the pressure of host is large.
So is it necessary to sync all vCPUs' TSC when the guest start? May be we could
set the tsc_offset to the same value,
when vCPU is created. Is it acceptable?
Thanks,
zhanghailiang
vnmi flexpriority ept vpid
bogomips: 4800.18
clflush size: 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
Thanks
Zhang hailiang
> On Sat, Mar 29, 2014 at 08:47:27AM +, Zhanghailiang wrote:
> > Hi,
> > I found when Guest is id
Hi,
I found when Guest is idle, VDSO pvclock may increase host consumption.
We can calcutate as follow, Correct me if I am wrong.
(Host)250 * update_pvclock_gtod = 1500 * gettimeofday(Guest)
In Host, VDSO pvclock introduce a notifier chain, pvclock_gtod_chain in
timekeeping.c. It consume nea
25 matches
Mail list logo