Re: [PATCH 1/3] x86/pat: export io memory reserve/free api.

2016-10-22 Thread Shawn Starr
For the series, no regressions in my testing, no stalls, no issues noted. Tested by: Shawn Starr Thanks, Shawn On Tuesday, October 18, 2016 4:13:11 PM EDT Dave Airlie wrote: > From: Dave Airlie > > These functions are needed for gpu/ttm drivers to

Re: [PATCH 1/3] x86/pat: export io memory reserve/free api.

2016-10-18 Thread Edward O'Callaghan
On 10/18/2016 07:29 PM, Dave Airlie wrote: > On 18 Oct. 2016 17:23, "Edward O'Callaghan" > wrote: >> >> NACK, >> >> I think you want to use 'iomap_create_wc()' instead to avoid aliasing. > > Please explain what can alias here?

Re: [PATCH 1/3] x86/pat: export io memory reserve/free api.

2016-10-18 Thread Dave Airlie
On 18 Oct. 2016 17:23, "Edward O'Callaghan" wrote: > > NACK, > > I think you want to use 'iomap_create_wc()' instead to avoid aliasing. Please explain what can alias here? Dave. > > Kind Regards, > Edward. > > On 10/18/2016 05:13 PM, Dave Airlie wrote: > > From:

Re: [PATCH 1/3] x86/pat: export io memory reserve/free api.

2016-10-18 Thread Edward O'Callaghan
NACK, I think you want to use 'iomap_create_wc()' instead to avoid aliasing. Kind Regards, Edward. On 10/18/2016 05:13 PM, Dave Airlie wrote: > From: Dave Airlie > > These functions are needed for gpu/ttm drivers to reserve the > VRAM area as write combined. In a lot of

[PATCH 1/3] x86/pat: export io memory reserve/free api.

2016-10-18 Thread Dave Airlie
From: Dave Airlie These functions are needed for gpu/ttm drivers to reserve the VRAM area as write combined. In a lot of places we don't ioremap but still need to insert pfn from it into a VMA using vm_insert_mixed, but a recent change in mixed insertion means we need to