RE: [patch 07/11] PAT x86: pat-conflict resolution using linear list

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: Andi Kleen [mailto:andi@xxxxxxxxxxxxxx] 
>Sent: Thursday, January 10, 2008 11:13 AM
>To: Pallipadi, Venkatesh
>Cc: ebiederm@xxxxxxxxxxxx; rdreier@xxxxxxxxx; 
>torvalds@xxxxxxxxxxxxxxxxxxxx; gregkh@xxxxxxx; 
>airlied@xxxxxxxxx; davej@xxxxxxxxxx; mingo@xxxxxxx; 
>tglx@xxxxxxxxxxxxx; hpa@xxxxxxxx; 
>linux-kernel@xxxxxxxxxxxxxxx; Siddha, Suresh B
>Subject: Re: [patch 07/11] PAT x86: pat-conflict resolution 
>using linear list
>
>venkatesh.pallipadi@xxxxxxxxx writes:
>>  
>>  	/* Reset the direct mapping. Can block */
>> -	if (p->flags >> 20)
>> -		ioremap_change_attr(p->phys_addr, p->size, 0);
>> +	if (p->flags >> 20) {
>> +		free_mattr(p->phys_addr, p->phys_addr + 
>get_vm_area_size(p),
>> +		           p->flags>>20);
>> +		ioremap_change_attr(p->phys_addr, 
>get_vm_area_size(p), 0);
>
>If you really unmap all holes and forbid (or let it just return the
>__va address) ioremap on anything mapped (which is probably ok) then
>you can eliminate that completely.
>

We heard X can allocate a page and then map it UC using it through gart.
So, I don't we can forbid all ioremaps for RAM.

Thanks,
Venki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/