linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
	linuxppc-dev@ozlabs.org, imunsie@au1.ibm.com, dja@axtens.net
Subject: Re: [PATCH] cxl: sparse: add __iomem annotations in vphb.c
Date: Fri, 30 Oct 2015 14:07:51 +0100	[thread overview]
Message-ID: <6848216.pocJKKsE8F@wuerfel> (raw)
In-Reply-To: <1446002979-29728-1-git-send-email-andrew.donnellan@au1.ibm.com>

On Wednesday 28 October 2015 14:29:39 Andrew Donnellan wrote:
> --- a/drivers/misc/cxl/vphb.c
> +++ b/drivers/misc/cxl/vphb.c
> @@ -128,7 +128,7 @@ static int cxl_pcie_config_info(struct pci_bus *bus, unsigned int devfn,
>                 return PCIBIOS_BAD_REGISTER_NUMBER;
>         addr = cxl_pcie_cfg_addr(phb, bus->number, devfn, offset);
>  
> -       *ioaddr = (void *)(addr & ~0x3ULL);
> +       *ioaddr = (void __iomem *)(addr & ~0x3ULL);
>         *shift = ((addr & 0x3) * 8);
>         switch (len) {
>         case 1:

It would be nice to change the return value of cxl_pcie_cfg_addr to
'void __iomem *' as well, and only do the cast (back and forth) inside 
the calculation, to make it clear that the input type is the same as the
output. Perhaps use a static inline function to wrap it.

> @@ -249,7 +249,7 @@ int cxl_pci_vphb_add(struct cxl_afu *afu)
>         /* Setup the PHB using arch provided callback */
>         phb->ops = &cxl_pcie_pci_ops;
>         phb->cfg_addr = afu->afu_desc_mmio + afu->crs_offset;
> -       phb->cfg_data = (void *)(u64)afu->crs_len;
> +       phb->cfg_data = (void __iomem *)afu->crs_len;
>         phb->private_data = afu;
>         phb->controller_ops = cxl_pci_controller_ops;


This needs a comment to explain why this is correct. I've tried to find it
out by reading the code and could not find any explanation. Also, you
need to cast to an intermediate (uintptr_t) type, as directly converting
a u64 to a pointer of any sort is nonportable, and it would be good to
at least allow compile-testing this code on other architectures.

I suspect that 'phb->cfg_data' is used in this driver in a way that is
incompatible with the other uses of the same variable. Maybe you can
replace it with something like

	union {
		void __iomem *cfg_data;
		u64 cxl_cfg_offset;
	};

to make it clear that in this driver it is used as an offset rather than
a pointer.

	Arnd

  parent reply	other threads:[~2015-10-30 13:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  3:29 [PATCH] cxl: sparse: add __iomem annotations in vphb.c Andrew Donnellan
2015-10-28  3:49 ` Ian Munsie
2015-10-30 13:07 ` Arnd Bergmann [this message]
2015-11-02  4:57   ` Andrew Donnellan
2015-11-03  9:09 ` Michael Ellerman
2015-11-04  6:17   ` Andrew Donnellan
2015-12-08  6:30     ` Andrew Donnellan
2015-12-09  1:00       ` Michael Neuling
2015-12-09  1:06         ` Michael Ellerman

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=6848216.pocJKKsE8F@wuerfel \
    --to=arnd@arndb.de \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=dja@axtens.net \
    --cc=imunsie@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxppc-dev@ozlabs.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).