Re: [Qemu-devel] [PATCH 2/3] numa: move default mapping init to machine

2017-05-22 Thread Eduardo Habkost
On Mon, May 22, 2017 at 09:04:03AM +0200, Igor Mammedov wrote: > On Thu, 18 May 2017 15:50:58 -0300 > Eduardo Habkost wrote: > > On Thu, May 18, 2017 at 10:09:30AM +0200, Igor Mammedov wrote: [...] > > > > > +default_mapping = !i; /* i == 0 : no explicit mapping provided

Re: [Qemu-devel] [PATCH 2/3] numa: move default mapping init to machine

2017-05-22 Thread Igor Mammedov
On Thu, 18 May 2017 15:50:58 -0300 Eduardo Habkost wrote: > On Thu, May 18, 2017 at 10:09:30AM +0200, Igor Mammedov wrote: > > there is no need use cpu_index_to_instance_props() for setting > > default cpu -> node mapping. Generic machine code can do it > > without cpu_index

Re: [Qemu-devel] [PATCH 2/3] numa: move default mapping init to machine

2017-05-18 Thread Eduardo Habkost
On Thu, May 18, 2017 at 10:09:30AM +0200, Igor Mammedov wrote: > there is no need use cpu_index_to_instance_props() for setting > default cpu -> node mapping. Generic machine code can do it > without cpu_index by just enabling already preset defaults > in possible_cpus. > > PS: > as bonus it

[Qemu-devel] [PATCH 2/3] numa: move default mapping init to machine

2017-05-18 Thread Igor Mammedov
there is no need use cpu_index_to_instance_props() for setting default cpu -> node mapping. Generic machine code can do it without cpu_index by just enabling already preset defaults in possible_cpus. PS: as bonus it makes one less user of cpu_index_to_instance_props() Signed-off-by: Igor