Re: operation ordering during pgd_alloc/pgd_free

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Jan Beulich
Date: Thursday, June 5, 2008 - 2:58 am

>But I think there's a problem *without* preemption.  

... which is precisely what the XenSource tree does.


It could be made so, but it doesn't at present - it exits the inner loop
when vmalloc_sync_one() returns NULL. The intention here is that if
the reference page table has a clear entry at some level, then there
shouldn't be any attempt to look at other page tables' entries mapping
the same va (and because it would be an error if page table other than
the reference one had a clear entry where the reference one didn't,
there was that BUG_ON() that your patch removed). Since the purpose
of vmalloc_sync_all() is to catch partially populated page tables, allowing
it to skip such that are under construction would need a way to
distinguish them from such being fully constructed but out of sync.

Jan

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
operation ordering during pgd_alloc/pgd_free, Jan Beulich, (Thu Jun 5, 1:51 am)
Re: operation ordering during pgd_alloc/pgd_free, Jeremy Fitzhardinge, (Thu Jun 5, 2:27 am)
Re: operation ordering during pgd_alloc/pgd_free, Jan Beulich, (Thu Jun 5, 2:58 am)