All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Clark Laughlin <clark.laughlin@linaro.org>,
	Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Subject: [PATCH 0/4 for-4.5] xen: arm: xgene bug fixes + support for McDivitt
Date: Tue, 18 Nov 2014 16:44:05 +0000	[thread overview]
Message-ID: <1416329045.17982.27.camel@citrix.com> (raw)

These patches:

      * fix up an off by one bug in the xgene mapping of additional PCI
        bus resources, which would cause an additional extra page to be
        mapped
      * correct the size of the mapped regions to match the docs
      * adds support for the other 4 PCI buses on the chip, which
        enables mcdivitt and presumably most other Xgene based platforms
        which uses PCI buses other than pcie0.
      * adds earlyprintk for the mcdivitt platform

McDivitt is the X-Gene based HP Moonshot cartridge (McDivitt is the code
name, I think the product is called m400, not quite sure).

Other than the bug fixes I'd like to see the mcdivitt support
(specifically the "other 4 PCI buses" one) in 4.5 because Moonshot is an
interesting and exciting platform for arm64. It is also being used for
ongoing work on Xen on ARM on Openstack in Linaro. The earlyprintk patch
is totally harmless unless it's explicitly enabled at compile time, IMHO
if we are taking the rest we may as well throw it in...

The risk here is that we break the existing support for the Mustang
platform, which would be the most likely failure case for the second
patch. I've tested these on a Mustang, including firing up a PCI NIC
device. The new mappings are a superset of the existing ones so the
potential for breakage should be quite small.

I've also successfully tested on a McDivitt.

Ian.

             reply	other threads:[~2014-11-18 16:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 16:44 Ian Campbell [this message]
2014-11-18 16:44 ` [PATCH for-4.5 1/4] xen: arm: Add earlyprintk for McDivitt Ian Campbell
2014-11-18 16:59   ` Julien Grall
2014-11-19  9:54     ` Ian Campbell
2014-11-19 10:02       ` Julien Grall
2014-11-18 16:44 ` [PATCH for-4.5 2/4] xen: arm: correct off by one in xgene-storm's map_one_mmio Ian Campbell
2014-11-18 17:01   ` Julien Grall
2014-11-19  9:54     ` Ian Campbell
2014-11-19 21:11   ` Konrad Rzeszutek Wilk
2014-11-18 16:44 ` [PATCH for-4.5 3/4] xen: arm: correct specific mappings for PCIE0 on X-Gene Ian Campbell
2014-11-18 17:04   ` Julien Grall
2014-11-18 16:44 ` [PATCH for-4.5 4/4] xen: arm: Support the other 4 PCI buses on Xgene Ian Campbell
2014-11-18 17:15   ` Julien Grall
2014-11-19  9:56     ` Ian Campbell
2014-11-19 10:06       ` Julien Grall
2014-11-19 10:18         ` Ian Campbell
2014-11-19 10:30           ` Julien Grall
2014-11-18 16:51 ` [PATCH 0/4 for-4.5] xen: arm: xgene bug fixes + support for McDivitt Ian Campbell
2014-11-19 21:18   ` Konrad Rzeszutek Wilk
2014-11-20  9:02     ` Ian Campbell

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=1416329045.17982.27.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=clark.laughlin@linaro.org \
    --cc=julien.grall@linaro.org \
    --cc=pranavkumar@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.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.