On Wed, Apr 18, 2018 at 03:24:46PM +0200, Hans de Goede wrote:
> Hi Greg,
>
> I know you are not entirely happy with the direct get_pages usage in this
> patch-set, but as discussed that is currently the only way to get DMA32
> memory.
>
> Adding a better API for getting DMA32 mem really falls
On Wed, Apr 18, 2018 at 03:24:46PM +0200, Hans de Goede wrote:
> Hi Greg,
>
> I know you are not entirely happy with the direct get_pages usage in this
> patch-set, but as discussed that is currently the only way to get DMA32
> memory.
>
> Adding a better API for getting DMA32 mem really falls
On Wed, Apr 18, 2018 at 03:24:46PM +0200, Hans de Goede wrote:
> Hi Greg,
>
> I know you are not entirely happy with the direct get_pages usage in this
> patch-set, but as discussed that is currently the only way to get DMA32
> memory.
>
> Adding a better API for getting DMA32 mem really falls
On Wed, Apr 18, 2018 at 03:24:46PM +0200, Hans de Goede wrote:
> Hi Greg,
>
> I know you are not entirely happy with the direct get_pages usage in this
> patch-set, but as discussed that is currently the only way to get DMA32
> memory.
>
> Adding a better API for getting DMA32 mem really falls
Hi Greg,
I know you are not entirely happy with the direct get_pages usage in this
patch-set, but as discussed that is currently the only way to get DMA32
memory.
Adding a better API for getting DMA32 mem really falls outside of the scope
of these patches and in the mean time the vboxguest
Hi Greg,
I know you are not entirely happy with the direct get_pages usage in this
patch-set, but as discussed that is currently the only way to get DMA32
memory.
Adding a better API for getting DMA32 mem really falls outside of the scope
of these patches and in the mean time the vboxguest
6 matches
Mail list logo