From: Jiang Liu <jiang.liu@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Joerg Roedel <joro@8bytes.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/apic updates for v3.20
Date: Sat, 14 Feb 2015 01:47:23 +0800 [thread overview]
Message-ID: <54DE38AB.50507@linux.intel.com> (raw)
In-Reply-To: <CA+55aFwArF_px_iyAWhxOBLq5n0hxY0yW-=dgUqdxio8gEUf7w@mail.gmail.com>
On 2015/2/14 1:00, Linus Torvalds wrote:
> On Fri, Feb 13, 2015 at 7:47 AM, Joerg Roedel <joro@8bytes.org> wrote:
>>
>> So the condition should rather look like this to keep x2apic disabled
>> like before:
>
> Yes, this works for me too.
>
>> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
>> index b665d24..770a0bb 100644
>> --- a/arch/x86/kernel/apic/apic.c
>> +++ b/arch/x86/kernel/apic/apic.c
>> @@ -1580,8 +1580,8 @@ static __init void try_to_enable_x2apic(int remap_mode)
>> * under KVM
>> */
>> if (max_physical_apicid > 255 ||
>> - (IS_ENABLED(CONFIG_HYPERVISOR_GUEST) &&
>> - !hypervisor_x2apic_available())) {
>> + !(IS_ENABLED(CONFIG_HYPERVISOR_GUEST) &&
>> + hypervisor_x2apic_available())) {
>> pr_info("x2apic: IRQ remapping doesn't support X2APIC mode\n");
>> x2apic_disable();
>> return;
>>
>> Another solution would be to just revert 5fcee53ce705. This code is not
>> in any fast-path, so we can live well without that optimization.
>
> Jiang, preferences? Revert, or fix like the above?
Hi Linus,
I think reverting is better.
The IS_ENABLED(CONFIG_HYPERVISOR_GUEST) optimization doesn't
give us much, but it makes the code a little complex.
Regards!
Gerry
>
> Linus
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2015-02-13 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 9:15 [GIT PULL] x86/apic updates for v3.20 Ingo Molnar
2015-02-13 0:52 ` Linus Torvalds
2015-02-13 2:06 ` Rafael J. Wysocki
2015-02-13 2:08 ` Linus Torvalds
2015-02-13 2:50 ` Linus Torvalds
2015-02-13 5:05 ` Jiang Liu
2015-02-13 15:47 ` Joerg Roedel
2015-02-13 17:00 ` Linus Torvalds
2015-02-13 17:47 ` Jiang Liu [this message]
2015-02-16 7:22 ` Ingo Molnar
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=54DE38AB.50507@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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