From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel@lists.xenproject.org, manish.jaggi@caviumnetworks.com,
stefano.stabellini@citrix.com, tim@xen.org
Subject: Re: [PATCH v4 7/8] xen/iommu: smmu: Advertise when the SMMU support coherent table walk
Date: Mon, 2 Mar 2015 16:24:07 +0000 [thread overview]
Message-ID: <1425313447.24959.1.camel@citrix.com> (raw)
In-Reply-To: <54F48059.6000604@linaro.org>
On Mon, 2015-03-02 at 15:23 +0000, Julien Grall wrote:
> >> + /* Find the last SMMU added and retrieve its features. */
> >
> > This comment no longer applies, I think?
>
> I think it's useful to have a comment explaining why we are retrieving
> the SMMU.
Sorry, I initially misread things and thought this was processing all
smmus.
>
> >> + spin_lock(&arm_smmu_devices_lock);
> >> + list_for_each_entry(smmu, &arm_smmu_devices, list) {
> >> + if (smmu->dev == &dev->dev)
> >> + goto found;
> >
> > Please try and avoid goto. In this case I think
> > {
> > platform_features &= smmu->features;
> > break;
> > }
>
> I though about this solution but it doesn't say if for some reason we
> miss to find the SMMU.
I think that's fine in this context. If it isn't on the list at this
point it might as well not exist and/or there would have been an error
somewhere else already.
> >
> > within the if would be fine, combined with dropping the following BUG().
> >
> > Alternatively you might prefer to provide a helper function to lookup an
> > smmu by &dev->dev.
>
> I would like to keep the BUG(). Because this would be a mistake to not
> find the last SMMU added.
Sounds more like an ASSERT to me.
> I will move to an helper function.
Sure.
next prev parent reply other threads:[~2015-03-02 16:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 18:52 [PATCH v4 0/8] xen/arm: Resync the SMMU driver with the Linux one Julien Grall
2015-02-25 18:52 ` [PATCH v4 1/8] xen/iommu: arm: Remove temporary the SMMU driver Julien Grall
2015-02-25 18:52 ` [PATCH v4 2/8] xen/arm: Introduce a generic way to describe device Julien Grall
2015-03-30 9:51 ` Manish Jaggi
2015-02-25 18:52 ` [PATCH v4 3/8] xen/iommu: Consolidate device assignment ops into a single set Julien Grall
2015-02-25 18:52 ` [PATCH v4 4/8] xen/arm: Describe devices supported by a driver with dt_device_match Julien Grall
2015-02-25 18:52 ` [PATCH v4 5/8] xen/iommu: arm: Import the SMMU driver from Linux Julien Grall
2015-02-25 18:52 ` [PATCH v4 6/8] xen/iommu: smmu: Add Xen specific code to be able to use the driver Julien Grall
2015-03-02 7:03 ` Manish Jaggi
2015-03-04 2:08 ` Manish Jaggi
2015-03-02 13:17 ` Ian Campbell
2015-03-02 13:45 ` Julien Grall
2015-03-02 13:54 ` Ian Campbell
2015-02-25 18:53 ` [PATCH v4 7/8] xen/iommu: smmu: Advertise when the SMMU support coherent table walk Julien Grall
2015-03-02 13:10 ` Ian Campbell
2015-03-02 15:23 ` Julien Grall
2015-03-02 16:24 ` Ian Campbell [this message]
2015-02-25 18:53 ` [PATCH v4 8/8] DO NOT APPLY xen/iommu: smmu: Changes to support Midway SMMU Julien Grall
2015-03-02 14:47 ` [PATCH v4 0/8] xen/arm: Resync the SMMU driver with the Linux one 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=1425313447.24959.1.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=manish.jaggi@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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.