linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
	gwshan@linux.vnet.ibm.com, paulus@samba.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH resend] powernv/iommu: disable IOMMU bypass with param iommu=nobypass
Date: Fri, 23 Jan 2015 14:02:56 +1100	[thread overview]
Message-ID: <1421982176.24984.6.camel@ellerman.id.au> (raw)
In-Reply-To: <1421853832-32533-1-git-send-email-cascardo@linux.vnet.ibm.com>

On Wed, 2015-01-21 at 13:23 -0200, Thadeu Lima de Souza Cascardo wrote:
> diff --git a/arch/powerpc/platforms/powernv/pci-ioda.c b/arch/powerpc/platforms/powernv/pci-ioda.c
> index fac88ed..f942a19 100644
> --- a/arch/powerpc/platforms/powernv/pci-ioda.c
> +++ b/arch/powerpc/platforms/powernv/pci-ioda.c
> @@ -75,6 +75,27 @@ static void pe_level_printk(const struct pnv_ioda_pe *pe, const char *level,
>  #define pe_info(pe, fmt, ...)					\
>  	pe_level_printk(pe, KERN_INFO, fmt, ##__VA_ARGS__)
>  
> +static bool pnv_iommu_bypass_disabled __read_mostly;
> +
> +static int __init iommu_setup(char *str)
> +{
> +	if (!str)
> +		return -EINVAL;
> +	while (*str) {
> +		if (!strncmp(str, "nobypass", 8)) {
> +			pnv_iommu_bypass_disabled = true;
> +			pr_info("PowerNV: IOMMU bypass window disabled.\n");

I added a break here.

> +		}
> +		str += strcspn(str, ",");
> +		if (*str == ',')
> +			str++;
> +	}
> +
> +	return 0;
> +}
> +
> +early_param("iommu", iommu_setup);

cheers

      parent reply	other threads:[~2015-01-23  3:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 15:23 [PATCH resend] powernv/iommu: disable IOMMU bypass with param iommu=nobypass Thadeu Lima de Souza Cascardo
2015-01-22  1:05 ` Michael Ellerman
2015-01-22 10:54   ` cascardo
2015-01-23  3:02 ` Michael Ellerman [this message]

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=1421982176.24984.6.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=cascardo@linux.vnet.ibm.com \
    --cc=corbet@lwn.net \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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).