Re: [patch 1/2] x86: track memtype for RAM in page struct - v3

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Suresh Siddha
Date: Tuesday, September 30, 2008 - 2:14 pm

On Tue, Sep 30, 2008 at 04:21:28AM -0700, Ingo Molnar wrote:

If a driver by mistake free's a RAM page before changing its memory attribute
back to WB, we want the generic -mm to catch it.

Today, free_pages_check() prevents freeing the page with PageReserved set. We
want to use this and make sure that either set_page_uc/wc() or the driver
calling these API's set the PageReserved bit. There are already some drivers
which do SetPageReserved() before changing the attribute.

I don't know the history behind PageReserved. But is there a recommended
way to achieve what we want? Either we need to use PageReserved bit or  add
some arch specific checks (in the x86 case, check arch_1) in free_pages_check().
Right?

thanks,
suresh
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[patch 1/2] x86: track memtype for RAM in page struct, Venkatesh Pallipadi, (Fri Sep 12, 5:00 pm)
Re: [patch 1/2] x86: track memtype for RAM in page struct, Jeremy Fitzhardinge, (Sat Sep 13, 10:03 am)
Re: [patch 1/2] x86: track memtype for RAM in page struct, Jeremy Fitzhardinge, (Sun Sep 14, 7:18 am)
Re: [patch 1/2] x86: track memtype for RAM in page struct, Venki Pallipadi, (Tue Sep 23, 2:46 pm)
RE: [patch 1/2] x86: track memtype for RAM in page struct, Pallipadi, Venkatesh, (Tue Sep 23, 2:48 pm)
Re: [patch 1/2] x86: track memtype for RAM in page struct, Christoph Lameter, (Tue Sep 23, 2:59 pm)
Re: [patch 1/2] x86: track memtype for RAM in page struct - v3, Suresh Siddha, (Tue Sep 30, 2:14 pm)