On Sat, Aug 01, 2020 at 01:20:07AM -0700, David Rientjes wrote:
> To follow-up on this, the introduction of the DMA atomic pools in 5.8
> fixes an issue for any AMD SEV enabled guest that has a driver that
> requires atomic DMA allocations (for us, nvme) because runtime decryption
> of memory al
On Sat, 1 Aug 2020 at 14:27, Christoph Hellwig wrote:
>
> On Sat, Aug 01, 2020 at 01:20:07AM -0700, David Rientjes wrote:
> > To follow-up on this, the introduction of the DMA atomic pools in 5.8
> > fixes an issue for any AMD SEV enabled guest that has a driver that
> > requires atomic DMA alloca
On Sat, 2020-08-01 at 17:27 +0530, Amit Pundir wrote:
[...]
> > I'm between a rock and a hard place here. If we simply want to revert
> > commits as-is to make sure both the Raspberry Pi 4 and thone phone do
> > not regress we'll have to go all the way back and revert the whole SEV
> > pool supp
On Sat, Aug 01, 2020 at 05:27:04PM +0530, Amit Pundir wrote:
> Hi, I found the problematic memory region. It was a memory
> chunk reserved/removed in the downstream tree but was
> seemingly reserved upstream for different drivers. I failed to
> calculate the length of the total region reserved down
On Sat, Aug 1, 2020 at 4:57 AM Amit Pundir wrote:
>
> Hi, I found the problematic memory region. It was a memory
> chunk reserved/removed in the downstream tree but was
> seemingly reserved upstream for different drivers.
Is this happening with a clean tree, or are there external drivers
involved
On Sat, 1 Aug 2020 at 23:58, Linus Torvalds
wrote:
>
> On Sat, Aug 1, 2020 at 4:57 AM Amit Pundir wrote:
> >
> > Hi, I found the problematic memory region. It was a memory
> > chunk reserved/removed in the downstream tree but was
> > seemingly reserved upstream for different drivers.
>
> Is this
On Sat, 1 Aug 2020 at 23:09, Christoph Hellwig wrote:
>
> On Sat, Aug 01, 2020 at 05:27:04PM +0530, Amit Pundir wrote:
> > Hi, I found the problematic memory region. It was a memory
> > chunk reserved/removed in the downstream tree but was
> > seemingly reserved upstream for different drivers. I f
On Sun, 2 Aug 2020 at 10:16, Amit Pundir wrote:
>
> On Sat, 1 Aug 2020 at 23:09, Christoph Hellwig wrote:
> >
> > On Sat, Aug 01, 2020 at 05:27:04PM +0530, Amit Pundir wrote:
> > > Hi, I found the problematic memory region. It was a memory
> > > chunk reserved/removed in the downstream tree but w
On Sun, 2 Aug 2020, Amit Pundir wrote:
> > > > Hi, I found the problematic memory region. It was a memory
> > > > chunk reserved/removed in the downstream tree but was
> > > > seemingly reserved upstream for different drivers. I failed to
> > > > calculate the length of the total region reserved d
On Sun, Aug 02, 2020 at 09:14:41PM -0700, David Rientjes wrote:
> Christoph: since we have atomic DMA coherent pools in 5.8 now, recall our
> previous discussions, including Greg KH, regarding backports to stable
> trees (we are interested in 5.4 and 5.6) of this support for the purposes
> of co
On Mon, 3 Aug 2020, Christoph Hellwig wrote:
> On Sun, Aug 02, 2020 at 09:14:41PM -0700, David Rientjes wrote:
> > Christoph: since we have atomic DMA coherent pools in 5.8 now, recall our
> > previous discussions, including Greg KH, regarding backports to stable
> > trees (we are interested in
11 matches
Mail list logo