linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Li Yang <leoli@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Zhao Chenhui <b26998@freescale.com>
Subject: Re: [PATCH 3/4] fsl_msi: enable msi sharing through AMP OSes
Date: Mon, 19 Apr 2010 12:34:09 +1000	[thread overview]
Message-ID: <1271644449.14835.35.camel@concordia> (raw)
In-Reply-To: <1271403278-30091-3-git-send-email-leoli@freescale.com>

[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]

On Fri, 2010-04-16 at 15:34 +0800, Li Yang wrote:
> From: Zhao Chenhui <b26998@freescale.com>
> 
> Make a single PCIe MSI bank shareable through CAMP OSes. The number of
> MSI used by each core can be configured by dts file.
> 
> Signed-off-by: Zhao Chenhui <b26998@freescale.com>
> Signed-off-by: Li Yang <leoli@freescale.com>
> ---
>  arch/powerpc/sysdev/fsl_msi.c    |    8 +++++++-
>  arch/powerpc/sysdev/msi_bitmap.c |    4 ++--
>  2 files changed, 9 insertions(+), 3 deletions(-)
..
> diff --git a/arch/powerpc/sysdev/msi_bitmap.c b/arch/powerpc/sysdev/msi_bitmap.c
> index 5a32cbe..b41db96 100644
> --- a/arch/powerpc/sysdev/msi_bitmap.c
> +++ b/arch/powerpc/sysdev/msi_bitmap.c
> @@ -95,8 +95,8 @@ int msi_bitmap_reserve_dt_hwirqs(struct msi_bitmap *bmp)
>  	/* Format is: (<u32 start> <u32 count>)+ */
>  	len /= 2 * sizeof(u32);
>  	for (i = 0; i < len; i++, p += 2) {
> -		for (j = 0; j < *(p + 1); j++)
> -			bitmap_release_region(bmp->bitmap, *p + j, 0);
> +		for (j = *p; j < *(p + 1); j++)
> +			bitmap_release_region(bmp->bitmap, j, 0);
>  	}
>  
>  	spin_unlock(&bmp->lock);

This looks like a bug fix to the msi bitmap code, is it not? Please
split it into a separate commit with an explanatory changelog.

cheers



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2010-04-19  2:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16  7:34 [PATCH 1/4] fsl_msi: fix the conflict of virt_msir's chip_data Li Yang
2010-04-16  7:34 ` [PATCH 2/4] fsl_msi: enable msi allocation in all banks Li Yang
2010-04-16  7:34   ` [PATCH 3/4] fsl_msi: enable msi sharing through AMP OSes Li Yang
2010-04-16  7:34     ` [PATCH 4/4] mpc8572ds: change camp dtses for MSI sharing Li Yang
2010-04-19  2:34     ` Michael Ellerman [this message]
2010-04-19  6:23       ` [PATCH 3/4] fsl_msi: enable msi sharing through AMP OSes Li Yang
2010-04-19  2:46   ` [PATCH 2/4] fsl_msi: enable msi allocation in all banks Michael Ellerman
2010-04-19  6:46     ` Li Yang
2010-04-19  2:40 ` [PATCH 1/4] fsl_msi: fix the conflict of virt_msir's chip_data Michael Ellerman
2010-04-19  4:50   ` Li Yang
2010-04-19 12:19     ` Kumar Gala
2010-04-20  3:10       ` Li Yang

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=1271644449.14835.35.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=b26998@freescale.com \
    --cc=leoli@freescale.com \
    --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).