Hi Igor,
On 2/28/22 6:54 PM, Igor Mammedov wrote:
On Mon, 28 Feb 2022 12:26:53 +0800
Gavin Shan wrote:
On 2/25/22 6:03 PM, Igor Mammedov wrote:
On Fri, 25 Feb 2022 16:41:43 +0800
Gavin Shan wrote:
On 2/17/22 10:14 AM, Gavin Shan wrote:
On 1/26/22 5:14 PM, Igor Mammedov wrote:
On Wed, 26 J
On Mon, 28 Feb 2022 12:26:53 +0800
Gavin Shan wrote:
> Hi Igor,
>
> On 2/25/22 6:03 PM, Igor Mammedov wrote:
> > On Fri, 25 Feb 2022 16:41:43 +0800
> > Gavin Shan wrote:
> >> On 2/17/22 10:14 AM, Gavin Shan wrote:
> >>> On 1/26/22 5:14 PM, Igor Mammedov wrote:
> On Wed, 26 Jan 2022 1
Hi Igor,
On 2/25/22 6:03 PM, Igor Mammedov wrote:
On Fri, 25 Feb 2022 16:41:43 +0800
Gavin Shan wrote:
On 2/17/22 10:14 AM, Gavin Shan wrote:
On 1/26/22 5:14 PM, Igor Mammedov wrote:
On Wed, 26 Jan 2022 13:24:10 +0800
Gavin Shan wrote:
The default CPU-to-NUMA association is given by mc-
On Fri, 25 Feb 2022 16:41:43 +0800
Gavin Shan wrote:
> Hi Igor,
>
> On 2/17/22 10:14 AM, Gavin Shan wrote:
> > On 1/26/22 5:14 PM, Igor Mammedov wrote:
> >> On Wed, 26 Jan 2022 13:24:10 +0800
> >> Gavin Shan wrote:
> >>
> >>> The default CPU-to-NUMA association is given by
> >>> mc->get_de
Hi Igor,
On 2/17/22 10:14 AM, Gavin Shan wrote:
On 1/26/22 5:14 PM, Igor Mammedov wrote:
On Wed, 26 Jan 2022 13:24:10 +0800
Gavin Shan wrote:
The default CPU-to-NUMA association is given by mc->get_default_cpu_node_id()
when it isn't provided explicitly. However, the CPU topology isn't fully
On 1/26/22 5:14 PM, Igor Mammedov wrote:
On Wed, 26 Jan 2022 13:24:10 +0800
Gavin Shan wrote:
The default CPU-to-NUMA association is given by mc->get_default_cpu_node_id()
when it isn't provided explicitly. However, the CPU topology isn't fully
considered in the default association and it caus
On 2/15/22 4:32 PM, Andrew Jones wrote:
On Tue, Feb 15, 2022 at 04:19:01PM +0800, Gavin Shan wrote:
The issue isn't related to CPU topology directly. It's actually related
to the fact: the default NUMA node ID will be picked for one particular
CPU if the associated NUMA node ID isn't provided by
On 1/28/22 3:05 PM, wangyanan (Y) via wrote
On 2022/1/26 17:14, Igor Mammedov wrote:
On Wed, 26 Jan 2022 13:24:10 +0800
Gavin Shan wrote:
The default CPU-to-NUMA association is given by mc->get_default_cpu_node_id()
when it isn't provided explicitly. However, the CPU topology isn't fully
cons
On Tue, Feb 15, 2022 at 04:19:01PM +0800, Gavin Shan wrote:
> The issue isn't related to CPU topology directly. It's actually related
> to the fact: the default NUMA node ID will be picked for one particular
> CPU if the associated NUMA node ID isn't provided by users explicitly.
> So it's related
On Wed, 26 Jan 2022 at 09:14, Igor Mammedov wrote:
>
> On Wed, 26 Jan 2022 13:24:10 +0800
> Gavin Shan wrote:
> > diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> > index 141350bf21..b4a95522d3 100644
> > --- a/hw/arm/virt.c
> > +++ b/hw/arm/virt.c
> > @@ -2499,7 +2499,7 @@ virt_cpu_index_to_props(Ma
Hi,
On 2022/1/26 17:14, Igor Mammedov wrote:
On Wed, 26 Jan 2022 13:24:10 +0800
Gavin Shan wrote:
The default CPU-to-NUMA association is given by mc->get_default_cpu_node_id()
when it isn't provided explicitly. However, the CPU topology isn't fully
considered in the default association and it
On Wed, 26 Jan 2022 13:24:10 +0800
Gavin Shan wrote:
> The default CPU-to-NUMA association is given by mc->get_default_cpu_node_id()
> when it isn't provided explicitly. However, the CPU topology isn't fully
> considered in the default association and it causes CPU topology broken
> warnings on b
CCing Igor.
Thanks,
drew
On Wed, Jan 26, 2022 at 01:24:10PM +0800, Gavin Shan wrote:
> The default CPU-to-NUMA association is given by mc->get_default_cpu_node_id()
> when it isn't provided explicitly. However, the CPU topology isn't fully
> considered in the default association and it causes C
The default CPU-to-NUMA association is given by mc->get_default_cpu_node_id()
when it isn't provided explicitly. However, the CPU topology isn't fully
considered in the default association and it causes CPU topology broken
warnings on booting Linux guest.
For example, the following warning message
14 matches
Mail list logo
