From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758246AbdJMPCt (ORCPT ); Fri, 13 Oct 2017 11:02:49 -0400 Received: from userp1040.oracle.com ([156.151.31.81]:21644 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753503AbdJMPCr (ORCPT ); Fri, 13 Oct 2017 11:02:47 -0400 X-Google-Smtp-Source: ABhQp+QCs/RqAptldsTDUcKztrL0QLAHG614h9WXbsrikzA1uj3H1tlkpinLd0sjFHURgBrKt7QMTqvmiQ2mTanRK8k= MIME-Version: 1.0 In-Reply-To: <20171013145431.GA5919@leverpostej> References: <20171009221931.1481-1-pasha.tatashin@oracle.com> <20171009221931.1481-8-pasha.tatashin@oracle.com> <20171010155619.GA2517@arm.com> <20171010171047.GC2517@arm.com> <20171013144319.GB4746@arm.com> <20171013145431.GA5919@leverpostej> From: Pavel Tatashin Date: Fri, 13 Oct 2017 11:02:42 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v11 7/9] arm64/kasan: add and use kasan_map_populate() To: Mark Rutland Cc: Will Deacon , linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org, linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org, x86@kernel.org, kasan-dev@googlegroups.com, borntraeger@de.ibm.com, heiko.carstens@de.ibm.com, davem@davemloft.net, willy@infradead.org, Michal Hocko , Ard Biesheuvel , catalin.marinas@arm.com, sam@ravnborg.org, mgorman@techsingularity.net, Steve Sistare , daniel.m.jordan@oracle.com, bob.picco@oracle.com Content-Type: text/plain; charset="UTF-8" X-Source-IP: userv0021.oracle.com [156.151.31.71] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Do you know what your physical memory layout looks like? [ 0.000000] Memory: 34960K/131072K available (16316K kernel code, 6716K rwdata, 7996K rodata, 1472K init, 8837K bss, 79728K reserved, 16384K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] kasan : 0xffff000000000000 - 0xffff200000000000 ( 32768 GB) [ 0.000000] modules : 0xffff200000000000 - 0xffff200008000000 ( 128 MB) [ 0.000000] vmalloc : 0xffff200008000000 - 0xffff7dffbfff0000 ( 96254 GB) [ 0.000000] .text : 0xffff200008080000 - 0xffff200009070000 ( 16320 KB) [ 0.000000] .rodata : 0xffff200009070000 - 0xffff200009850000 ( 8064 KB) [ 0.000000] .init : 0xffff200009850000 - 0xffff2000099c0000 ( 1472 KB) [ 0.000000] .data : 0xffff2000099c0000 - 0xffff20000a04f200 ( 6717 KB) [ 0.000000] .bss : 0xffff20000a04f200 - 0xffff20000a8f09e0 ( 8838 KB) [ 0.000000] fixed : 0xffff7dfffe7fd000 - 0xffff7dfffec00000 ( 4108 KB) [ 0.000000] PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000 ( 16 MB) [ 0.000000] vmemmap : 0xffff7e0000000000 - 0xffff800000000000 ( 2048 GB maximum) [ 0.000000] 0xffff7e0000000000 - 0xffff7e0000200000 ( 2 MB actual) [ 0.000000] memory : 0xffff800000000000 - 0xffff800008000000 ( 128 MB) > > Knowing that would tell us where shadow memory *should* be. > > Can you share the command line you're using the launch the VM? > virtme-run --kdir . --arch aarch64 --qemu-opts -s -S and get messages from connected gdb session via lx-dmesg command. The actual qemu arguments are these: qemu-system-aarch64 -fsdev local,id=virtfs1,path=/,security_model=none,readonly -device virtio-9p-device,fsdev=virtfs1,mount_tag=/dev/root -fsdev local,id=virtfs5,path=/usr/share/virtme-guest-0,security_model=none,readonly -device virtio-9p-device,fsdev=virtfs5,mount_tag=virtme.guesttools -M virt -cpu cortex-a57 -parallel none -net none -echr 1 -serial none -chardev stdio,id=console,signal=off,mux=on -serial chardev:console -mon chardev=console -vga none -display none -kernel ./arch/arm64/boot/Image -append 'earlyprintk=serial,ttyAMA0,115200 console=ttyAMA0 psmouse.proto=exps "virtme_stty_con=rows 57 cols 105 iutf8" TERM=screen-256color-bce rootfstype=9p rootflags=version=9p2000.L,trans=virtio,access=any raid=noautodetect ro init=/bin/sh -- -c "mount -t tmpfs run /run;mkdir -p /run/virtme/guesttools;/bin/mount -n -t 9p -o ro,version=9p2000.L,trans=virtio,access=any virtme.guesttools /run/virtme/guesttools;exec /run/virtme/guesttools/virtme-init"' -s -S From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Tatashin Date: Fri, 13 Oct 2017 15:02:42 +0000 Subject: Re: [PATCH v11 7/9] arm64/kasan: add and use kasan_map_populate() Message-Id: List-Id: References: <20171009221931.1481-1-pasha.tatashin@oracle.com> <20171009221931.1481-8-pasha.tatashin@oracle.com> <20171010155619.GA2517@arm.com> <20171010171047.GC2517@arm.com> <20171013144319.GB4746@arm.com> <20171013145431.GA5919@leverpostej> In-Reply-To: <20171013145431.GA5919@leverpostej> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-arm-kernel@lists.infradead.org > Do you know what your physical memory layout looks like? [ 0.000000] Memory: 34960K/131072K available (16316K kernel code, 6716K rwdata, 7996K rodata, 1472K init, 8837K bss, 79728K reserved, 16384K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] kasan : 0xffff000000000000 - 0xffff200000000000 ( 32768 GB) [ 0.000000] modules : 0xffff200000000000 - 0xffff200008000000 ( 128 MB) [ 0.000000] vmalloc : 0xffff200008000000 - 0xffff7dffbfff0000 ( 96254 GB) [ 0.000000] .text : 0xffff200008080000 - 0xffff200009070000 ( 16320 KB) [ 0.000000] .rodata : 0xffff200009070000 - 0xffff200009850000 ( 8064 KB) [ 0.000000] .init : 0xffff200009850000 - 0xffff2000099c0000 ( 1472 KB) [ 0.000000] .data : 0xffff2000099c0000 - 0xffff20000a04f200 ( 6717 KB) [ 0.000000] .bss : 0xffff20000a04f200 - 0xffff20000a8f09e0 ( 8838 KB) [ 0.000000] fixed : 0xffff7dfffe7fd000 - 0xffff7dfffec00000 ( 4108 KB) [ 0.000000] PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000 ( 16 MB) [ 0.000000] vmemmap : 0xffff7e0000000000 - 0xffff800000000000 ( 2048 GB maximum) [ 0.000000] 0xffff7e0000000000 - 0xffff7e0000200000 ( 2 MB actual) [ 0.000000] memory : 0xffff800000000000 - 0xffff800008000000 ( 128 MB) > > Knowing that would tell us where shadow memory *should* be. > > Can you share the command line you're using the launch the VM? > virtme-run --kdir . --arch aarch64 --qemu-opts -s -S and get messages from connected gdb session via lx-dmesg command. The actual qemu arguments are these: qemu-system-aarch64 -fsdev local,id=virtfs1,path=/,security_model=none,readonly -device virtio-9p-device,fsdev=virtfs1,mount_tag=/dev/root -fsdev local,id=virtfs5,path=/usr/share/virtme-guest-0,security_model=none,readonly -device virtio-9p-device,fsdev=virtfs5,mount_tag=virtme.guesttools -M virt -cpu cortex-a57 -parallel none -net none -echr 1 -serial none -chardev stdio,id=console,signal=off,mux=on -serial chardev:console -mon chardev=console -vga none -display none -kernel ./arch/arm64/boot/Image -append 'earlyprintk=serial,ttyAMA0,115200 console=ttyAMA0 psmouse.proto=exps "virtme_stty_con=rows 57 cols 105 iutf8" TERM=screen-256color-bce rootfstype=9p rootflags=version=9p2000.L,trans=virtio,access=any raid=noautodetect ro init=/bin/sh -- -c "mount -t tmpfs run /run;mkdir -p /run/virtme/guesttools;/bin/mount -n -t 9p -o ro,version=9p2000.L,trans=virtio,access=any virtme.guesttools /run/virtme/guesttools;exec /run/virtme/guesttools/virtme-init"' -s -S From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f198.google.com (mail-qk0-f198.google.com [209.85.220.198]) by kanga.kvack.org (Postfix) with ESMTP id 6ACD16B0033 for ; Fri, 13 Oct 2017 11:02:47 -0400 (EDT) Received: by mail-qk0-f198.google.com with SMTP id k123so3849498qke.5 for ; Fri, 13 Oct 2017 08:02:47 -0700 (PDT) Received: from aserp1040.oracle.com (aserp1040.oracle.com. [141.146.126.69]) by mx.google.com with ESMTPS id u6si943265qkd.122.2017.10.13.08.02.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Oct 2017 08:02:46 -0700 (PDT) Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v9DF2i76020861 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 13 Oct 2017 15:02:45 GMT Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id v9DF2i7o032610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 13 Oct 2017 15:02:44 GMT Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id v9DF2hVY016069 for ; Fri, 13 Oct 2017 15:02:44 GMT Received: by mail-oi0-f53.google.com with SMTP id h200so14723503oib.4 for ; Fri, 13 Oct 2017 08:02:43 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20171013145431.GA5919@leverpostej> References: <20171009221931.1481-1-pasha.tatashin@oracle.com> <20171009221931.1481-8-pasha.tatashin@oracle.com> <20171010155619.GA2517@arm.com> <20171010171047.GC2517@arm.com> <20171013144319.GB4746@arm.com> <20171013145431.GA5919@leverpostej> From: Pavel Tatashin Date: Fri, 13 Oct 2017 11:02:42 -0400 Message-ID: Subject: Re: [PATCH v11 7/9] arm64/kasan: add and use kasan_map_populate() Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Mark Rutland Cc: Will Deacon , linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org, linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org, x86@kernel.org, kasan-dev@googlegroups.com, borntraeger@de.ibm.com, heiko.carstens@de.ibm.com, davem@davemloft.net, willy@infradead.org, Michal Hocko , Ard Biesheuvel , catalin.marinas@arm.com, sam@ravnborg.org, mgorman@techsingularity.net, Steve Sistare , daniel.m.jordan@oracle.com, bob.picco@oracle.com > Do you know what your physical memory layout looks like? [ 0.000000] Memory: 34960K/131072K available (16316K kernel code, 6716K rwdata, 7996K rodata, 1472K init, 8837K bss, 79728K reserved, 16384K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] kasan : 0xffff000000000000 - 0xffff200000000000 ( 32768 GB) [ 0.000000] modules : 0xffff200000000000 - 0xffff200008000000 ( 128 MB) [ 0.000000] vmalloc : 0xffff200008000000 - 0xffff7dffbfff0000 ( 96254 GB) [ 0.000000] .text : 0xffff200008080000 - 0xffff200009070000 ( 16320 KB) [ 0.000000] .rodata : 0xffff200009070000 - 0xffff200009850000 ( 8064 KB) [ 0.000000] .init : 0xffff200009850000 - 0xffff2000099c0000 ( 1472 KB) [ 0.000000] .data : 0xffff2000099c0000 - 0xffff20000a04f200 ( 6717 KB) [ 0.000000] .bss : 0xffff20000a04f200 - 0xffff20000a8f09e0 ( 8838 KB) [ 0.000000] fixed : 0xffff7dfffe7fd000 - 0xffff7dfffec00000 ( 4108 KB) [ 0.000000] PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000 ( 16 MB) [ 0.000000] vmemmap : 0xffff7e0000000000 - 0xffff800000000000 ( 2048 GB maximum) [ 0.000000] 0xffff7e0000000000 - 0xffff7e0000200000 ( 2 MB actual) [ 0.000000] memory : 0xffff800000000000 - 0xffff800008000000 ( 128 MB) > > Knowing that would tell us where shadow memory *should* be. > > Can you share the command line you're using the launch the VM? > virtme-run --kdir . --arch aarch64 --qemu-opts -s -S and get messages from connected gdb session via lx-dmesg command. The actual qemu arguments are these: qemu-system-aarch64 -fsdev local,id=virtfs1,path=/,security_model=none,readonly -device virtio-9p-device,fsdev=virtfs1,mount_tag=/dev/root -fsdev local,id=virtfs5,path=/usr/share/virtme-guest-0,security_model=none,readonly -device virtio-9p-device,fsdev=virtfs5,mount_tag=virtme.guesttools -M virt -cpu cortex-a57 -parallel none -net none -echr 1 -serial none -chardev stdio,id=console,signal=off,mux=on -serial chardev:console -mon chardev=console -vga none -display none -kernel ./arch/arm64/boot/Image -append 'earlyprintk=serial,ttyAMA0,115200 console=ttyAMA0 psmouse.proto=exps "virtme_stty_con=rows 57 cols 105 iutf8" TERM=screen-256color-bce rootfstype=9p rootflags=version=9p2000.L,trans=virtio,access=any raid=noautodetect ro init=/bin/sh -- -c "mount -t tmpfs run /run;mkdir -p /run/virtme/guesttools;/bin/mount -n -t 9p -o ro,version=9p2000.L,trans=virtio,access=any virtme.guesttools /run/virtme/guesttools;exec /run/virtme/guesttools/virtme-init"' -s -S -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: pasha.tatashin@oracle.com (Pavel Tatashin) Date: Fri, 13 Oct 2017 11:02:42 -0400 Subject: [PATCH v11 7/9] arm64/kasan: add and use kasan_map_populate() In-Reply-To: <20171013145431.GA5919@leverpostej> References: <20171009221931.1481-1-pasha.tatashin@oracle.com> <20171009221931.1481-8-pasha.tatashin@oracle.com> <20171010155619.GA2517@arm.com> <20171010171047.GC2517@arm.com> <20171013144319.GB4746@arm.com> <20171013145431.GA5919@leverpostej> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > Do you know what your physical memory layout looks like? [ 0.000000] Memory: 34960K/131072K available (16316K kernel code, 6716K rwdata, 7996K rodata, 1472K init, 8837K bss, 79728K reserved, 16384K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] kasan : 0xffff000000000000 - 0xffff200000000000 ( 32768 GB) [ 0.000000] modules : 0xffff200000000000 - 0xffff200008000000 ( 128 MB) [ 0.000000] vmalloc : 0xffff200008000000 - 0xffff7dffbfff0000 ( 96254 GB) [ 0.000000] .text : 0xffff200008080000 - 0xffff200009070000 ( 16320 KB) [ 0.000000] .rodata : 0xffff200009070000 - 0xffff200009850000 ( 8064 KB) [ 0.000000] .init : 0xffff200009850000 - 0xffff2000099c0000 ( 1472 KB) [ 0.000000] .data : 0xffff2000099c0000 - 0xffff20000a04f200 ( 6717 KB) [ 0.000000] .bss : 0xffff20000a04f200 - 0xffff20000a8f09e0 ( 8838 KB) [ 0.000000] fixed : 0xffff7dfffe7fd000 - 0xffff7dfffec00000 ( 4108 KB) [ 0.000000] PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000 ( 16 MB) [ 0.000000] vmemmap : 0xffff7e0000000000 - 0xffff800000000000 ( 2048 GB maximum) [ 0.000000] 0xffff7e0000000000 - 0xffff7e0000200000 ( 2 MB actual) [ 0.000000] memory : 0xffff800000000000 - 0xffff800008000000 ( 128 MB) > > Knowing that would tell us where shadow memory *should* be. > > Can you share the command line you're using the launch the VM? > virtme-run --kdir . --arch aarch64 --qemu-opts -s -S and get messages from connected gdb session via lx-dmesg command. The actual qemu arguments are these: qemu-system-aarch64 -fsdev local,id=virtfs1,path=/,security_model=none,readonly -device virtio-9p-device,fsdev=virtfs1,mount_tag=/dev/root -fsdev local,id=virtfs5,path=/usr/share/virtme-guest-0,security_model=none,readonly -device virtio-9p-device,fsdev=virtfs5,mount_tag=virtme.guesttools -M virt -cpu cortex-a57 -parallel none -net none -echr 1 -serial none -chardev stdio,id=console,signal=off,mux=on -serial chardev:console -mon chardev=console -vga none -display none -kernel ./arch/arm64/boot/Image -append 'earlyprintk=serial,ttyAMA0,115200 console=ttyAMA0 psmouse.proto=exps "virtme_stty_con=rows 57 cols 105 iutf8" TERM=screen-256color-bce rootfstype=9p rootflags=version=9p2000.L,trans=virtio,access=any raid=noautodetect ro init=/bin/sh -- -c "mount -t tmpfs run /run;mkdir -p /run/virtme/guesttools;/bin/mount -n -t 9p -o ro,version=9p2000.L,trans=virtio,access=any virtme.guesttools /run/virtme/guesttools;exec /run/virtme/guesttools/virtme-init"' -s -S