All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Andrey Ryabinin <a.ryabinin@samsung.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Chris Wright <chrisw@sous-sol.org>,
	xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	virtualization@lists.linux-foundation.org,
	Alok Kataria <akataria@vmware.com>
Subject: Re: [Xen-devel] kasan_map_early_shadow() on Xen
Date: Wed, 04 Mar 2015 05:53:04 +0100	[thread overview]
Message-ID: <54F68FB0.1040909@suse.com> (raw)
In-Reply-To: <CAB=NE6WWqP959DHN==XzrOhg5i8+xMZNmHcuBSbuyf-4tcRCtQ@mail.gmail.com>

On 03/03/2015 08:20 PM, Luis R. Rodriguez wrote:
> On Tue, Mar 3, 2015 at 2:06 AM, David Vrabel <david.vrabel@citrix.com> wrote:
>> On 03/03/15 09:40, Luis R. Rodriguez wrote:
>>> Andrey,
>>>
>>> I believe that on Xen we should disable kasan, would like confirmation
>>
>> Why?  This is the first of heard of this.
>
> Andrey chimed in here confirming this.
>
>>> 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 future. The CR4 shadow issue was another
>>> recent example issue, also introduced via v4.0 [0]. We can't keep
>>> doing this reactively.
>>>
>>> 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 but PVOPs' goal is to enable
>>
>> Why?  Again, this is the first I've heard of this as well.  FWIW, all
>> the Xen configs we use have SPARSEMEM_VMEMMAP enabled.
>
> Interesting... we have config ARCH_SPARSEMEM_ENABLE depend on !XEN at
> SUSE. Figured this was a generic issue. The SUSE kernels are based on
> 3.12 though, but anyway with it enabled I do get compile failures
> because of redefinition of MAX_PHYSMEM_BITS which we provide on Xen
> set to 43 for some reason (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...

The SUSE kernel has several patches renaming/altering Xen-related config
options. Don't mix that up with upstream/pvops.

Juergen

  parent reply	other threads:[~2015-03-04  4:53 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  9:40 kasan_map_early_shadow() on Xen Luis R. Rodriguez
2015-03-03 10:06 ` [Xen-devel] " David Vrabel
2015-03-03 10:06 ` David Vrabel
2015-03-03 10:06 ` [Xen-devel] " David Vrabel
2015-03-03 19:20   ` Luis R. Rodriguez
2015-03-03 19:20   ` [Xen-devel] " Luis R. Rodriguez
2015-03-03 19:20     ` Luis R. Rodriguez
2015-03-04  4:53     ` Juergen Gross
2015-03-04  4:53     ` [Xen-devel] " Juergen Gross
2015-03-04  4:53     ` Juergen Gross [this message]
2015-03-04  8:02       ` Jan Beulich
2015-03-04  8:02       ` [Xen-devel] " Jan Beulich
2015-03-04  8:02         ` Jan Beulich
2015-03-03 10:09 ` Jan Beulich
2015-03-03 10:09 ` Jan Beulich
2015-03-03 10:09 ` [Xen-devel] " Jan Beulich
2015-03-03 13:15 ` Andrey Ryabinin
2015-03-03 13:15 ` Andrey Ryabinin
2015-03-03 14:16   ` Konrad Rzeszutek Wilk
2015-03-03 14:16   ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-03-03 14:16     ` Konrad Rzeszutek Wilk
2015-03-03 15:38     ` Andrey Ryabinin
2015-03-03 15:38     ` Andrey Ryabinin
2015-03-03 16:02       ` Konrad Rzeszutek Wilk
2015-03-03 16:02         ` Konrad Rzeszutek Wilk
2015-03-04 14:36         ` Andrey Ryabinin
2015-03-04 14:36         ` [Xen-devel] " Andrey Ryabinin
2015-03-04 14:36         ` Andrey Ryabinin
2015-03-05  1:47           ` Luis R. Rodriguez
2015-03-05  1:47           ` [Xen-devel] " Luis R. Rodriguez
2015-03-06 16:02             ` Konrad Rzeszutek Wilk
2015-03-06 16:02               ` Konrad Rzeszutek Wilk
2015-03-06 16:47               ` Luis R. Rodriguez
2015-03-06 16:47               ` Luis R. Rodriguez
2015-12-15 20:02                 ` Luis R. Rodriguez
2015-12-15 20:02                 ` [Xen-devel] " Luis R. Rodriguez
2015-12-15 20:02                 ` Luis R. Rodriguez
2015-03-06 16:47               ` Luis R. Rodriguez
2015-03-06 16:02             ` Konrad Rzeszutek Wilk
2015-03-05  1:47           ` [Xen-devel] " Luis R. Rodriguez
2015-03-03 16:02       ` Konrad Rzeszutek Wilk
2015-03-03 15:38     ` Andrey Ryabinin
2015-03-03 13:15 ` Andrey Ryabinin

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=54F68FB0.1040909@suse.com \
    --to=jgross@suse.com \
    --cc=JBeulich@suse.com \
    --cc=a.ryabinin@samsung.com \
    --cc=akataria@vmware.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=chrisw@sous-sol.org \
    --cc=david.vrabel@citrix.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.