search for: ca15f20f

...can't find that justification), so it doesn't use the default 46 that would be used otherwise. But another reason seems to be the lack of forward porting yet PAT support for PV domains -- commit 47591df50 upstream which requires us to still have the union on the pte_t, and I suppose we need ca15f20f as well... If there is nothing else I suppose this just requires fixing up at SUSE's end for SPARSEMEM_VMEMMAP... --- ./arch/x86/include/asm/pgtable_64_types.h 2015-03-02 13:35:49.885257763 -0800 +++ ./arch/x86/include/mach-xen/asm/pgtable_64_types.h 2015-03-02 13:36:25.554259348 -0800 @@...

...can't find that justification), so it doesn't use the default 46 that would be used otherwise. But another reason seems to be the lack of forward porting yet PAT support for PV domains -- commit 47591df50 upstream which requires us to still have the union on the pte_t, and I suppose we need ca15f20f as well... If there is nothing else I suppose this just requires fixing up at SUSE's end for SPARSEMEM_VMEMMAP... --- ./arch/x86/include/asm/pgtable_64_types.h 2015-03-02 13:35:49.885257763 -0800 +++ ./arch/x86/include/mach-xen/asm/pgtable_64_types.h 2015-03-02 13:36:25.554259348 -0800 @@...

...justification), so it > doesn't use the default 46 that would be used otherwise. But another > reason seems to be the lack of forward porting yet PAT support for PV > domains -- commit 47591df50 upstream which requires us to still have > the union on the pte_t, and I suppose we need ca15f20f as well... > > If there is nothing else I suppose this just requires fixing up at > SUSE's end for SPARSEMEM_VMEMMAP... The SUSE kernel has several patches renaming/altering Xen-related config options. Don't mix that up with upstream/pvops. Juergen

...so it >> doesn't use the default 46 that would be used otherwise. But another >> reason seems to be the lack of forward porting yet PAT support for PV >> domains -- commit 47591df50 upstream which requires us to still have >> the union on the pte_t, and I suppose we need ca15f20f as well... >> >> If there is nothing else I suppose this just requires fixing up at >> SUSE's end for SPARSEMEM_VMEMMAP... > > The SUSE kernel has several patches renaming/altering Xen-related config > options. Don't mix that up with upstream/pvops. Exactly - so...

Andrey, I believe that on Xen we should disable kasan, would like confirmation from someone on xen-devel though. Here's the thing though -- if true -- I'd like to do it *properly*, where *properly* means addressing a bit of architecture. A simple Kconfig slap seems rather reactive. I'd like to address a way to properly ensure we don't run into this and other similar issues in the

Andrey, I believe that on Xen we should disable kasan, would like confirmation from someone on xen-devel though. Here's the thing though -- if true -- I'd like to do it *properly*, where *properly* means addressing a bit of architecture. A simple Kconfig slap seems rather reactive. I'd like to address a way to properly ensure we don't run into this and other similar issues in the