From: "Jan Beulich" <JBeulich@suse.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "Andy Lutomirski" <luto@amacapital.net>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
<virtualization@lists.linux-foundation.org>,
<xen-devel@lists.xenproject.org>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Andrey Ryabinin" <a.ryabinin@samsung.com>,
"Chris Wright" <chrisw@sous-sol.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Alok Kataria" <akataria@vmware.com>
Subject: Re: [Xen-devel] kasan_map_early_shadow() on Xen
Date: Tue, 03 Mar 2015 10:09:41 +0000 [thread overview]
Message-ID: <54F5967502000078000658C8@mail.emea.novell.com> (raw)
In-Reply-To: <CAB=NE6Xs5fepzNtymzT4CueeJZ0KMPETpda114DpL4eMtDswtw@mail.gmail.com>
>>> On 03.03.15 at 10:40, <mcgrof@suse.com> 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
next prev parent reply other threads:[~2015-03-03 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 9:40 Luis R. Rodriguez
2015-03-03 10:06 ` [Xen-devel] " David Vrabel
2015-03-03 19:20 ` Luis R. Rodriguez
2015-03-04 4:53 ` Juergen Gross
2015-03-04 8:02 ` Jan Beulich
2015-03-03 10:09 ` Jan Beulich [this message]
2015-03-03 13:15 ` Andrey Ryabinin
2015-03-03 14:16 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-03-03 15:38 ` Andrey Ryabinin
2015-03-03 16:02 ` Konrad Rzeszutek Wilk
2015-03-04 14:36 ` Andrey Ryabinin
2015-03-05 1:47 ` Luis R. Rodriguez
2015-03-06 16:02 ` Konrad Rzeszutek Wilk
2015-03-06 16:47 ` Luis R. Rodriguez
2015-12-15 20:02 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F5967502000078000658C8@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=a.ryabinin@samsung.com \
--cc=akataria@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®