>>> On 09.02.18 at 13:35, wrote:
> On 30/01/18 16:40, Jan Beulich wrote:
> On 22.01.18 at 13:32, wrote:
>>> @@ -37,10 +52,24 @@ struct vcpu;
>>>
>>> struct cpu_info {
>>> struct cpu_user_regs guest_cpu_user_regs;
>>> -unsigned int processor_id;
>>> -struct vcpu *current_vcpu;
On 30/01/18 16:40, Jan Beulich wrote:
On 22.01.18 at 13:32, wrote:
>> @@ -37,10 +52,24 @@ struct vcpu;
>>
>> struct cpu_info {
>> struct cpu_user_regs guest_cpu_user_regs;
>> -unsigned int processor_id;
>> -struct vcpu *current_vcpu;
>> -unsigned long per_cpu_offset;
>> -
>>> On 30.01.18 at 18:12, wrote:
> On 30/01/18 16:40, Jan Beulich wrote:
> On 22.01.18 at 13:32, wrote:
>>> +static int pv_vcpu_init_xpti(struct vcpu *v)
>>> +{
>>> +struct domain *d = v->domain;
>>> +struct page_info *pg;
>>> +void *ptr;
>>> +struct cpu_info *info;
>>> +u
On 30/01/18 16:40, Jan Beulich wrote:
On 22.01.18 at 13:32, wrote:
>> In case of XPTI being active for a pv-domain allocate and initialize
>> per-vcpu stacks. The stacks are added to the per-domain mappings of
>> the pv-domain.
>
> Considering the intended use of these stacks (as per the ove
>>> On 22.01.18 at 13:32, wrote:
> In case of XPTI being active for a pv-domain allocate and initialize
> per-vcpu stacks. The stacks are added to the per-domain mappings of
> the pv-domain.
Considering the intended use of these stacks (as per the overview
mail) I consider 32k per vCPU a non-negl
In case of XPTI being active for a pv-domain allocate and initialize
per-vcpu stacks. The stacks are added to the per-domain mappings of
the pv-domain.
Signed-off-by: Juergen Gross
---
xen/arch/x86/pv/domain.c | 72 +++
xen/include/asm-x86/config.h |