All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: wei.liu2@citrix.com, Andrew Cooper <andrew.cooper3@citrix.com>,
	Amit Tomer <amittomer25@gmail.com>,
	Julien Grall <julien.grall@arm.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel@lists.xenproject.org, ian.jackson@citrix.com
Subject: Re: [PATCH 0/6] iomem cacheability
Date: Tue, 5 Mar 2019 22:45:52 +0000	[thread overview]
Message-ID: <CAF3u54Di61CufwzwJ35sqPrBRVt2ewrmR=siDHPWA8ur29db7Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1903051321390.17552@sstabellini-ThinkPad-X260>


[-- Attachment #1.1: Type: text/plain, Size: 7253 bytes --]

Sorry for the formatting.

On Tue, 5 Mar 2019, 21:24 Stefano Stabellini, <sstabellini@kernel.org>
wrote:

> On Sun, 3 Mar 2019, Amit Tomer wrote:
> > Hi,
> >
> > > This series introduces a cacheability parameter for the iomem option,
> so
> > > that we can map an iomem region into a guest as cacheable memory.
> > >
> > > Then, this series fixes the way Xen handles reserved memory regions on
> > > ARM: they should be mapped as normal memory, instead today they are
> > > treated as device memory.
> > >
> >
> > We tried testing this patch series on R-CAR platform but see following
> crash
> > when booting dom0 Linux.
>
> Thanks for testing! You might have found a real bug in the series. Could
> you please also attach the full device tree?
>

Looking at the stack trace, this is very likely due to the issue I pointed
out earlier on. I.e reserved-memory region should be described in the
memory nodes.

Cheers,


>
> > [    0.577777] bd20: 0000000000000000 ffff000008b27fa0
> > ffffffffffffffff ffff000008b27000
> > [    0.585639] bd40: ffff00000804bd50 ffff000008959164
> > [    0.590565] [<ffff000008959164>] cma_init_reserved_areas+0x98/0x1d0
> > [    0.596876] [<ffff000008083a50>] do_one_initcall+0x38/0x120
> > [    0.602493] [<ffff000008940d04>] kernel_init_freeable+0x188/0x228
> > [    0.608628] [<ffff0000086a6288>] kernel_init+0x10/0x100
> > [    0.613898] [<ffff000008084c68>] ret_from_fork+0x10/0x18
> > [    0.619250] ---[ end trace c2041e247871a6ff ]---
> > [    0.623929] Unable to handle kernel paging request at virtual
> > address ffff7dffe55c0000
> > [    0.631880] Mem abort info:
> > [    0.634715]   Exception class = DABT (current EL), IL = 32 bits
> > [    0.640684]   SET = 0, FnV = 0
> > [    0.643786]   EA = 0, S1PTW = 0
> > [    0.646990] Data abort info:
> > [    0.649920]   ISV = 0, ISS = 0x00000006
> > [    0.653821]   CM = 0, WnR = 0
> > [    0.656834] swapper pgtable: 4k pages, 48-bit VAs, pgd =
> ffff000008b47000
> > [    0.663670] [ffff7dffe55c0000] *pgd=0000000700aef803,
> > *pud=0000000700af0803, *pmd=0000000000000000
> > [    0.672652] Internal error: Oops: 96000006 [#1] PREEMPT SMP
> > [    0.678259] Modules linked in:
> > [    0.681371] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W
> > 4.14.50-yocto-standard #1
> > [    0.689923] Hardware name: Renesas Salvator-X board based on
> > r8a7795 ES2.0+ (DT)
> > [    0.697355] task: ffff80001e910000 task.stack: ffff000008048000
> > [    0.703317] PC is at cma_init_reserved_areas+0xbc/0x1d0
> > [    0.708587] LR is at cma_init_reserved_areas+0x94/0x1d0
> > [    0.713862] pc : [<ffff000008959188>] lr : [<ffff000008959160>]
> > pstate: 60000045
> > [    0.721287] sp : ffff00000804bd50
> > [    0.724657] x29: ffff00000804bd50 x28: ffff000008a88a28
> > [    0.730013] x27: 0000000000057000 x26: ffff000008994040
> > [    0.735370] x25: ffff000008b27fa0 x24: ffff000008b27000
> > [    0.740727] x23: ffff7e0000000000 x22: ffff0000088ed000
> > [    0.746084] x21: 0000000000000000 x20: 0000000000000000
> > [    0.751440] x19: 0000000000000004 x18: 0000000000000000
> > [    0.756797] x17: 0000000000000001 x16: 00000000deadbeef
> > [    0.762154] x15: 0000000000000000 x14: 0000000000000400
> > [    0.767511] x13: 0000000000000400 x12: 0000000000000000
> > [    0.772872] x11: 0000000000000000 x10: 0000000000000002
> > [    0.778224] x9 : 0000000000000000 x8 : ffff80001e945800
> > [    0.783586] x7 : 0000000000000000 x6 : ffff000008b24868
> > [    0.788938] x5 : ffff000008b24868 x4 : 0000000000000000
> > [    0.794295] x3 : 0000000000000780 x2 : 0000000700000000
> > [    0.799652] x1 : ffff000008a88a28 x0 : ffffffffe55c0000
> > [    0.805010] Process swapper/0 (pid: 1, stack limit =
> 0xffff000008048000)
> > [    0.811747] Call trace:
> > [    0.814254] Exception stack(0xffff00000804bc10 to 0xffff00000804bd50)
> > [    0.820734] bc00:
> > ffffffffe55c0000 ffff000008a88a28
> > [    0.828598] bc20: 0000000700000000 0000000000000780
> > 0000000000000000 ffff000008b24868
> > [    0.836460] bc40: ffff000008b24868 0000000000000000
> > ffff80001e945800 0000000000000000
> > [    0.844322] bc60: 0000000000000002 0000000000000000
> > 0000000000000000 0000000000000400
> > [    0.852184] bc80: 0000000000000400 0000000000000000
> > 00000000deadbeef 0000000000000001
> > [    0.860047] bca0: 0000000000000000 0000000000000004
> > 0000000000000000 0000000000000000
> > [    0.867910] bcc0: ffff0000088ed000 ffff7e0000000000
> > ffff000008b27000 ffff000008b27fa0
> > [    0.875772] bce0: ffff000008994040 0000000000057000
> > ffff000008a88a28 ffff00000804bd50
> > [    0.883639] bd00: ffff000008959160 ffff00000804bd50
> > ffff000008959188 0000000060000045
> > [    0.891497] bd20: 0000000000000000 ffff000008b27fa0
> > ffffffffffffffff ffff000008b27000
> > [    0.899359] bd40: ffff00000804bd50 ffff000008959188
> > [    0.904285] [<ffff000008959188>] cma_init_reserved_areas+0xbc/0x1d0
> > [    0.910592] [<ffff000008083a50>] do_one_initcall+0x38/0x120
> > [    0.916209] [<ffff000008940d04>] kernel_init_freeable+0x188/0x228
> > [    0.922343] [<ffff0000086a6288>] kernel_init+0x10/0x100
> > [    0.927613] [<ffff000008084c68>] ret_from_fork+0x10/0x18
> > [    0.932975] Code: f94262c0 aa0103fc cb803360 d37ae400 (f8776800)
> > [    0.939104] ---[ end trace c2041e247871a700 ]---
> > [    0.943800] Kernel panic - not syncing: Attempted to kill init!
> > exitcode=0x0000000b
> > [    0.943800]
> > [    0.953021] SMP: stopping secondary CPUs
> > [    0.957009] ---[ end Kernel panic - not syncing: Attempted to kill
> > init! exitcode=0x0000000b
> >
> > Below is how reserved node looks like:
> >
> >          reserved-memory {
> >                  #address-cells = <2>;
> >                  #size-cells = <2>;
> >                  ranges;
> >
> >                  /* device specific region for Lossy Decompression */
> >                  lossy_decompress: linux,lossy_decompress@54000000 {
> >                          no-map;
> >                          reg = <0x00000000 0x54000000 0x0 0x03000000>;
> >                  };
> >
> >                  /* For Audio DSP */
> >                  adsp_reserved: linux,adsp@57000000 {
> >                          compatible = "shared-dma-pool";
> >                          reusable;
> >                          reg = <0x00000000 0x57000000 0x0 0x01000000>;
> >                  };
> >
> >                  /* global autoconfigured region for contiguous
> allocations */
> >                  linux,cma@58000000 {
> >                          compatible = "shared-dma-pool";
> >                          reusable;
> >                          reg = <0x00000000 0x58000000 0x0 0x18000000>;
> >                          linux,cma-default;
> >                  };
> >
> >                  /* device specific region for contiguous allocations */
> >                  mmp_reserved: linux,multimedia@70000000 {
> >                          compatible = "shared-dma-pool";
> >                          reusable;
> >                          reg = <0x00000000 0x70000000 0x0 0x10000000>;
> >                  };
> >          };
> >
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel

[-- Attachment #1.2: Type: text/html, Size: 9300 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-03-05 22:46 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 23:06 [PATCH 0/6] iomem cacheability Stefano Stabellini
2019-02-26 23:07 ` [PATCH 1/6] xen: extend XEN_DOMCTL_memory_mapping to handle cacheability Stefano Stabellini
2019-02-26 23:18   ` Julien Grall
2019-04-20  0:02     ` Stefano Stabellini
2019-04-20  0:02       ` [Xen-devel] " Stefano Stabellini
2019-04-21 17:32       ` Julien Grall
2019-04-21 17:32         ` [Xen-devel] " Julien Grall
2019-04-22 21:59         ` Stefano Stabellini
2019-04-22 21:59           ` [Xen-devel] " Stefano Stabellini
2019-04-24 10:42           ` Julien Grall
2019-04-24 10:42             ` [Xen-devel] " Julien Grall
2019-02-27 10:34   ` Jan Beulich
2019-04-17 21:12     ` Stefano Stabellini
2019-04-17 21:12       ` [Xen-devel] " Stefano Stabellini
2019-04-17 21:25       ` Julien Grall
2019-04-17 21:25         ` [Xen-devel] " Julien Grall
2019-04-17 21:55         ` Stefano Stabellini
2019-04-17 21:55           ` [Xen-devel] " Stefano Stabellini
2019-04-25 10:41       ` Jan Beulich
2019-04-25 10:41         ` [Xen-devel] " Jan Beulich
2019-04-25 22:31         ` Stefano Stabellini
2019-04-25 22:31           ` [Xen-devel] " Stefano Stabellini
2019-04-26  7:12           ` Jan Beulich
2019-04-26  7:12             ` [Xen-devel] " Jan Beulich
2019-02-27 19:28   ` Julien Grall
2019-04-19 23:20     ` Stefano Stabellini
2019-04-19 23:20       ` [Xen-devel] " Stefano Stabellini
2019-04-21 17:14       ` Julien Grall
2019-04-21 17:14         ` [Xen-devel] " Julien Grall
2019-04-22 17:33         ` Stefano Stabellini
2019-04-22 17:33           ` [Xen-devel] " Stefano Stabellini
2019-04-22 17:42           ` Julien Grall
2019-04-22 17:42             ` [Xen-devel] " Julien Grall
2019-02-27 21:02   ` Julien Grall
2019-02-26 23:07 ` [PATCH 2/6] libxc: xc_domain_memory_mapping, " Stefano Stabellini
2019-02-26 23:07 ` [PATCH 3/6] libxl/xl: add cacheability option to iomem Stefano Stabellini
2019-02-27 20:02   ` Julien Grall
2019-04-19 23:13     ` Stefano Stabellini
2019-04-19 23:13       ` [Xen-devel] " Stefano Stabellini
2019-02-26 23:07 ` [PATCH 4/6] xen/arm: keep track of reserved-memory regions Stefano Stabellini
2019-02-28 14:38   ` Julien Grall
2019-02-26 23:07 ` [PATCH 5/6] xen/arm: map reserved-memory regions as normal memory in dom0 Stefano Stabellini
2019-02-26 23:45   ` Julien Grall
2019-04-22 22:42     ` Stefano Stabellini
2019-04-22 22:42       ` [Xen-devel] " Stefano Stabellini
2019-04-23  8:09       ` Julien Grall
2019-04-23  8:09         ` [Xen-devel] " Julien Grall
2019-04-23 17:32         ` Stefano Stabellini
2019-04-23 17:32           ` [Xen-devel] " Stefano Stabellini
2019-04-23 18:37           ` Julien Grall
2019-04-23 18:37             ` [Xen-devel] " Julien Grall
2019-04-23 21:34             ` Stefano Stabellini
2019-04-23 21:34               ` [Xen-devel] " Stefano Stabellini
2019-02-26 23:07 ` [PATCH 6/6] xen/docs: how to map a page between dom0 and domU using iomem Stefano Stabellini
2019-03-03 17:20 ` [PATCH 0/6] iomem cacheability Amit Tomer
2019-03-05 21:22   ` Stefano Stabellini
2019-03-05 22:45     ` Julien Grall [this message]
2019-03-06 11:46       ` Amit Tomer
2019-03-06 22:42         ` Stefano Stabellini
2019-03-06 22:59           ` Julien Grall
2019-03-07  8:42             ` Amit Tomer
2019-03-07 10:04               ` Julien Grall
2019-03-07 21:24                 ` Stefano Stabellini
2019-03-08 10:10                   ` Amit Tomer
2019-03-08 16:37                     ` Julien Grall
2019-03-08 17:44                       ` Amit Tomer
2019-03-06 11:30     ` Amit Tomer

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='CAF3u54Di61CufwzwJ35sqPrBRVt2ewrmR=siDHPWA8ur29db7Q@mail.gmail.com' \
    --to=julien.grall@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=amittomer25@gmail.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --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.