From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756131AbbCCKJq (ORCPT ); Tue, 3 Mar 2015 05:09:46 -0500 Received: from mail.emea.novell.com ([130.57.118.101]:39349 "EHLO mail.emea.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752872AbbCCKJo convert rfc822-to-8bit (ORCPT ); Tue, 3 Mar 2015 05:09:44 -0500 Message-Id: <54F5967502000078000658C8@mail.emea.novell.com> X-Mailer: Novell GroupWise Internet Agent 14.0.1 Date: Tue, 03 Mar 2015 10:09:41 +0000 From: "Jan Beulich" To: "Luis R. Rodriguez" Cc: "Andy Lutomirski" , "Jeremy Fitzhardinge" , , , "Boris Ostrovsky" , "Rusty Russell" , "Andrey Ryabinin" , "Chris Wright" , "linux-kernel@vger.kernel.org" , "Alok Kataria" Subject: Re: [Xen-devel] kasan_map_early_shadow() on Xen References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>> On 03.03.15 at 10:40, wrote: > Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be > selected on x86 when: > > if X86_64 && SPARSEMEM_VMEMMAP > > Now Xen should not have SPARSEMEM_VMEMMAP Why would that be? Jan