On Fri, May 29, 2015 at 04:38:31PM +0800, Chao Peng wrote:
On Fri, May 29, 2015 at 09:06:46AM +0100, Jan Beulich wrote:
On 29.05.15 at 04:43, chao.p.p...@linux.intel.com wrote:
On Thu, May 28, 2015 at 02:17:54PM +0100, Jan Beulich wrote:
On 21.05.15 at 10:41, chao.p.p...@linux.intel.com
On Mon, Jun 01, 2015 at 09:36:15AM +0100, Jan Beulich wrote:
On 01.06.15 at 10:05, chao.p.p...@linux.intel.com wrote:
2) Unfeasible to allocate memory first and do initialization later in
cpu hotplug notifications. My former approach is performing both the
allocation and initialization in
On 01.06.15 at 10:05, chao.p.p...@linux.intel.com wrote:
2) Unfeasible to allocate memory first and do initialization later in
cpu hotplug notifications. My former approach is performing both the
allocation and initialization in the CPU_STARTING, which is not a good
idea indicated by Jan.
On Fri, May 29, 2015 at 09:06:46AM +0100, Jan Beulich wrote:
On 29.05.15 at 04:43, chao.p.p...@linux.intel.com wrote:
On Thu, May 28, 2015 at 02:17:54PM +0100, Jan Beulich wrote:
On 21.05.15 at 10:41, chao.p.p...@linux.intel.com wrote:
+static int cat_cpu_init(unsigned int cpu)
+{
On 29.05.15 at 04:43, chao.p.p...@linux.intel.com wrote:
On Thu, May 28, 2015 at 02:17:54PM +0100, Jan Beulich wrote:
On 21.05.15 at 10:41, chao.p.p...@linux.intel.com wrote:
+static int cat_cpu_init(unsigned int cpu)
+{
+int rc;
+const struct cpuinfo_x86 *c = cpu_data + cpu;
On Thu, May 28, 2015 at 02:17:54PM +0100, Jan Beulich wrote:
On 21.05.15 at 10:41, chao.p.p...@linux.intel.com wrote:
For each socket, a COS to CBM mapping structure is maintained for each
COS. The mapping is indexed by COS and the value is the corresponding
CBM. Different VMs may use the
On 21.05.15 at 10:41, chao.p.p...@linux.intel.com wrote:
For each socket, a COS to CBM mapping structure is maintained for each
COS. The mapping is indexed by COS and the value is the corresponding
CBM. Different VMs may use the same CBM, a reference count is used to
indicate if the CBM is
For each socket, a COS to CBM mapping structure is maintained for each
COS. The mapping is indexed by COS and the value is the corresponding
CBM. Different VMs may use the same CBM, a reference count is used to
indicate if the CBM is available.
Signed-off-by: Chao Peng chao.p.p...@linux.intel.com
