in; qemu-devel@nongnu.org;
> > Michael S . Tsirkin
> > Subject: Re: [Qemu-devel] [RFC] exec: eliminate ram naming issue as
> > migration
> >
> > On Sat, 24 Feb 2018 03:11:30 +
> > "Tan, Jianfeng" wrote:
> >
> > > > -Origina
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Monday, February 26, 2018 10:43 PM
> To: Igor Mammedov; Tan, Jianfeng
> Cc: Jason Wang; Maxime Coquelin; qemu-devel@nongnu.org; Michael S .
> Tsirkin
> Subject: Re: [Qemu-devel] [RFC
: 'Igor Mammedov'
> > > Cc: Paolo Bonzini; Jason Wang; Maxime Coquelin; qemu-
> de...@nongnu.org;
> > > Michael S . Tsirkin
> > > Subject: RE: [Qemu-devel] [RFC] exec: eliminate ram naming issue as
> > > migration
> > >
> > > Hi Igor and al
On 26/02/2018 13:55, Igor Mammedov wrote:
>>> So how about just adding a new option --mem-share to decide if that's a
>>> private memory or shared memory? That seems much straightforward way
> Above options are legacy (which we can't remove for compat reasons),
> their replacement is 'memory-backen
el@nongnu.org;
> > Michael S . Tsirkin
> > Subject: RE: [Qemu-devel] [RFC] exec: eliminate ram naming issue as
> > migration
> >
> > Hi Igor and all,
> >
> > > -Original Message-
> > > From: Igor Mammedov [mailto:imamm...@redhat.com]
&g
> -Original Message-
> From: Tan, Jianfeng
> Sent: Saturday, February 24, 2018 11:08 AM
> To: 'Igor Mammedov'
> Cc: Paolo Bonzini; Jason Wang; Maxime Coquelin; qemu-devel@nongnu.org;
> Michael S . Tsirkin
> Subject: RE: [Qemu-devel] [RFC] exec: eliminate
emu-devel] [RFC] exec: eliminate ram naming issue as
> migration
>
[...]
> > > It could be solved by adding memdev option to machine,
> > > which would allow to specify backend object. And then on
> > > top make -mem-path alias new option to clean thing up.
> &
t; >>>>> To: Igor Mammedov
> >>>>> Cc: Tan, Jianfeng; qemu-devel@nongnu.org; Jason Wang; Maxime Coquelin;
> >>>>> Michael S . Tsirkin
> >>>>> Subject: Re: [Qemu-devel] [RFC] exec: eliminate ram naming issue as
> >>
...@redhat.com]
Sent: Tuesday, February 6, 2018 1:32 AM
To: Igor Mammedov
Cc: Tan, Jianfeng; qemu-devel@nongnu.org; Jason Wang; Maxime Coquelin;
Michael S . Tsirkin
Subject: Re: [Qemu-devel] [RFC] exec: eliminate ram naming issue as
migration
On 05/02/2018 18:15, Igor Mammedov wrote:
Then we would have
zini [mailto:pbonz...@redhat.com]
> >>> Sent: Tuesday, February 6, 2018 1:32 AM
> >>> To: Igor Mammedov
> >>> Cc: Tan, Jianfeng; qemu-devel@nongnu.org; Jason Wang; Maxime Coquelin;
> >>> Michael S . Tsirkin
> >>> Subject: Re: [Qemu-devel] [RFC]
Jason Wang; Maxime Coquelin;
Michael S . Tsirkin
Subject: Re: [Qemu-devel] [RFC] exec: eliminate ram naming issue as
migration
On 05/02/2018 18:15, Igor Mammedov wrote:
Then we would have both ram block named pc.ram:
Block NamePSize
pc.ram 4 KiB
/obje
son Wang; Maxime Coquelin;
> > Michael S . Tsirkin
> > Subject: Re: [Qemu-devel] [RFC] exec: eliminate ram naming issue as
> > migration
> >
> > On 05/02/2018 18:15, Igor Mammedov wrote:
> > >>>
> > >>> Then we would have both ram bloc
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Tuesday, February 6, 2018 1:32 AM
> To: Igor Mammedov
> Cc: Tan, Jianfeng; qemu-devel@nongnu.org; Jason Wang; Maxime Coquelin;
> Michael S . Tsirkin
> Subject: Re: [Qemu-devel] [RFC
On Mon, 5 Feb 2018 18:36:31 +
"Dr. David Alan Gilbert" wrote:
> * Tan, Jianfeng (jianfeng@intel.com) wrote:
> >
> >
> > On 2/6/2018 12:29 AM, Igor Mammedov wrote:
> > > On Mon, 5 Feb 2018 14:58:55 +
> > > Jianfeng Tan wrote:
> > >
> > > > Existing VMs with virtio devices and
* Igor Mammedov (imamm...@redhat.com) wrote:
> On Mon, 5 Feb 2018 17:19:09 +0100
> Paolo Bonzini wrote:
>
> > On 05/02/2018 17:12, Tan, Jianfeng wrote:
> > > Hi Paolo,
> > >
> > > On 2/5/2018 11:53 PM, Paolo Bonzini wrote:
> > >> On 05/02/2018 15:58, Jianfeng Tan wrote:
> > >>> Here are some
* Tan, Jianfeng (jianfeng@intel.com) wrote:
>
>
> On 2/6/2018 12:29 AM, Igor Mammedov wrote:
> > On Mon, 5 Feb 2018 14:58:55 +
> > Jianfeng Tan wrote:
> >
> > > Existing VMs with virtio devices and vhost-kernel as the backend
> > > are always started with mem config:
> > >
> > >"-
On 05/02/2018 17:44, Tan, Jianfeng wrote:
>>>
>> I understand. However it's not as bad as "there's no possibility at all
>> to migrate from vhost-kernel to vhost-user". There are cases that are
>> more problematic: for example, there's no possibility at all to add
>> memory NUMA policy during a l
On Mon, 5 Feb 2018 14:58:55 +
Jianfeng Tan wrote:
> Existing VMs with virtio devices and vhost-kernel as the backend
> are always started with mem config:
>
> "-m xG"
> (with a ram block named "pc.ram")
>
> while new VMs with virtio devices and vhost-user as the backend
> are always st
On 05/02/2018 18:15, Igor Mammedov wrote:
>>>
>>> Then we would have both ram block named pc.ram:
>>> Block Name PSize
>>> pc.ram 4 KiB
>>> /objects/pc.ram 2 MiB
>>>
>>> But I assume it's a corner case which not really happen.
>> Yeah, you're ri
On Mon, 5 Feb 2018 17:19:09 +0100
Paolo Bonzini wrote:
> On 05/02/2018 17:12, Tan, Jianfeng wrote:
> > Hi Paolo,
> >
> > On 2/5/2018 11:53 PM, Paolo Bonzini wrote:
> >> On 05/02/2018 15:58, Jianfeng Tan wrote:
> >>> Here are some options to fix this:
> >>>
> >>> 1. When we do ram name compar
On 05/02/2018 15:58, Jianfeng Tan wrote:
> Here are some options to fix this:
>
> 1. When we do ram name comparison, we truncate the prefix as this patch shows.
> It cannot cover the corner case: the source VM could have two ram blocks
> with name of "pc.ram" and "/object/pc.ram".
That shouldn't
On 2/6/2018 12:19 AM, Paolo Bonzini wrote:
On 05/02/2018 17:12, Tan, Jianfeng wrote:
Hi Paolo,
On 2/5/2018 11:53 PM, Paolo Bonzini wrote:
On 05/02/2018 15:58, Jianfeng Tan wrote:
Here are some options to fix this:
1. When we do ram name comparison, we truncate the prefix as this
patch show
On 05/02/2018 17:12, Tan, Jianfeng wrote:
> Hi Paolo,
>
> On 2/5/2018 11:53 PM, Paolo Bonzini wrote:
>> On 05/02/2018 15:58, Jianfeng Tan wrote:
>>> Here are some options to fix this:
>>>
>>> 1. When we do ram name comparison, we truncate the prefix as this
>>> patch shows.
>>> It cannot cover the
On 2/6/2018 12:29 AM, Igor Mammedov wrote:
On Mon, 5 Feb 2018 14:58:55 +
Jianfeng Tan wrote:
Existing VMs with virtio devices and vhost-kernel as the backend
are always started with mem config:
"-m xG"
(with a ram block named "pc.ram")
while new VMs with virtio devices and vhost
Hi Paolo,
On 2/5/2018 11:53 PM, Paolo Bonzini wrote:
On 05/02/2018 15:58, Jianfeng Tan wrote:
Here are some options to fix this:
1. When we do ram name comparison, we truncate the prefix as this patch shows.
It cannot cover the corner case: the source VM could have two ram blocks
with name of
: eliminate ram naming issue as migration
=== TEST SCRIPT BEGIN ===
#!/bin/bash
set -e
git submodule update --init dtc
# Let docker tests dump environment info
export SHOW_ENV=1
export J=8
time make docker-test-mingw@fedora
=== TEST SCRIPT END ===
Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1517842735-9011-1-git-send-email-jianfeng@intel.com
Subject: [Qemu-devel] [RFC] exec: eliminate ram naming issue as migration
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE
Existing VMs with virtio devices and vhost-kernel as the backend
are always started with mem config:
"-m xG"
(with a ram block named "pc.ram")
while new VMs with virtio devices and vhost-user as the backend
are always started with mem config:
"-m xG -numa node,memdev=pc.ram -object memory-
28 matches
Mail list logo
