On 15/12/16 14:59, Jan Beulich wrote:
On 15.12.16 at 15:15, wrote:
>> On 09/12/16 08:59, Jan Beulich wrote:
>> On 08.12.16 at 18:51, wrote:
On 08/12/16 16:02, Jan Beulich wrote:
> variable. With an IRQ happening at the
>>> On 15.12.16 at 15:15, wrote:
> On 09/12/16 08:59, Jan Beulich wrote:
> On 08.12.16 at 18:51, wrote:
>>> On 08/12/16 16:02, Jan Beulich wrote:
variable. With an IRQ happening at the deepest point of the stack, and
with
On 09/12/16 08:59, Jan Beulich wrote:
On 08.12.16 at 18:51, wrote:
>> On 08/12/16 16:02, Jan Beulich wrote:
>>> variable. With an IRQ happening at the deepest point of the stack, and
>>> with send_guest_pirq() being called from there (leading to vcpu_kick()
>>> ->
>>> On 08.12.16 at 18:51, wrote:
> On 08/12/16 16:02, Jan Beulich wrote:
>> variable. With an IRQ happening at the deepest point of the stack, and
>> with send_guest_pirq() being called from there (leading to vcpu_kick()
>> -> ... -> csched_vcpu_wake() ->
On 08/12/16 16:02, Jan Beulich wrote:
> __get_page_type(), so far using an on-stack CPU mask variable, is
> involved in the recursion when e.g. pinning page tables. This means
"in recursion".
> there may be up two five instances of the function active at a time,
"up to five".
> implying five
__get_page_type(), so far using an on-stack CPU mask variable, is
involved in the recursion when e.g. pinning page tables. This means
there may be up two five instances of the function active at a time,
implying five instances of the (up to 512 bytes large) CPU mask
variable. With an IRQ happening