[PATCH 3/4] PF: Provide additional direct page notification

2013-07-10 Thread Dominik Dingel
By setting a Kconfig option, the architecture can control when guest notifications will be presented by the apf backend. So there is the default batch mechanism, working as before, where the vcpu thread should pull in this information. On the other hand there is now the direct mechanism, this will

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-10 Thread Alexander Graf
On 10.07.2013, at 12:48, Gleb Natapov wrote: > On Wed, Jul 10, 2013 at 12:45:59PM +0200, Alexander Graf wrote: >> >> On 10.07.2013, at 12:42, Gleb Natapov wrote: >> >>> On Wed, Jul 10, 2013 at 12:39:01PM +0200, Alexander Graf wrote: On 09.07.2013, at 18:01, Christian Borntraeger wrot

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-10 Thread Alexander Graf
On 10.07.2013, at 12:49, Christian Borntraeger wrote: > On 10/07/13 12:39, Alexander Graf wrote: >> >> On 09.07.2013, at 18:01, Christian Borntraeger wrote: >> >>> On 09/07/13 15:56, Dominik Dingel wrote: By setting a Kconfig option, the architecture can control when guest notificatio

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-10 Thread Gleb Natapov
On Wed, Jul 10, 2013 at 12:45:59PM +0200, Alexander Graf wrote: > > On 10.07.2013, at 12:42, Gleb Natapov wrote: > > > On Wed, Jul 10, 2013 at 12:39:01PM +0200, Alexander Graf wrote: > >> > >> On 09.07.2013, at 18:01, Christian Borntraeger wrote: > >> > >>> On 09/07/13 15:56, Dominik Dingel wro

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-10 Thread Christian Borntraeger
On 10/07/13 12:39, Alexander Graf wrote: > > On 09.07.2013, at 18:01, Christian Borntraeger wrote: > >> On 09/07/13 15:56, Dominik Dingel wrote: >>> By setting a Kconfig option, the architecture can control when >>> guest notifications will be presented by the apf backend. >>> So there is the def

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-10 Thread Alexander Graf
On 10.07.2013, at 12:42, Gleb Natapov wrote: > On Wed, Jul 10, 2013 at 12:39:01PM +0200, Alexander Graf wrote: >> >> On 09.07.2013, at 18:01, Christian Borntraeger wrote: >> >>> On 09/07/13 15:56, Dominik Dingel wrote: By setting a Kconfig option, the architecture can control when gue

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-10 Thread Gleb Natapov
On Wed, Jul 10, 2013 at 12:39:01PM +0200, Alexander Graf wrote: > > On 09.07.2013, at 18:01, Christian Borntraeger wrote: > > > On 09/07/13 15:56, Dominik Dingel wrote: > >> By setting a Kconfig option, the architecture can control when > >> guest notifications will be presented by the apf backen

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-10 Thread Alexander Graf
On 09.07.2013, at 18:01, Christian Borntraeger wrote: > On 09/07/13 15:56, Dominik Dingel wrote: >> By setting a Kconfig option, the architecture can control when >> guest notifications will be presented by the apf backend. >> So there is the default batch mechanism, working as before, where the

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-09 Thread Christian Borntraeger
On 09/07/13 15:56, Dominik Dingel wrote: > By setting a Kconfig option, the architecture can control when > guest notifications will be presented by the apf backend. > So there is the default batch mechanism, working as before, where the vcpu > thread > should pull in this information. On the othe

[PATCH 3/4] PF: Provide additional direct page notification

2013-07-09 Thread Dominik Dingel
By setting a Kconfig option, the architecture can control when guest notifications will be presented by the apf backend. So there is the default batch mechanism, working as before, where the vcpu thread should pull in this information. On the other hand there is now the direct mechanism, this will

Re: [PATCH 3/4] PF: Provide additional direct page notification

2013-07-07 Thread Gleb Natapov
On Fri, Jul 05, 2013 at 10:55:53PM +0200, Dominik Dingel wrote: > By setting a Kconfig option, the architecture can control when > guest notifications will be presented by the apf backend. > So there is the default batch mechanism, working as before, where the vcpu > thread > should pull in this i

[PATCH 3/4] PF: Provide additional direct page notification

2013-07-05 Thread Dominik Dingel
By setting a Kconfig option, the architecture can control when guest notifications will be presented by the apf backend. So there is the default batch mechanism, working as before, where the vcpu thread should pull in this information. On the other hand there is now the direct mechanism, this will