On Wed, 18 Dec 2019 16:11:51 +0100 "Jürgen Groß" wrote:
> On 18.12.19 15:40, SeongJae Park wrote:
> > On Wed, 18 Dec 2019 14:30:44 +0100 "Jürgen Groß" wrote:
> >
> >> On 18.12.19 13:42, SeongJae Park wrote:
> >>> On Wed, 18 Dec 2019 13:27:37 +0100 "Jürgen Groß" wrote:
> >>>
> On 18.12.19
On 18.12.19 15:40, SeongJae Park wrote:
On Wed, 18 Dec 2019 14:30:44 +0100 "Jürgen Groß" wrote:
On 18.12.19 13:42, SeongJae Park wrote:
On Wed, 18 Dec 2019 13:27:37 +0100 "Jürgen Groß" wrote:
On 18.12.19 11:42, SeongJae Park wrote:
From: SeongJae Park
'reclaim_memory' callback can race
On Wed, 18 Dec 2019 14:30:44 +0100 "Jürgen Groß" wrote:
> On 18.12.19 13:42, SeongJae Park wrote:
> > On Wed, 18 Dec 2019 13:27:37 +0100 "Jürgen Groß" wrote:
> >
> >> On 18.12.19 11:42, SeongJae Park wrote:
> >>> From: SeongJae Park
> >>>
> >>> 'reclaim_memory' callback can race with a driver
On 18.12.19 13:42, SeongJae Park wrote:
On Wed, 18 Dec 2019 13:27:37 +0100 "Jürgen Groß" wrote:
On 18.12.19 11:42, SeongJae Park wrote:
From: SeongJae Park
'reclaim_memory' callback can race with a driver code as this callback
will be called from any memory pressure detected context. To de
On Wed, 18 Dec 2019 13:27:37 +0100 "Jürgen Groß" wrote:
> On 18.12.19 11:42, SeongJae Park wrote:
> > From: SeongJae Park
> >
> > 'reclaim_memory' callback can race with a driver code as this callback
> > will be called from any memory pressure detected context. To deal with
> > the case, this
On 18.12.19 11:42, SeongJae Park wrote:
From: SeongJae Park
'reclaim_memory' callback can race with a driver code as this callback
will be called from any memory pressure detected context. To deal with
the case, this commit adds a spinlock in the 'xenbus_device'. Whenever
'reclaim_memory' cal
From: SeongJae Park
'reclaim_memory' callback can race with a driver code as this callback
will be called from any memory pressure detected context. To deal with
the case, this commit adds a spinlock in the 'xenbus_device'. Whenever
'reclaim_memory' callback is called, the lock of the device wh
