From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755409AbaKPQBZ (ORCPT ); Sun, 16 Nov 2014 11:01:25 -0500 Received: from bh-25.webhostbox.net ([208.91.199.152]:53629 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754966AbaKPQBY (ORCPT ); Sun, 16 Nov 2014 11:01:24 -0500 Message-ID: <5468CA48.3040504@roeck-us.net> Date: Sun, 16 Nov 2014 08:01:12 -0800 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Jiang Liu , Stephen Rothwell CC: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: linux-next: Tree for Nov 14 References: <20141114192738.08e744cc@canb.auug.org.au> <20141115211922.GA2347@roeck-us.net> <54680D0A.7070900@linux.intel.com> <5468185D.5020400@roeck-us.net> <54682618.1070508@linux.intel.com> <54684A9E.90606@roeck-us.net> <54685F39.3060007@linux.intel.com> In-Reply-To: <54685F39.3060007@linux.intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-CTCH-PVer: 0000001 X-CTCH-Spam: Unknown X-CTCH-VOD: Unknown X-CTCH-Flags: 0 X-CTCH-RefID: str=0001.0A020204.5468CA53.0172,ss=1,re=0.001,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CTCH-Score: 0.001 X-CTCH-ScoreCust: 0.000 X-CTCH-Rules: C_4847, X-CTCH-SenderID: linux@roeck-us.net X-CTCH-SenderID-Flags: 0 X-CTCH-SenderID-TotalMessages: 2 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 0 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-TotalRecipients: 0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: mailgid no entry from get_relayhosts_entry X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Guenter