On Mon, Jun 09, 2014 at 10:44:02AM +0800, Hu Tao wrote:
On Fri, Jun 06, 2014 at 02:48:15PM +0200, Igor Mammedov wrote:
On Fri, 6 Jun 2014 17:29:38 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, May 30, 2014 at 09:59:55AM +0200, Igor Mammedov wrote:
On Fri, 30 May 2014 00:05:51
On Mon, Jun 9, 2014 at 12:44 PM, Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, Jun 06, 2014 at 02:48:15PM +0200, Igor Mammedov wrote:
On Fri, 6 Jun 2014 17:29:38 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, May 30, 2014 at 09:59:55AM +0200, Igor Mammedov wrote:
On Fri, 30 May 2014
On Mon, Jun 09, 2014 at 06:54:54PM +1000, Peter Crosthwaite wrote:
On Mon, Jun 9, 2014 at 12:44 PM, Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, Jun 06, 2014 at 02:48:15PM +0200, Igor Mammedov wrote:
On Fri, 6 Jun 2014 17:29:38 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, May 30,
On Fri, Jun 06, 2014 at 02:48:15PM +0200, Igor Mammedov wrote:
On Fri, 6 Jun 2014 17:29:38 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, May 30, 2014 at 09:59:55AM +0200, Igor Mammedov wrote:
On Fri, 30 May 2014 00:05:51 +1000
Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
On Fri, May 30, 2014 at 09:59:55AM +0200, Igor Mammedov wrote:
On Fri, 30 May 2014 00:05:51 +1000
Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
On Tue, May 27, 2014 at 11:01 PM, Igor Mammedov imamm...@redhat.com wrote:
Provides framework for splitting host RAM allocation/
On Fri, 6 Jun 2014 17:29:38 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, May 30, 2014 at 09:59:55AM +0200, Igor Mammedov wrote:
On Fri, 30 May 2014 00:05:51 +1000
Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
On Tue, May 27, 2014 at 11:01 PM, Igor Mammedov
On Fri, 30 May 2014 00:05:51 +1000
Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
On Tue, May 27, 2014 at 11:01 PM, Igor Mammedov imamm...@redhat.com wrote:
Provides framework for splitting host RAM allocation/
policies into a separate backend that could be used
by devices.
On Thu, 29 May 2014 10:41:32 -0600
Eric Blake ebl...@redhat.com wrote:
On 05/27/2014 07:01 AM, Igor Mammedov wrote:
Provides framework for splitting host RAM allocation/
policies into a separate backend that could be used
by devices.
Initially only legacy RAM backend is provided,
Igor Mammedov imamm...@redhat.com writes:
On Thu, 29 May 2014 10:41:32 -0600
Eric Blake ebl...@redhat.com wrote:
On 05/27/2014 07:01 AM, Igor Mammedov wrote:
[...]
+goto out;
+}
+if (!value) {
+error_setg(local_err, Property '%s.%s' doesn't take value '%
+
On Fri, 30 May 2014 10:21:04 +0200
Markus Armbruster arm...@redhat.com wrote:
Igor Mammedov imamm...@redhat.com writes:
On Thu, 29 May 2014 10:41:32 -0600
Eric Blake ebl...@redhat.com wrote:
On 05/27/2014 07:01 AM, Igor Mammedov wrote:
[...]
+goto out;
+}
+if
On Tue, May 27, 2014 at 11:01 PM, Igor Mammedov imamm...@redhat.com wrote:
Provides framework for splitting host RAM allocation/
policies into a separate backend that could be used
by devices.
Initially only legacy RAM backend is provided, which
uses memory_region_init_ram() allocator and
Il 29/05/2014 16:05, Peter Crosthwaite ha scritto:
+path = object_get_canonical_path_component(OBJECT(backend));
+memory_region_init_ram(backend-mr, OBJECT(backend), path,
Passing the full canonical path as the name of memory region is
redundant as that information is already passed
Il 29/05/2014 17:39, Peter Crosthwaite ha scritto:
It's not the full canonical path, it's basically the id.
Fair enough. Although its still redundant though isn't it?
Should we ever clean up messages etc in memory api to include both
owner and name this is going to come out:
foo/bar/baz:baz
On Fri, May 30, 2014 at 1:25 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 29/05/2014 16:05, Peter Crosthwaite ha scritto:
+path = object_get_canonical_path_component(OBJECT(backend));
+memory_region_init_ram(backend-mr, OBJECT(backend), path,
Passing the full canonical path as
On 05/27/2014 07:01 AM, Igor Mammedov wrote:
Provides framework for splitting host RAM allocation/
policies into a separate backend that could be used
by devices.
Initially only legacy RAM backend is provided, which
uses memory_region_init_ram() allocator and compatible
with every CLI
Provides framework for splitting host RAM allocation/
policies into a separate backend that could be used
by devices.
Initially only legacy RAM backend is provided, which
uses memory_region_init_ram() allocator and compatible
with every CLI option that affects memory_region_init_ram().
16 matches
Mail list logo
