On 22.05.15 at 10:25, jbeul...@suse.com wrote:
On 21.05.15 at 13:48, jbeul...@suse.com wrote:
On 21.05.15 at 13:08, andrew.coop...@citrix.com wrote:
It might be wise to have a BUILD_BUG_ON() which confirms that
STUBS_PER_PAGE is a power of two, which is a requirement given the way
it is
On 21.05.15 at 13:48, jbeul...@suse.com wrote:
On 21.05.15 at 13:08, andrew.coop...@citrix.com wrote:
On 21/05/15 11:15, Jan Beulich wrote:
This is needed as stacks are going to become non-executable. Use
separate stub pages (shared among suitable CPUs on the same node)
instead.
Stub areas
On 22/05/2015 09:25, Jan Beulich wrote:
On 21.05.15 at 13:48, jbeul...@suse.com wrote:
On 21.05.15 at 13:08, andrew.coop...@citrix.com wrote:
On 21/05/15 11:15, Jan Beulich wrote:
This is needed as stacks are going to become non-executable. Use
separate stub pages (shared among suitable CPUs
On 21.05.15 at 13:08, andrew.coop...@citrix.com wrote:
On 21/05/15 11:15, Jan Beulich wrote:
This is needed as stacks are going to become non-executable. Use
separate stub pages (shared among suitable CPUs on the same node)
instead.
Stub areas (currently 128 bytes each) are being split into
On 21/05/15 12:48, Jan Beulich wrote:
On 21.05.15 at 13:08, andrew.coop...@citrix.com wrote:
On 21/05/15 11:15, Jan Beulich wrote:
This is needed as stacks are going to become non-executable. Use
separate stub pages (shared among suitable CPUs on the same node)
instead.
Stub areas
This is needed as stacks are going to become non-executable. Use
separate stub pages (shared among suitable CPUs on the same node)
instead.
Stub areas (currently 128 bytes each) are being split into two parts -
a fixed usage one (the syscall ones) and dynamically usable space,
which will be used
On 21/05/15 11:15, Jan Beulich wrote:
This is needed as stacks are going to become non-executable. Use
separate stub pages (shared among suitable CPUs on the same node)
instead.
Stub areas (currently 128 bytes each) are being split into two parts -
a fixed usage one (the syscall ones) and
