public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/5] ArmPkg et al: remove UncachedMemoryallocationLib
Date: Tue, 29 Aug 2017 17:57:29 +0100	[thread overview]
Message-ID: <CAKv+Gu_Z3NunUeY17tEt5zUOa287ivcninL6uL2VFsLv7UHkYg@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu8qmXnSOHdMqJcPR38MASj5DCqkxQe2oSdJsnPPt9Rd4Q@mail.gmail.com>

On 29 August 2017 at 16:47, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> On 29 August 2017 at 16:44, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>> On Fri, Aug 25, 2017 at 01:10:09PM +0100, Ard Biesheuvel wrote:
>>> This series is a followup to 'ArmPkg/ArmDmaLib: remove dependency on
>>> UncachedMemoryAllocationLib' sent out yesterday, and removes library
>>> entirely.
>>>
>>> There are two reasons for this:
>>> - UncachedMemoryAllocationLib is often abused by drivers that should
>>>   be using DMA abstractions instead. It is up to the platform to decide
>>>   whether DMA is cache coherent or not, and the fact that non-cache
>>>   coherent DMA may be implemented using uncached allocations should remain
>>>   an implementation detail of the DmaLib instance.
>>>
>>> - The code is poorly maintained, only frees its allocations in the destructor,
>>>   and misleads by exposing pool allocate/free entry points that are actually
>>>   backed by page based allocations.
>>>
>>> Patches #1 and #2 add a DmaAllocateAlignedBuffer() to DmaLib and both
>>> its implementations. This is required for current users of
>>> UncachedMemoryAllocationLib that rely on minimum alignment to be able
>>> to switch the DmaLib.
>>>
>>> Patches #3 and #4 remove a couple of stale references.
>>>
>>> Patch #5 actually removes the library and its single remaining implementation.
>>
>> For the series:
>> Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
>>
>> However, this breaks a bunch of (edk2-)platforms: juno, fvp, tc2,
>> hikey and armada70x0. Is there a follow-on patch coming for those,
>> and could you hold off on pushing this series until that is ready?
>>
>> Armada has the only non-bogus UncachedMemoryAllocationLib dependency,
>> the others are just trivial deletions.
>>
>
> Yes. There are interdependencies between repos, so I will just merge
> #1 and #2 and hold off with the rest until after all dependencies have
> been removed.


Patches #1 .. #4 pushed as

deef290f95e0 EmbeddedPkg/DmaLib: add routine to allocate aligned buffers
4b4104d87e28 ArmPkg/ArmDmaLib: implement DmaAllocateAlignedBuffer()
b56397ba9f67 BeagleBoardPkg: remove UncachedMemoryAllocationLib resolutions
c1d799b91509 Omap35xxPkg: remove bogus UncachedMemoryAllocationLib dependency

I will push the remaining patch that actually removes
UncachedMemoryAllocationLib once the dependencies are gone from
edk2-platforms.


      reply	other threads:[~2017-08-29 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 12:10 [PATCH 0/5] ArmPkg et al: remove UncachedMemoryallocationLib Ard Biesheuvel
2017-08-25 12:10 ` [PATCH 1/5] EmbeddedPkg/DmaLib: add routine to allocate aligned buffers Ard Biesheuvel
2017-08-25 12:10 ` [PATCH 2/5] ArmPkg/ArmDmaLib: implement DmaAllocateAlignedBuffer() Ard Biesheuvel
2017-08-25 12:10 ` [PATCH 3/5] BeagleBoardPkg: remove UncachedMemoryAllocationLib resolutions Ard Biesheuvel
2017-08-25 12:10 ` [PATCH 4/5] Omap35xxPkg: remove bogus UncachedMemoryAllocationLib dependency Ard Biesheuvel
2017-08-25 12:10 ` [PATCH 5/5] ArmPkg: remove UncachedMemoryAllocationLib Ard Biesheuvel
2017-08-31 14:00   ` Ard Biesheuvel
2017-08-29 15:44 ` [PATCH 0/5] ArmPkg et al: remove UncachedMemoryallocationLib Leif Lindholm
2017-08-29 15:47   ` Ard Biesheuvel
2017-08-29 16:57     ` Ard Biesheuvel [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-list 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=CAKv+Gu_Z3NunUeY17tEt5zUOa287ivcninL6uL2VFsLv7UHkYg@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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