Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Marc Zyngier <marc.zyngier@xxxxxxx>
Subject: Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
From: "Liuwenliang (Abbott Liu)" <liuwenliang@xxxxxxxxxx>
Date: Fri, 17 Nov 2017 07:18:45 +0000
Accept-language: en-US
Cc: "linux@xxxxxxxxxxxxxxx" <linux@xxxxxxxxxxxxxxx>, "aryabinin@xxxxxxxxxxxxx" <aryabinin@xxxxxxxxxxxxx>, "afzal.mohd.ma@xxxxxxxxx" <afzal.mohd.ma@xxxxxxxxx>, "f.fainelli@xxxxxxxxx" <f.fainelli@xxxxxxxxx>, "labbott@xxxxxxxxxx" <labbott@xxxxxxxxxx>, "kirill.shutemov@xxxxxxxxxxxxxxx" <kirill.shutemov@xxxxxxxxxxxxxxx>, "mhocko@xxxxxxxx" <mhocko@xxxxxxxx>, "cdall@xxxxxxxxxx" <cdall@xxxxxxxxxx>, "catalin.marinas@xxxxxxx" <catalin.marinas@xxxxxxx>, "akpm@xxxxxxxxxxxxxxxxxxxx" <akpm@xxxxxxxxxxxxxxxxxxxx>, "mawilcox@xxxxxxxxxxxxx" <mawilcox@xxxxxxxxxxxxx>, "tglx@xxxxxxxxxxxxx" <tglx@xxxxxxxxxxxxx>, "thgarnie@xxxxxxxxxx" <thgarnie@xxxxxxxxxx>, "keescook@xxxxxxxxxxxx" <keescook@xxxxxxxxxxxx>, "arnd@xxxxxxxx" <arnd@xxxxxxxx>, "vladimir.murzin@xxxxxxx" <vladimir.murzin@xxxxxxx>, "tixy@xxxxxxxxxx" <tixy@xxxxxxxxxx>, "ard.biesheuvel@xxxxxxxxxx" <ard.biesheuvel@xxxxxxxxxx>, "robin.murphy@xxxxxxx" <robin.murphy@xxxxxxx>, "mingo@xxxxxxxxxx" <mingo@xxxxxxxxxx>, "grygorii.strashko@xxxxxxxxxx" <grygorii.strashko@xxxxxxxxxx>, "glider@xxxxxxxxxx" <glider@xxxxxxxxxx>, "dvyukov@xxxxxxxxxx" <dvyukov@xxxxxxxxxx>, "opendmb@xxxxxxxxx" <opendmb@xxxxxxxxx>, "linux-arm-kernel@xxxxxxxxxxxxxxxxxxx" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "kasan-dev@xxxxxxxxxxxxxxxx" <kasan-dev@xxxxxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, Jiazhenghua <jiazhenghua@xxxxxxxxxx>, Dailei <dylix.dailei@xxxxxxxxxx>, Zengweilin <zengweilin@xxxxxxxxxx>, Heshaoliang <heshaoliang@xxxxxxxxxx>
In-reply-to: <87375eqobb.fsf@on-the-bus.cambridge.arm.com>
References: <20171011082227.20546-1-liuwenliang@huawei.com> <20171011082227.20546-2-liuwenliang@huawei.com> <227e2c6e-f479-849d-8942-1d5ff4ccd440@arm.com> <B8AC3E80E903784988AB3003E3E97330C0063172@dggemm510-mbs.china.huawei.com> <8e959f69-a578-793b-6c32-18b5b0cd08c2@arm.com> <B8AC3E80E903784988AB3003E3E97330C0063545@dggemm510-mbs.china.huawei.com> <87a7znsubp.fsf@on-the-bus.cambridge.arm.com> <B8AC3E80E903784988AB3003E3E97330C0063587@dggemm510-mbs.china.huawei.com> <bbf43f92-3d0c-940d-b66b-68f92eb9b282@arm.com> <B8AC3E80E903784988AB3003E3E97330C00635F3@dggemm510-mbs.china.huawei.com> <87po8ir1kg.fsf@on-the-bus.cambridge.arm.com> <B8AC3E80E903784988AB3003E3E97330C006371B@dggemm510-mbs.china.huawei.com> <87375eqobb.fsf@on-the-bus.cambridge.arm.com>

On 16/11/17  22:41 Marc Zyngier [mailto:marc.zyngier@xxxxxxx] wrote:
>No, it doesn't. It cannot work, because Cortex-A9 predates the invention
>of the 64bit accessor. I suspect that you are testing stuff in QEMU,
>which is giving you a SW model that always supports LPAE. I suggest you
>test this code on *real* HW, and not only on QEMU.

I am sorry. My test is fault. I only defined TTBR0 as __ACCESS_CP15_64,
but I don't use the definition TTBR0 as __ACCESS_CP15_64. 

Now I use the definition TTBR0 as __ACCESS_CP15_64 on CPU supporting
LPAE(vexpress_a9), I find it doesn't work and report undefined instruction error
when execute "mrrc" instruction.

So, you are right that 64bit accessor of TTBR0 cannot work on LPAE.

��.n������g����a����&ޖ)���)��h���&������梷�����Ǟ�m������)������^�����������v���O��zf������

Follow-Ups:
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Christoffer Dall

References:
- [PATCH 00/11] KASan for arm
  - From: Abbott Liu
- [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Abbott Liu
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Marc Zyngier
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Liuwenliang (Abbott Liu)
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Marc Zyngier
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Liuwenliang (Abbott Liu)
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Marc Zyngier
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Liuwenliang (Abbott Liu)
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Marc Zyngier
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Liuwenliang (Abbott Liu)
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Marc Zyngier
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Liuwenliang (Abbott Liu)
- Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
  - From: Marc Zyngier

Prev by Date: RE: [PATCH 12/16] nsproxy: convert nsproxy.count to refcount_t
Next by Date: Re: [RFC PATCH 1/2] mm: introduce MAP_FIXED_SAFE
Previous by thread: 答复: [PATCH 01/11] Initialize the mapping of KASan shadow memory
Next by thread: Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]