From: Laura Abbott <lauraa-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org> Cc: Catalin Marinas <Catalin.Marinas-5wv7dgnIgG8@public.gmane.org>, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, David Riley <davidriley-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>, "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>, Ritesh Harjani <ritesh.harjani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Subject: Re: [PATCHv2] arm64: Add atomic pool for non-coherent and CMA allocaitons. Date: Tue, 03 Jun 2014 17:30:18 -0700 [thread overview] Message-ID: <538E689A.3050109@codeaurora.org> (raw) In-Reply-To: <20140603132842.GI23149-5wv7dgnIgG8@public.gmane.org> On 6/3/2014 6:28 AM, Will Deacon wrote: > Hi Laura, > > On Mon, Jun 02, 2014 at 09:03:52PM +0100, Laura Abbott wrote: >> Neither CMA nor noncoherent allocations support atomic allocations. >> Add a dedicated atomic pool to support this. >> >> Change-Id: I46c8fdffe5e0687403d42b37643137c8cf344259 >> Signed-off-by: Laura Abbott <lauraa-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> >> --- >> >> v2: Various bug fixes pointed out by David and Ritesh (CMA dependency, swapping >> coherent, noncoherent). I'm still not sure how to address the devicetree >> suggestion by Will [1][2]. I added the devicetree mailing list this time around >> to get more input on this. >> >> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/249180.html >> [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/249528.html > > Perhaps that can be done later then, since from what you're saying, we need > the command-line option either way? Have you looked at how this fits in with > the iommu-helper work from Ritesh? We could put the parameter parsing in > there too. > This doesn't seem to overlap with Ritesh's work. The atomic mapping is still handled in the arm specific code so I assume it would be handled in the arm64 specific code as well. Another question might be is if it would be useful to make the atomic code common somehow between arm and arm64. > Will > Thanks, Laura -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: lauraa@codeaurora.org (Laura Abbott) To: linux-arm-kernel@lists.infradead.org Subject: [PATCHv2] arm64: Add atomic pool for non-coherent and CMA allocaitons. Date: Tue, 03 Jun 2014 17:30:18 -0700 [thread overview] Message-ID: <538E689A.3050109@codeaurora.org> (raw) In-Reply-To: <20140603132842.GI23149@arm.com> On 6/3/2014 6:28 AM, Will Deacon wrote: > Hi Laura, > > On Mon, Jun 02, 2014 at 09:03:52PM +0100, Laura Abbott wrote: >> Neither CMA nor noncoherent allocations support atomic allocations. >> Add a dedicated atomic pool to support this. >> >> Change-Id: I46c8fdffe5e0687403d42b37643137c8cf344259 >> Signed-off-by: Laura Abbott <lauraa@codeaurora.org> >> --- >> >> v2: Various bug fixes pointed out by David and Ritesh (CMA dependency, swapping >> coherent, noncoherent). I'm still not sure how to address the devicetree >> suggestion by Will [1][2]. I added the devicetree mailing list this time around >> to get more input on this. >> >> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/249180.html >> [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/249528.html > > Perhaps that can be done later then, since from what you're saying, we need > the command-line option either way? Have you looked at how this fits in with > the iommu-helper work from Ritesh? We could put the parameter parsing in > there too. > This doesn't seem to overlap with Ritesh's work. The atomic mapping is still handled in the arm specific code so I assume it would be handled in the arm64 specific code as well. Another question might be is if it would be useful to make the atomic code common somehow between arm and arm64. > Will > Thanks, Laura -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2014-06-04 0:30 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-02 20:03 [PATCHv2] arm64: Add atomic pool for non-coherent and CMA allocaitons Laura Abbott 2014-06-02 20:03 ` Laura Abbott [not found] ` <1401739432-5358-1-git-send-email-lauraa-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2014-06-03 0:23 ` David Riley 2014-06-03 0:23 ` David Riley 2014-06-03 13:28 ` Will Deacon 2014-06-03 13:28 ` Will Deacon [not found] ` <20140603132842.GI23149-5wv7dgnIgG8@public.gmane.org> 2014-06-04 0:30 ` Laura Abbott [this message] 2014-06-04 0:30 ` Laura Abbott [not found] ` <538E689A.3050109-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2014-06-04 17:59 ` Will Deacon 2014-06-04 17:59 ` Will Deacon 2014-06-05 17:05 ` Catalin Marinas 2014-06-05 17:05 ` Catalin Marinas [not found] ` <20140605170500.GC27946-5wv7dgnIgG8@public.gmane.org> 2014-06-07 0:55 ` Laura Abbott 2014-06-07 0:55 ` Laura Abbott 2014-06-09 9:27 ` Catalin Marinas 2014-06-09 9:27 ` Catalin Marinas 2014-06-04 16:17 Ritesh Harjani
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=538E689A.3050109@codeaurora.org \ --to=lauraa-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \ --cc=Catalin.Marinas-5wv7dgnIgG8@public.gmane.org \ --cc=davidriley-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=ritesh.harjani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=will.deacon-5wv7dgnIgG8@public.gmane.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: linkBe 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.