Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759346AbZDDJPu (ORCPT ); Sat, 4 Apr 2009 05:15:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752727AbZDDJPj (ORCPT ); Sat, 4 Apr 2009 05:15:39 -0400 Received: from casper.infradead.org ([85.118.1.10]:52659 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752008AbZDDJPi (ORCPT ); Sat, 4 Apr 2009 05:15:38 -0400 Subject: RE: [patch 2/2] x2apic/intr-remap: decouple interrupt remapping from x2apic From: David Woodhouse To: "Han, Weidong" Cc: "Siddha, Suresh B" , "'Ingo Molnar'" , "'IOMMU'" , "'LKML'" In-Reply-To: <1238836040.3560.17.camel@macbook.infradead.org> References: <715D42877B251141A38726ABF5CABF2C01A2F7C3A7@pdsmsx503.ccr.corp.intel.com> <1238781474.27006.7866.camel@localhost.localdomain> <715D42877B251141A38726ABF5CABF2C01A2F7C435@pdsmsx503.ccr.corp.intel.com> <1238833738.3560.14.camel@macbook.infradead.org> <715D42877B251141A38726ABF5CABF2C01A2F7C440@pdsmsx503.ccr.corp.intel.com> <1238836040.3560.17.camel@macbook.infradead.org> Content-Type: text/plain Date: Sat, 04 Apr 2009 10:15:32 +0100 Message-Id: <1238836532.3560.19.camel@macbook.infradead.org> Mime-Version: 1.0 X-Mailer: Evolution 2.26.0 (2.26.0-1.fc11) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2769 Lines: 53 On Sat, 2009-04-04 at 10:07 +0100, David Woodhouse wrote: > On Sat, 2009-04-04 at 16:48 +0800, Han, Weidong wrote: > > On linux head, I cannot find EIM_32BIT_APIC_ID in apic.c. I suspect > > iommu-2.6.git doesn't sync up with linux head on apic.c. I also fixed > > a bug which causes system hang due to queue invalidation is disabled > > when enable interrupt remapping. I will resend the patches. Do you > > want patches based on linux head or your iommu-2.6.git? BTW, I pull > > iommu-2.6.git very slow due to office proxy. But I can do it if you > > want. > > The conflict is with Fenghua's suspend/resume patches: > http://git.infradead.org/iommu-2.6.git?a=commitdiff;h=b24696bc5 > > A simpler build fix is just to move the definitions of EIM_8BIT_APIC_ID > and EIM_32BIT_APIC_ID outside #ifdef CONFIG_X86_X2APIC. I'll try that > and see if it boots. ... which it doesn't. Same failure mode (the faults are normal; crappy BIOS lacks RMRRs): [ 34.061991] DMAR:DRHD (flags: 0x00000001)base: 0x00000000fe710000 [ 34.068076] DMAR:RMRR base: 0x00000000000e9000 end: 0x00000000000e9fff [ 34.074592] DMAR:RMRR base: 0x00000000000ea000 end: 0x00000000000eafff [ 34.081105] DMAR:RMRR base: 0x00000000000eb000 end: 0x00000000000ebfff [ 34.087618] DMAR:RMRR base: 0x00000000000e6000 end: 0x00000000000e6fff [ 34.094131] DMAR:RMRR base: 0x00000000000e7000 end: 0x00000000000e7fff [ 34.100644] DMAR:RMRR base: 0x00000000000e8000 end: 0x00000000000e8fff [ 34.107157] DMAR:Unknown DMAR structure type [ 34.111413] IOAPIC id 8 under DRHD base 0xfe710000 [ 34.116220] DRHD: handling fault status reg 2 [ 34.120567] DMAR:[DMA Read] Request device [00:1a.2] fault addr ec000 [ 34.120568] DMAR:[fault reason 06] PTE Read access is not set [ 34.133298] DMAR:[DMA Read] Request device [00:1d.1] fault addr ec000 [ 34.133298] DMAR:[fault reason 06] PTE Read access is not set [ 34.145547] DMAR:[DMA Read] Request device [00:1a.1] fault addr ec000 [ 34.145548] DMAR:[fault reason 06] PTE Read access is not set [ 34.157796] DMAR:[DMA Read] Request device [00:1d.0] fault addr ec000 [ 34.157796] DMAR:[fault reason 06] PTE Read access is not set [ 34.170045] DMAR:[DMA Read] Request device [00:1a.0] fault addr ec000 [ 34.170045] DMAR:[fault reason 06] PTE Read access is not set [ 34.182294] DMAR:[DMA Read] Request device [00:1d.2] fault addr ec000 [ 34.182295] DMAR:[fault reason 06] PTE Read access is not set [ 34.194546] IOMMU 0xfe710000: using Queued invalidation -- dwmw2 -- 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/