linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: "Li,Rongqing" <lirongqing@baidu.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"jgross@suse.com" <jgross@suse.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>
Subject: Re: 答复: [RFC PATCH] x86/acpi: Prevent x2apic id -1 from being accounted
Date: Mon, 9 Apr 2018 16:46:55 +0800	[thread overview]
Message-ID: <148150f5-4b33-c064-a877-88c20f63e96e@cn.fujitsu.com> (raw)
In-Reply-To: <2AD939572F25A448A3AE3CAEA61328C23758FDF3@BC-MAIL-M28.internal.baidu.com>

RongQing,

At 04/09/2018 02:38 PM, Li,Rongqing wrote:
> 
> 
>> -----邮件原件-----
>> 发件人: Dou Liyang [mailto:douly.fnst@cn.fujitsu.com]
>> 发送时间: 2018年4月9日 13:38
>> 收件人: Li,Rongqing <lirongqing@baidu.com>; linux-kernel@vger.kernel.org;
>> tglx@linutronix.de; mingo@redhat.com; hpa@zytor.com; jgross@suse.com;
>> x86@kernel.org; peterz@infradead.org
>> 主题: Re: [RFC PATCH] x86/acpi: Prevent x2apic id -1 from being accounted
>>
>> Hi RongQing,
>>
>> Is there an local x2apic whose ID is  in your machine?
>>
> 
> I think no

[...]

> [    0.000000] ACPI: X2APIC (apic_id[0xffffffff] uid[0x00] disabled)
> [    0.000000] ACPI: X2APIC (apic_id[0xffffffff] uid[0x01] disabled)
> [    0.000000] ACPI: X2APIC (apic_id[0xffffffff] uid[0x02] disabled)

Ah, sure enough!

[...]
> 
> 
>> At 04/08/2018 07:38 PM, Li RongQing wrote:
>>> local_apic_id of acpi_madt_local_x2apic is u32, it is converted to int
>>> when checked by default_apic_id_valid() and return true if it is
>>> larger than 0x7fffffff, this is wrong
>>>
>>
>> For x2apic enabled systems,
>>
>>     - the byte length of X2APIC ID is 4, and it can be larger than
>>       0x7fffffff in theory
>>
> 
> Yes
> 
>>     - the ->apic_id_valid points to x2apic_apic_id_valid(), which always
>>       return _ture_ , not default_apic_id_valid().
>>
> 
> To this machine, the apic is apic_flat

I see, I am sorry the title and changelog make me misunderstand.

   Here, actually, we prevent all the X2APIC Id from being parsed in
   non-x2apic mode, not just 0xFFFFFFFF. because the values of x2APIC ID
   must be 255 and greater in ACPI MADT.

> 
> -RongQing
> 
>> Thanks,
>> 	dou
>>
>>> and if local_apic_id is invalid, we should prevent it from being
>>> accounted > This fixes a bug that Purley platform displays too many
>>> possible cpu
>>>
>>> Signed-off-by: Li RongQing <lirongqing@baidu.com>
>>> Cc: Peter Zijlstra <peterz@infradead.org>
>>> Cc: Thomas Gleixner <tglx@linutronix.de>
>>> Cc: Dou Liyang <douly.fnst@cn.fujitsu.com>
>>> ---
>>>    arch/x86/include/asm/apic.h          |  4 ++--
>>>    arch/x86/kernel/acpi/boot.c          | 10 ++++++----
>>>    arch/x86/kernel/apic/apic_common.c   |  2 +-
>>>    arch/x86/kernel/apic/apic_numachip.c |  2 +-
>>>    arch/x86/kernel/apic/x2apic.h        |  2 +-
>>>    arch/x86/kernel/apic/x2apic_phys.c   |  2 +-
>>>    arch/x86/kernel/apic/x2apic_uv_x.c   |  2 +-
>>>    arch/x86/xen/apic.c                  |  2 +-
>>>    8 files changed, 14 insertions(+), 12 deletions(-)
>>>
>>> diff --git a/arch/x86/include/asm/apic.h b/arch/x86/include/asm/apic.h
>>> index 40a3d3642f3a..08acd954f00e 100644
>>> --- a/arch/x86/include/asm/apic.h
>>> +++ b/arch/x86/include/asm/apic.h
>>> @@ -313,7 +313,7 @@ struct apic {
>>>    	/* Probe, setup and smpboot functions */
>>>    	int	(*probe)(void);
>>>    	int	(*acpi_madt_oem_check)(char *oem_id, char
>> *oem_table_id);
>>> -	int	(*apic_id_valid)(int apicid);
>>> +	int	(*apic_id_valid)(u32 apicid);
>>>    	int	(*apic_id_registered)(void);
>>>
>>>    	bool	(*check_apicid_used)(physid_mask_t *map, int apicid);
>>> @@ -486,7 +486,7 @@ static inline unsigned int read_apic_id(void)
>>>    	return apic->get_apic_id(reg);
>>>    }
>>>
>>> -extern int default_apic_id_valid(int apicid);
>>> +extern int default_apic_id_valid(u32 apicid);
>>>    extern int default_acpi_madt_oem_check(char *, char *);
>>>    extern void default_setup_apic_routing(void);
>>>
>>> diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
>>> index 7a37d9357bc4..7412564dc2a7 100644
>>> --- a/arch/x86/kernel/acpi/boot.c
>>> +++ b/arch/x86/kernel/acpi/boot.c
>>> @@ -200,7 +200,7 @@ acpi_parse_x2apic(struct acpi_subtable_header
>> *header, const unsigned long end)
>>>    {
>>>    	struct acpi_madt_local_x2apic *processor = NULL;
>>>    #ifdef CONFIG_X86_X2APIC
>>> -	int apic_id;
>>> +	u32 apic_id;
>>>    	u8 enabled;
>>>    #endif
>>>
>>> @@ -222,10 +222,12 @@ acpi_parse_x2apic(struct acpi_subtable_header
>> *header, const unsigned long end)
>>>    	 * to not preallocating memory for all NR_CPUS
>>>    	 * when we use CPU hotplug.
>>>    	 */
>>> -	if (!apic->apic_id_valid(apic_id) && enabled)
>>> +	if (!apic->apic_id_valid(apic_id)) {
>>>    		printk(KERN_WARNING PREFIX "x2apic entry ignored\n");

Due to the disable APIC entries may not exist physically, please just
printk the warning if the APIC ID is enabled.

if (!apic->apic_id_valid(apic_id)) {
	if(enabled)
		printk...

	return 0;
}



Thanks,
	dou

  parent reply	other threads:[~2018-04-09  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-08 11:38 [RFC PATCH] x86/acpi: Prevent x2apic id -1 from being accounted Li RongQing
2018-04-09  5:37 ` Dou Liyang
     [not found]   ` <2AD939572F25A448A3AE3CAEA61328C23758FDF3@BC-MAIL-M28.internal.baidu.com>
2018-04-09  8:46     ` Dou Liyang [this message]
2018-04-09  9:33       ` 答复: 答复: " Li,Rongqing
2018-04-09 12:16         ` Dou Liyang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=148150f5-4b33-c064-a877-88c20f63e96e@cn.fujitsu.com \
    --to=douly.fnst@cn.fujitsu.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lirongqing@baidu.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).