Wtf yo?
Am 15.06.22 um 20:32 schrieb Daniel Vetter:
On Wed, 15 Jun 2022 at 19:43, T.J. Mercier wrote:
On Wed, Jun 1, 2022 at 5:40 AM Daniel Vetter wrote:
On Mon, May 30, 2022 at 08:12:16AM +0200, Christian König wrote:
Am 25.05.22 um 23:05 schrieb T.J. Mercier:
On Wed, May 25, 2022 at 7:38 AM Danie
On Wed, 15 Jun 2022 at 19:43, T.J. Mercier wrote:
>
> On Wed, Jun 1, 2022 at 5:40 AM Daniel Vetter wrote:
> >
> > On Mon, May 30, 2022 at 08:12:16AM +0200, Christian König wrote:
> > > Am 25.05.22 um 23:05 schrieb T.J. Mercier:
> > > > On Wed, May 25, 2022 at 7:38 AM Daniel Vetter wrote:
> > > >
On Wed, Jun 1, 2022 at 5:40 AM Daniel Vetter wrote:
>
> On Mon, May 30, 2022 at 08:12:16AM +0200, Christian König wrote:
> > Am 25.05.22 um 23:05 schrieb T.J. Mercier:
> > > On Wed, May 25, 2022 at 7:38 AM Daniel Vetter wrote:
> > > > On Tue, May 17, 2022 at 08:13:24AM +0200, Greg Kroah-Hartman w
On Mon, May 30, 2022 at 08:12:16AM +0200, Christian König wrote:
> Am 25.05.22 um 23:05 schrieb T.J. Mercier:
> > On Wed, May 25, 2022 at 7:38 AM Daniel Vetter wrote:
> > > On Tue, May 17, 2022 at 08:13:24AM +0200, Greg Kroah-Hartman wrote:
> > > > On Mon, May 16, 2022 at 05:08:05PM -0700, T.J. Me
Am 25.05.22 um 23:05 schrieb T.J. Mercier:
On Wed, May 25, 2022 at 7:38 AM Daniel Vetter wrote:
On Tue, May 17, 2022 at 08:13:24AM +0200, Greg Kroah-Hartman wrote:
On Mon, May 16, 2022 at 05:08:05PM -0700, T.J. Mercier wrote:
On Mon, May 16, 2022 at 12:21 PM Christian König
wrote:
Am 16.05.
On Wed, May 25, 2022 at 2:05 PM T.J. Mercier wrote:
>
> On Wed, May 25, 2022 at 7:38 AM Daniel Vetter wrote:
> >
> > On Tue, May 17, 2022 at 08:13:24AM +0200, Greg Kroah-Hartman wrote:
> > > On Mon, May 16, 2022 at 05:08:05PM -0700, T.J. Mercier wrote:
> > > > On Mon, May 16, 2022 at 12:21 PM Chr
On Wed, May 25, 2022 at 7:38 AM Daniel Vetter wrote:
>
> On Tue, May 17, 2022 at 08:13:24AM +0200, Greg Kroah-Hartman wrote:
> > On Mon, May 16, 2022 at 05:08:05PM -0700, T.J. Mercier wrote:
> > > On Mon, May 16, 2022 at 12:21 PM Christian König
> > > wrote:
> > > >
> > > > Am 16.05.22 um 20:08 s
On Tue, May 17, 2022 at 08:13:24AM +0200, Greg Kroah-Hartman wrote:
> On Mon, May 16, 2022 at 05:08:05PM -0700, T.J. Mercier wrote:
> > On Mon, May 16, 2022 at 12:21 PM Christian König
> > wrote:
> > >
> > > Am 16.05.22 um 20:08 schrieb T.J. Mercier:
> > > > On Mon, May 16, 2022 at 10:20 AM Christ
Am 20.05.22 um 00:58 schrieb T.J. Mercier:
[SNIP]
Is there some other
solution to the problem of exports getting blocked that you would
suggest here?
Well pretty much the same as Greg outlined as well. Go back to your
drawing board and come back with a solution which does not need such
workarou
On Tue, May 17, 2022 at 04:09:36PM -0700, T.J. Mercier wrote:
> On Mon, May 16, 2022 at 11:13 PM Greg Kroah-Hartman
> wrote:
> >
> > On Mon, May 16, 2022 at 05:08:05PM -0700, T.J. Mercier wrote:
> > > On Mon, May 16, 2022 at 12:21 PM Christian König
> > > wrote:
> > > >
> > > > Am 16.05.22 um 20:
Am 18.05.22 um 01:09 schrieb T.J. Mercier:
[SNIP]
Perhaps we should go just one step further and make a misc device node
for dmabug debugging information to be in and just have userspace
poll/read on the device node and we spit the info that used to be in
debugfs out through that? That way this
Am 17.05.22 um 08:13 schrieb Greg Kroah-Hartman:
On Mon, May 16, 2022 at 05:08:05PM -0700, T.J. Mercier wrote:
[SNIP]
Fixes: bdb8d06dfefd ("dmabuf: Add the capability to expose DMA-BUF stats in
sysfs")
Originally-by: Hridya Valsaraju
Signed-off-by: T.J. Mercier
---
See the originally submit
On Mon, May 16, 2022 at 05:08:05PM -0700, T.J. Mercier wrote:
> On Mon, May 16, 2022 at 12:21 PM Christian König
> wrote:
> >
> > Am 16.05.22 um 20:08 schrieb T.J. Mercier:
> > > On Mon, May 16, 2022 at 10:20 AM Christian König
> > > wrote:
> > >> Am 16.05.22 um 19:13 schrieb T.J. Mercier:
> > >>
Am 16.05.22 um 20:08 schrieb T.J. Mercier:
On Mon, May 16, 2022 at 10:20 AM Christian König
wrote:
Am 16.05.22 um 19:13 schrieb T.J. Mercier:
Recently, we noticed an issue where a process went into direct reclaim
while holding the kernfs rw semaphore for sysfs in write (exclusive)
mode. This c
Am 16.05.22 um 19:13 schrieb T.J. Mercier:
Recently, we noticed an issue where a process went into direct reclaim
while holding the kernfs rw semaphore for sysfs in write (exclusive)
mode. This caused processes who were doing DMA-BUF exports and releases
to go into uninterruptible sleep since the
16 matches
Mail list logo