From: Guenter Roeck <linux@roeck-us.net>
To: Jiang Liu <jiang.liu@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: Tree for Nov 14
Date: Sun, 16 Nov 2014 08:11:10 -0800 [thread overview]
Message-ID: <5468CC9E.7010300@roeck-us.net> (raw)
In-Reply-To: <5468CA48.3040504@roeck-us.net>
On 11/16/2014 08:01 AM, Guenter Roeck wrote:
> On 11/16/2014 12:24 AM, Jiang Liu wrote:
>> On 2014/11/16 14:56, Guenter Roeck wrote:
>>> On 11/15/2014 08:20 PM, Jiang Liu wrote:
>>>>
>>>> On 2014/11/16 11:22, Guenter Roeck wrote:
>>>>> On 11/15/2014 06:33 PM, Jiang Liu wrote:
>>>>>> Hi Guenter,
>>>>>> Could you please help to provide the config file and
>>>>>> error messages?
>>>>>
>>>>> Config file:
>>>>>
>>>>> https://github.com/groeck/linux-build-test/blob/master/rootfs/x86/qemu_x86_pc_nosmp_defconfig
>>>>>
>>>> Hi Guenter,
>>>> Thanks for help. According to the above configuration file:
>>>> CONFIG_PCI_MSI is enabled, but CONFIG_X86_LOCAL_APIC and
>>>> CONFIG_X86_IO_APIC are both disabled. But the Kconfig for X86_LOCAL_APIC
>>>> is defined as:
>>>> config X86_LOCAL_APIC
>>>> def_bool y
>>>> depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
>>>> || PCI_MSI
>>>> select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
>>>>
>>>> That means CONFIG_X86_LOCAL_APIC should be enabled if CONFIG_PCI_MSI is
>>>> enabled. So how did you generate the qemu_x86_pc_nosmp_defconfig? Are
>>>> you using an old configuration file?
>>>
>>> I took the configuration file I had for the SMP case (located in the same
>>> directory in the git repository), disabled SMP, and ran "make
>>> savedefconfig".
>>> "old" is relative in this context; I don't usually create new configuration
>>> files for each new kernel release, so, yes, you could say that the file
>>> I used is "old".
>>>
>>> CONFIG_X86_LOCAL_APIC is enabled. Keep in mind this is a configuration file
>>> created with "make savedefconfig", so default settings are not included.
>>> Correct, CONFIG_X86_IO_APIC is not enabled, but that is not really
>>> surprising
>>> since its dependencies are not met as far as I can see.
>>>
>>> Overall, I am not sure I understand what you are trying to say. X86_IO_APIC
>>> depends on X86_64 (not set) or SMP (not set) or X86_32_NON_STANDARD (not
>>> set)
>>> or X86_UP_IOAPIC (not set because it depends on X86_UP_APIC which
>>> depends on
>>> !PCI_MSI).
>>>
>>> Does that mean that I'll have to disable PCI_MSI to get x86 uniprocessor
>>> support to work after your patch ?
>> Hi Guenter,
>> Previously, X86_IO_APIC will be enabled if PCI_MSI is enabled.
>> With my patch, x86_IO_APIC may be disabled even if PCI_MSI is enabled.
>> If X86_LOCAL_APIC/PCI_MSI are enabled and X86_IO_APIC is disabled, it
>> should work theoretically. I remember it works on my HP laptop.
>> Could you please help to check whether it solve the issue by manually
>> turning on X86_IO_APIC?
>
> I can not turn on X86_IO_APIC manually. I have to enable one of the
> following to do it.
>
> def_bool X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC
>
> Since I want to build for 32 bit, I can not enable X86_64.
> Since I want to build a uniprocessor image, I can not enable SMP.
> X86_32_NON_STANDARD depends on SMP, so I can not enable it either.
> X86_UP_IOAPIC depends on X86_UP_APIC which I can only enable by
> disabling PCI_MSI.
>
> So I disabled PCI_MSI and enabled X86_UP_IOAPIC as well as X86_IO_APIC.
> The resulting image hangs completely with no console output whatsoever.
>
Additional data points: After reverting your patch on top of linux-next,
everything works fine. The working configuration has CONFIG_IRQ_DOMAIN,
CONFIG_X86_IO_APIC, CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS, and
CONFIG_ACPI_HOTPLUG_IOAPIC enabled. The non-working configuration
(with your patch applied) has all those disabled.
Guenter
next prev parent reply other threads:[~2014-11-16 16:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 8:27 linux-next: Tree for Nov 14 Stephen Rothwell
2014-11-15 21:19 ` Guenter Roeck
2014-11-16 2:33 ` Jiang Liu
2014-11-16 3:22 ` Guenter Roeck
2014-11-16 4:20 ` Jiang Liu
2014-11-16 6:56 ` Guenter Roeck
2014-11-16 8:24 ` Jiang Liu
2014-11-16 8:37 ` Jiang Liu
2014-11-16 15:42 ` Guenter Roeck
2014-11-16 16:01 ` Guenter Roeck
2014-11-16 16:11 ` Guenter Roeck [this message]
2014-11-17 5:12 ` Jiang Liu
2014-11-17 17:02 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 3:19 Stephen Rothwell
2022-11-14 7:49 Stephen Rothwell
2019-11-14 8:31 Stephen Rothwell
2019-11-14 18:38 ` Naresh Kamboju
2019-11-14 20:11 ` Jan Stancek
2019-11-14 21:19 ` Arnd Bergmann
2018-11-14 5:26 Stephen Rothwell
2017-11-14 6:20 Stephen Rothwell
2016-11-14 7:23 Stephen Rothwell
2013-11-14 4:22 Stephen Rothwell
2012-11-14 5:30 Stephen Rothwell
2012-11-14 5:37 ` Andrew Morton
2012-11-14 5:53 ` Andrew Morton
2012-11-14 6:47 ` Ingo Molnar
2012-11-14 6:56 ` Andrew Morton
2012-11-14 7:15 ` Stephen Rothwell
2012-11-14 7:24 ` Andrew Morton
2012-11-14 7:39 ` Ingo Molnar
2012-11-14 8:13 ` Hugh Dickins
2012-11-14 17:05 ` Rik van Riel
2012-11-15 12:10 ` Mel Gorman
2012-11-14 17:19 ` Linus Torvalds
2012-11-14 6:55 ` Stephen Rothwell
2012-11-14 7:03 ` Stephen Rothwell
2011-11-14 3:43 Stephen Rothwell
2019-11-14 16:43 ` Christian Brauner
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=5468CC9E.7010300@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).