Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [patch 0/4] x86: PAT followup - Incremental changes and bug fixes
Date: Wed, 16 Jan 2008 14:14:40 -0800
Message-ID: <924EFEDD5F540B4284297C4DC59F3DEE5E8C86@orsmsx423.amr.corp.intel.com>
In-Reply-To: <20080116220153.GA39717@muc.de>
Thread-Topic: [patch 0/4] x86: PAT followup - Incremental changes and bug fixes
Thread-Index: AchYi2q/EIgt+k4MSQ6yN9tlr8WhSgAAZhsg
References: <20080116023955.597433000@intel.com> <20080116185748.GA11244@alberich.amd.com> <20080116203328.GA17869@linux-os.sc.intel.com> <20080116220153.GA39717@muc.de>
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "Andi Kleen" <ak@muc.de>
Cc: "Andreas Herrmann" <andreas.herrmann3@amd.com>, <ebiederm@xmission.com>,
       <rdreier@cisco.com>, <torvalds@linux-foundation.org>, <gregkh@suse.de>,
       <airlied@skynet.ie>, <davej@redhat.com>, <mingo@elte.hu>,
       <tglx@linutronix.de>, <hpa@zytor.com>, <akpm@linux-foundation.org>,
       <arjan@infradead.org>, "Barnes, Jesse" <jesse.barnes@intel.com>,
       <davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
       "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1271
Lines: 34

 

>-----Original Message-----
>From: Andi Kleen [mailto:ak@muc.de] 
>Sent: Wednesday, January 16, 2008 2:02 PM
>To: Pallipadi, Venkatesh
>Cc: Andreas Herrmann; ebiederm@xmission.com; 
>rdreier@cisco.com; torvalds@linux-foundation.org; 
>gregkh@suse.de; airlied@skynet.ie; davej@redhat.com; 
>mingo@elte.hu; tglx@linutronix.de; hpa@zytor.com; 
>akpm@linux-foundation.org; arjan@infradead.org; Barnes, Jesse; 
>davem@davemloft.net; linux-kernel@vger.kernel.org; Siddha, Suresh B
>Subject: Re: [patch 0/4] x86: PAT followup - Incremental 
>changes and bug fixes
>
>> This ioremap failing seems to be the real problem. This can be due to
>> new tracking of ioremaps introduced by PAT patches. We do not allow
>> conflicting ioremaps to same region. Probably that is happening
>
>Normally if there is a conflict there should be a printk (or 
>at least it was
>so in the original mattr code if you haven't changed it)
>

Yes. Printks are there. But are with KERN_DEBUG now. We should change
them to WARNING atleast.

Thanks,
Venki
--
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/