From: Scott Wood <scottwood@freescale.com>
To: Zhao Qiang-B45475 <qiang.zhao@freescale.com>
Cc: Laura Abbott <labbott@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
Xie Xiaobo-R63061 <X.Xie@freescale.com>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
Li Yang-Leo-R58472 <LeoLi@freescale.com>,
"paulus@samba.org" <paulus@samba.org>
Subject: Re: [PATCH v6 3/3] qe_common: add qe_muram_ functions to manage muram
Date: Tue, 25 Aug 2015 20:52:59 -0500 [thread overview]
Message-ID: <1440553979.16577.89.camel@freescale.com> (raw)
In-Reply-To: <SN1PR0301MB15500F5D6D59CB344A8BF9FE9B600@SN1PR0301MB1550.namprd03.prod.outlook.com>
On Tue, 2015-08-25 at 20:49 -0500, Zhao Qiang-B45475 wrote:
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Wednesday, August 26, 2015 12:23 AM
> > To: Zhao Qiang-B45475
> > Cc: Laura Abbott; linux-kernel@vger.kernel.org; linuxppc-
> > dev@lists.ozlabs.org; lauraa@codeaurora.org; Xie Xiaobo-R63061;
> > benh@kernel.crashing.org; Li Yang-Leo-R58472; paulus@samba.org
> > Subject: Re: [PATCH v6 3/3] qe_common: add qe_muram_ functions to manage
> > muram
> >
> > On Tue, 2015-08-25 at 02:19 -0500, Zhao Qiang-B45475 wrote:
> > > On 08/25/2015 12:15 PM, Laura Abbott wrote
> > > > -----Original Message-----
> > > > From: Laura Abbott [mailto:labbott@redhat.com]
> > > > Sent: Tuesday, August 25, 2015 12:15 PM
> > > > To: Zhao Qiang-B45475; Wood Scott-B07421
> > > > Cc: linux-kernel@vger.kernel.org; linuxppc-dev@lists.ozlabs.org;
> > > > lauraa@codeaurora.org; Xie Xiaobo-R63061; benh@kernel.crashing.org;
> > > > Li Yang-Leo-R58472; paulus@samba.org
> > > > Subject: Re: [PATCH v6 3/3] qe_common: add qe_muram_ functions to
> > > > manage muram
> > > >
> > > > On 08/24/2015 08:03 PM, Zhao Qiang wrote:
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Laura Abbott [mailto:labbott@redhat.com]
> > > > > > Sent: Tuesday, August 25, 2015 7:32 AM
> > > > > > To: Zhao Qiang-B45475; Wood Scott-B07421
> > > > > > Cc: linux-kernel@vger.kernel.org; linuxppc-dev@lists.ozlabs.org;
> > > > > > lauraa@codeaurora.org; Xie Xiaobo-R63061;
> > > > > > benh@kernel.crashing.org; Li Yang-Leo-R58472; paulus@samba.org
> > > > > > Subject: Re: [PATCH v6 3/3] qe_common: add qe_muram_ functions
> > > > > > to manage muram
> > > > > >
> > > > > > There doesn't seem to be a check for allocation failure from the
> > > > > > gen_alloc.
> > > > >
> > > > > gen_pool_alloc will return 0 if there is error, but if the address
> > > > > returned is just 0x0, it can't distinguish it is address or error.
> > > > >
> > > >
> > > > Yes, that's a bad limitation of gen_pool. Maybe one day that will
> > > > get fixed.
> > > > In a previous out of tree driver, I worked around this by offsetting
> > > > the gen_pool_add by a constant so any return value was non-zero and
> > > > out of memory was zero and then subtracting the constant off of the
> > return value.
> > > > Not sure if that's better or worse than just fixing gen_alloc.
> > > >
> > >
> > > The workaround works for non alignment allocation, but for alignment
> > > allocation, It need to align bytes to addr 0, offsetting the
> > > gen_pool_add maybe make wrong alignment
> >
> > It would work if the offset you add is a multiple of the size of muram.
>
> The QE apps ask different bytes alignment for different use due to hardware
> restriction.
> Why don’t we deal with it in gen_pool_alloc func instead of a workaround?
> It is more reasonable.
>
Sure, fixing gen_pool_alloc would be better if you're willing to do it, and
are careful not to break existing users. I was just pointing out that the
workaround isn't totally incompatible with alignment.
-Scott
next prev parent reply other threads:[~2015-08-26 1:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 9:31 [PATCH v6 1/3] genalloc:support memory-allocation with bytes-alignment to genalloc Zhao Qiang
2015-08-24 9:31 ` [PATCH v6 2/3] QE: Move QE from arch/powerpc to drivers/soc Zhao Qiang
2015-08-24 9:31 ` [PATCH v6 3/3] qe_common: add qe_muram_ functions to manage muram Zhao Qiang
2015-08-24 16:34 ` Scott Wood
2015-08-25 7:52 ` Zhao Qiang
2015-08-25 7:52 ` Zhao Qiang
2015-08-25 16:25 ` Scott Wood
2015-08-24 23:32 ` Laura Abbott
2015-08-25 3:03 ` Zhao Qiang
2015-08-25 3:03 ` Zhao Qiang
2015-08-25 4:14 ` Laura Abbott
2015-08-25 7:19 ` Zhao Qiang
2015-08-25 7:19 ` Zhao Qiang
2015-08-25 16:22 ` Scott Wood
2015-08-26 1:49 ` Zhao Qiang
2015-08-26 1:49 ` Zhao Qiang
2015-08-26 1:52 ` Scott Wood [this message]
2015-08-24 23:10 ` [PATCH v6 1/3] genalloc:support memory-allocation with bytes-alignment to genalloc Laura Abbott
2015-08-25 2:40 ` Zhao Qiang
2015-08-25 2:40 ` Zhao Qiang
2015-08-25 4:01 ` Laura Abbott
2015-08-25 8:09 ` Zhao Qiang
2015-08-25 8:09 ` Zhao Qiang
2015-08-25 16:28 ` Scott Wood
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=1440553979.16577.89.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=LeoLi@freescale.com \
--cc=X.Xie@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=labbott@redhat.com \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=qiang.zhao@freescale.com \
/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.