From: Marc Zyngier <maz@kernel.org>
To: zhukeqian <zhukeqian1@huawei.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <sean.j.christopherson@intel.com>,
Jay Zhou <jianjay.zhou@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] KVM: arm64: support enabling dirty log graually in small chunks
Date: Tue, 10 Mar 2020 13:16:53 +0000 [thread overview]
Message-ID: <a642a79ea9190542a9098e4c9dc5a9f2@kernel.org> (raw)
In-Reply-To: <64925c8b-af3d-beb5-bc9b-66ef1e47f92d@huawei.com>
On 2020-03-10 08:26, zhukeqian wrote:
> Hi Marc,
>
> On 2020/3/9 19:45, Marc Zyngier wrote:
>> Kegian,
[...]
>> Is there a userspace counterpart to it?
>>
> As this KVM/x86 related changes have not been merged to mainline
> kernel, some little modification is needed on mainline Qemu.
Could you please point me to these changes?
> As I tested this patch on a 128GB RAM Linux VM with no huge pages, the
> time of enabling dirty log will decrease obviously.
I'm not sure how realistic that is. Not having huge pages tends to lead
to pretty bad performance in general...
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: zhukeqian <zhukeqian1@huawei.com>
Cc: kvm@vger.kernel.org, Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-kernel@vger.kernel.org,
Sean Christopherson <sean.j.christopherson@intel.com>,
James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Jay Zhou <jianjay.zhou@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] KVM: arm64: support enabling dirty log graually in small chunks
Date: Tue, 10 Mar 2020 13:16:53 +0000 [thread overview]
Message-ID: <a642a79ea9190542a9098e4c9dc5a9f2@kernel.org> (raw)
In-Reply-To: <64925c8b-af3d-beb5-bc9b-66ef1e47f92d@huawei.com>
On 2020-03-10 08:26, zhukeqian wrote:
> Hi Marc,
>
> On 2020/3/9 19:45, Marc Zyngier wrote:
>> Kegian,
[...]
>> Is there a userspace counterpart to it?
>>
> As this KVM/x86 related changes have not been merged to mainline
> kernel, some little modification is needed on mainline Qemu.
Could you please point me to these changes?
> As I tested this patch on a 128GB RAM Linux VM with no huge pages, the
> time of enabling dirty log will decrease obviously.
I'm not sure how realistic that is. Not having huge pages tends to lead
to pretty bad performance in general...
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: zhukeqian <zhukeqian1@huawei.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jay Zhou <jianjay.zhou@huawei.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [RFC] KVM: arm64: support enabling dirty log graually in small chunks
Date: Tue, 10 Mar 2020 13:16:53 +0000 [thread overview]
Message-ID: <a642a79ea9190542a9098e4c9dc5a9f2@kernel.org> (raw)
In-Reply-To: <64925c8b-af3d-beb5-bc9b-66ef1e47f92d@huawei.com>
On 2020-03-10 08:26, zhukeqian wrote:
> Hi Marc,
>
> On 2020/3/9 19:45, Marc Zyngier wrote:
>> Kegian,
[...]
>> Is there a userspace counterpart to it?
>>
> As this KVM/x86 related changes have not been merged to mainline
> kernel, some little modification is needed on mainline Qemu.
Could you please point me to these changes?
> As I tested this patch on a 128GB RAM Linux VM with no huge pages, the
> time of enabling dirty log will decrease obviously.
I'm not sure how realistic that is. Not having huge pages tends to lead
to pretty bad performance in general...
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-03-10 13:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 8:57 [RFC] KVM: arm64: support enabling dirty log graually in small chunks Keqian Zhu
2020-03-09 8:57 ` Keqian Zhu
2020-03-09 8:57 ` Keqian Zhu
2020-03-09 11:45 ` Marc Zyngier
2020-03-09 11:45 ` Marc Zyngier
2020-03-09 11:45 ` Marc Zyngier
2020-03-10 8:26 ` zhukeqian
2020-03-10 8:26 ` zhukeqian
2020-03-10 8:26 ` zhukeqian
2020-03-10 13:16 ` Marc Zyngier [this message]
2020-03-10 13:16 ` Marc Zyngier
2020-03-10 13:16 ` Marc Zyngier
2020-03-11 7:19 ` zhukeqian
2020-03-11 7:19 ` zhukeqian
2020-03-11 7:19 ` zhukeqian
2020-03-11 7:34 ` Zhoujian (jay)
2020-03-11 7:34 ` Zhoujian (jay)
2020-03-11 7:34 ` Zhoujian (jay)
2020-03-12 1:45 ` zhukeqian
2020-03-12 1:45 ` zhukeqian
2020-03-12 1:45 ` zhukeqian
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=a642a79ea9190542a9098e4c9dc5a9f2@kernel.org \
--to=maz@kernel.org \
--cc=jianjay.zhou@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=zhukeqian1@huawei.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.