xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: julien.grall@linaro.org, tim@xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v4 5/6] xen: arm: map child MMIO and IRQs to dom0 for PCI bus DT nodes.
Date: Fri, 26 Jun 2015 19:56:33 +0200	[thread overview]
Message-ID: <558D9251.2070703@citrix.com> (raw)
In-Reply-To: <1431084420-14372-5-git-send-email-ian.campbell@citrix.com>

Hi Ian,

NIT in the title: The final point is not necessary

On 08/05/2015 13:26, Ian Campbell wrote:
> +static int map_device_children(struct domain *d,
> +                               const struct dt_device_node *dev)
> +{
> +    bool_t need_mapping = !dt_device_for_passthrough(dev);
> +    int ret;
> +
> +    if ( dt_device_type_is_equal(dev, "pci") )
> +    {
> +        DPRINT("Mapping children of %s to guest\n", dt_node_full_name(dev));
> +
> +        /*
> +         * We need to handle IRQs even if !need_mapping in order to
> +         * setup the domain's permissions on the device's IRQs, such
> +         * that it can pass them through to other domains.
> +         */
> +         ret = dt_for_each_irq_map(dev, &map_interrupt_to_domain, d);
> +         if ( ret < 0 )
> +             return ret;
> +
> +         if ( need_mapping )
> +         {

I forgot to mention in the previous version that we need to give iomem 
permission to the guest. Otherwise DOM0 won't be able to map the BAR 
into the guest.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-06-26 17:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 11:26 [PATCH v3 0/6] xen: arm: Parse PCI DT nodes' ranges and interrupt-map Ian Campbell
2015-05-08 11:26 ` [PATCH v4 1/6] xen: dt: add dt_for_each_irq_map helper Ian Campbell
2015-06-26 17:47   ` Julien Grall
2015-07-03 14:16     ` Ian Campbell
2015-07-03 15:15       ` Julien Grall
2015-07-03 15:28         ` Ian Campbell
2015-05-08 11:26 ` [PATCH v4 2/6] xen: dt: add dt_for_each_range helper Ian Campbell
2015-05-08 11:26 ` [PATCH v4 3/6] xen: arm: slightly refactor gic DT node creation for domain 0 Ian Campbell
2015-05-08 16:21   ` Ian Campbell
2015-05-08 11:26 ` [PATCH v4 4/6] xen: arm: drop redundant extra call to vgic_reserve_virq Ian Campbell
2015-06-26 17:49   ` Julien Grall
2015-05-08 11:26 ` [PATCH v4 5/6] xen: arm: map child MMIO and IRQs to dom0 for PCI bus DT nodes Ian Campbell
2015-06-26 17:56   ` Julien Grall [this message]
2015-07-03 10:59     ` Ian Campbell
2015-07-03 11:26       ` Julien Grall
2015-05-08 11:27 ` [PATCH v4 6/6] xen: arm: Import of_bus PCI entry from Linux (as a dt_bus entry) Ian Campbell
2015-06-26 18:08   ` Julien Grall
2015-07-03 10:47     ` Ian Campbell
2015-07-03 10:56       ` Ian Campbell
2015-07-03 11:24         ` Julien Grall
2015-07-03 11:30           ` Ian Campbell
2015-05-08 11:41 ` [PATCH v3 0/6] xen: arm: Parse PCI DT nodes' ranges and interrupt-map 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=558D9251.2070703@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).