CFP: The 24th European Symposium on Research in Computer Security (ESORICS 2019)

2019-01-13 Thread Publicity Chair ESORICS 2019
*** Apologies for multiple copies *** C a l l F o r P a p e r s Twenty-fourth European Symposium on Research in Computer Security (ESORICS 2019) Luxembourg -- September 23-27, 2019 WWW:

Re: [PATCH] mm: Introduce GFP_PGTABLE

2019-01-13 Thread Anshuman Khandual
On 01/12/2019 09:19 PM, Matthew Wilcox wrote: > On Sat, Jan 12, 2019 at 02:49:29PM +0100, Christophe Leroy wrote: >> As far as I can see, >> >> #define GFP_KERNEL_ACCOUNT (GFP_KERNEL | __GFP_ACCOUNT) >> >> So what's the difference between: >> >> (GFP_KERNEL_ACCOUNT | __GFP_ZERO) &

Re: [PATCH] mm: Introduce GFP_PGTABLE

2019-01-13 Thread Anshuman Khandual
On 01/12/2019 10:18 PM, Shakeel Butt wrote: >> --- a/arch/x86/kernel/espfix_64.c >> +++ b/arch/x86/kernel/espfix_64.c >> @@ -57,8 +57,6 @@ >> # error "Need more virtual address space for the ESPFIX hack" >> #endif >> >> -#define PGALLOC_GFP (GFP_KERNEL | __GFP_ZERO) >> - >> /* This contains

Re: [PATCH] mm: Introduce GFP_PGTABLE

2019-01-13 Thread Anshuman Khandual
On 01/13/2019 11:05 PM, Michal Hocko wrote: > On Sat 12-01-19 15:56:38, Anshuman Khandual wrote: >> All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL | >> __GFP_ZERO) and using it for allocating page table pages. This causes some >> code duplication which can be easily