@Jing Qi Thanks for your comments.
@Martin Kletzander Thanks for your help on fixing the issues and refine the
comments.
I have no problem on current patches.
>-Original Message-
>From: Martin Kletzander
>Sent: Friday, April 16, 2021 8:48 PM
>To: Zhong, Luyao
>
he policy) for themselves. AFAIK QEMU does not provide
> an API for this, neither should it have the permissions to do it.
> We, however, can do that if we just use cgroups. And 'virsh numatune'
> already provides that for the whole domain (we just don't have an API
> to do that pe
>-Original Message-
>From: Martin Kletzander
>Sent: Wednesday, March 31, 2021 5:37 PM
>To: Zhong, Luyao
>Cc: Daniel P. Berrangé ; libvir-list@redhat.com
>Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in numatune
>
>On Wed, Mar 31, 2021 at
>-Original Message-
>From: Martin Kletzander
>Sent: Wednesday, March 31, 2021 12:21 AM
>To: Zhong, Luyao
>Cc: Daniel P. Berrangé ; libvir-list@redhat.com
>Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in numatune
>
>On Tue, Mar 30, 2021 at
> -Original Message-
> From: Martin Kletzander
> Sent: Thursday, March 25, 2021 10:28 PM
> To: Daniel P. Berrangé
> Cc: Zhong, Luyao ; libvir-list@redhat.com
> Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in numatune
>
> On Thu, Mar 25,
> -Original Message-
> From: Martin Kletzander
> Sent: Thursday, March 25, 2021 4:46 AM
> To: Daniel P. Berrangé
> Cc: Zhong, Luyao ; libvir-list@redhat.com
> Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in numatune
>
> On Tue, Mar 23,
Do I need attach the test results to patch and send a new version again? This
patch set is seems missed by developers.
Regards,
Luyao
From: Han Han
Sent: Thursday, January 7, 2021 5:57 PM
To: Zhong, Luyao
Cc: libvir-list@redhat.com
Subject: Re: [libvirt][PATCH v3 3/3] qemu: add parser
Thanks Daniel, I forgot it.
Regards,
Luyao
-Original Message-
From: Daniel Henrique Barboza
Sent: Tuesday, January 5, 2021 8:29 PM
To: Zhong, Luyao ; libvir-list@redhat.com
Subject: Re: [libvirt][PATCH v2 0/3] introduce 'restrictive' mode in numatune
Luyao,
I failed to realize
On 11/23/2020 8:14 PM, Martin Kletzander wrote:
On Mon, Nov 23, 2020 at 05:02:31PM +0800, Zhong, Luyao wrote:
On 11/20/2020 6:08 PM, Martin Kletzander wrote:
On Fri, Nov 20, 2020 at 01:17:29PM +0800, Zhong, Luyao wrote:
On 11/18/2020 8:42 PM, Martin Kletzander wrote:
So let's finish
On 11/23/2020 8:14 PM, Martin Kletzander wrote:
On Mon, Nov 23, 2020 at 05:02:31PM +0800, Zhong, Luyao wrote:
On 11/20/2020 6:08 PM, Martin Kletzander wrote:
On Fri, Nov 20, 2020 at 01:17:29PM +0800, Zhong, Luyao wrote:
On 11/18/2020 8:42 PM, Martin Kletzander wrote:
So let's finish
On 11/20/2020 6:08 PM, Martin Kletzander wrote:
On Fri, Nov 20, 2020 at 01:17:29PM +0800, Zhong, Luyao wrote:
On 11/18/2020 8:42 PM, Martin Kletzander wrote:
So let's finish this sooner rather than later. Let's remove the
"migratable/movable" attribute and add another mode f
On 11/18/2020 8:42 PM, Martin Kletzander wrote:
On Wed, Nov 18, 2020 at 05:40:04PM +0800, Zhong, Luyao wrote:
On 11/12/2020 5:27 PM, Martin Kletzander wrote:
On Thu, Nov 12, 2020 at 02:19:06PM +0800, Zhong, Luyao wrote:
On 11/9/2020 7:21 PM, Martin Kletzander wrote:
On Sat, Nov 07
On 11/12/2020 5:27 PM, Martin Kletzander wrote:
On Thu, Nov 12, 2020 at 02:19:06PM +0800, Zhong, Luyao wrote:
On 11/9/2020 7:21 PM, Martin Kletzander wrote:
On Sat, Nov 07, 2020 at 10:41:52AM +0800, Zhong, Luyao wrote:
On 11/4/2020 9:02 PM, Martin Kletzander wrote:
On Fri, Oct 16
On 11/9/2020 7:21 PM, Martin Kletzander wrote:
On Sat, Nov 07, 2020 at 10:41:52AM +0800, Zhong, Luyao wrote:
On 11/4/2020 9:02 PM, Martin Kletzander wrote:
On Fri, Oct 16, 2020 at 10:38:51PM +0800, Zhong, Luyao wrote:
On 10/16/2020 9:32 PM, Zang, Rui wrote:
How about if “migratable
On 11/4/2020 9:02 PM, Martin Kletzander wrote:
On Fri, Oct 16, 2020 at 10:38:51PM +0800, Zhong, Luyao wrote:
On 10/16/2020 9:32 PM, Zang, Rui wrote:
How about if “migratable” is set, “mode” should be ignored/omitted?
So any setting of “mode” will be rejected with an error indicating
some fixed skeleton, so it's not easy to modify.
So I need a option to indicate "I don't specify any mode.".
在 2020年10月16日，20:34，Zhong, Luyao 写道：
Hi Martin, Peter and other experts,
We got a consensus that we need introducing a new "migratable" attribute
before. But in i
tand if we introduce a 'default' option
directly.
Regards,
Luyao
On 8/26/2020 6:20 AM, Martin Kletzander wrote:
On Tue, Aug 25, 2020 at 09:42:36PM +0800, Zhong, Luyao wrote:
On 8/19/2020 11:24 PM, Martin Kletzander wrote:
On Tue, Aug 18, 2020 at 07:49:30AM +, Zang, Rui wrote:
-Origin
On 10/6/2020 3:15 PM, Peter Krempa wrote:
On Tue, Oct 06, 2020 at 13:47:25 +0800, Luyao Zhong wrote:
Attribute ``migratable`` will be 'no' by default, and 'yes' indicates
that it allows operating system or hypervisor migrating the memory
pages between different
On 8/19/2020 11:24 PM, Martin Kletzander wrote:
On Tue, Aug 18, 2020 at 07:49:30AM +, Zang, Rui wrote:
-Original Message-
From: Martin Kletzander
Sent: Monday, August 17, 2020 4:58 PM
To: Zhong, Luyao
Cc: libvir-list@redhat.com; Zang, Rui ; Michal
Privoznik
Subject: Re
On 8/7/2020 4:24 PM, Martin Kletzander wrote:
On Fri, Aug 07, 2020 at 01:27:59PM +0800, Zhong, Luyao wrote:
On 8/3/2020 7:00 PM, Martin Kletzander wrote:
On Mon, Aug 03, 2020 at 05:31:56PM +0800, Luyao Zhong wrote:
Hi Libvirt experts,
I would like enhence the numatune snippet
On 8/3/2020 7:00 PM, Martin Kletzander wrote:
On Mon, Aug 03, 2020 at 05:31:56PM +0800, Luyao Zhong wrote:
Hi Libvirt experts,
I would like enhence the numatune snippet configuration. Given a
example snippet:
...
...
Currently, attribute mode is either 'interleave',
On 12/20/2018 12:07 AM, Daniel P. Berrangé wrote:
On Tue, Dec 18, 2018 at 09:50:40AM +0800, Luyao Zhong wrote:
On 2018/12/17 下午7:07, Daniel P. Berrangé wrote:
On Mon, Dec 17, 2018 at 05:26:13PM +0800, Luyao Zhong wrote:
The 'unarmed' option allows users to mark vNVDIMM read-only:
Why
ed', which are related to
NVDIMM memory device. So we need parse and format the xml to save
these configurations.Besides, more testcases related to these
parameters were added to verify the xml2xml process.
Signed-off-by: Zhong,Luyao
---
src/conf/domain_conf.c
.
Signed-off-by: Zhong,Luyao
---
src/qemu/qemu_command.c| 25 ++
.../memory-hotplug-nvdimm-align.args | 31
.../memory-hotplug-nvdimm-align.xml| 58 ++
.../memory-hotplug-nvdimm-persistence.args
ed', which are related to
NVDIMM memory device. So we need parse and format the xml to save
these configurations.Besides, more testcases related to these
parameters were added to verify the xml2xml process.
Signed-off-by: Zhong,Luyao
---
src/conf/domain_conf.c
On 11/16/2018 11:35 PM, Zhong, Luyao wrote:
I maybe misunderstand some comments. so sorry for that. I have updated
my reply.
On 11/8/2018 5:09 AM, John Ferlan wrote:
On 10/16/18 10:21 PM, Luyao Zhong wrote:
In order to align with QEMU ,four more parameters about NVDIMM
e details, see
https://github.com/qemu/qemu/blob/master/docs/nvdimm.txt
Not a commit message worthy... Place it under the ---...
Signed-off-by: Zhong,Luyao
---
docs/formatdomain.html.in | 98 ---
docs/schemas/domaincommon.rng | 31 --
2 f
27 matches
Mail list logo
