All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, xen-devel@lists.xen.org
Cc: edgar.iglesias@xilinx.com, nd@arm.com, sstabellini@kernel.org
Subject: Re: [PATCH v1 0/1] xen/arm: zynqmp: Disable PCIe
Date: Mon, 31 Jul 2017 23:11:39 +0100	[thread overview]
Message-ID: <217597b3-e7c4-1666-b21e-36ca18cd6ca7@arm.com> (raw)
In-Reply-To: <1501529825-16326-1-git-send-email-edgar.iglesias@gmail.com>



On 31/07/2017 20:37, Edgar E. Iglesias wrote:
> From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
>
> Hi,

Hi Edgar,


> We're seeing panics in dom0 with PCIe enabled due to what seems
> to be wrongly created mappings by Xen. With older kernels we
> didn't see the panics but PCIe wasn't functional in dom0.
>
> This disables the PCIe nodes on the ZynqMP until Xen/ARM gets
> more PCIe support.

I feel a bit sad to ack a patch disabling PCIe in the ZynqMP.

Before doing that. Can you describe what is the exact problem with Xen? 
It might be possible that we don't parse correctly the device-tree.

Cheers,

-- 
Julien Grall

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

  parent reply	other threads:[~2017-07-31 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 19:37 [PATCH v1 0/1] xen/arm: zynqmp: Disable PCIe Edgar E. Iglesias
2017-07-31 19:37 ` [PATCH v1 1/1] xen/arm: Disable PCIe on the ZynqMP Edgar E. Iglesias
2017-07-31 22:11 ` Julien Grall [this message]
2017-08-01  0:01   ` [PATCH v1 0/1] xen/arm: zynqmp: Disable PCIe Edgar E. Iglesias
2017-08-01 20:26     ` Stefano Stabellini

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=217597b3-e7c4-1666-b21e-36ca18cd6ca7@arm.com \
    --to=julien.grall@arm.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=nd@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.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.