dom0_construct_pv() has logic to transition dom0 into a compat domain when
booting an ELF32 image.
One aspect which is missing is the CPUID policy recalculation, meaning that a
32bit dom0 sees a 64bit policy, which differ by the Long Mode feature flag in
particular. Another missing item is the x8
>>> On 06.02.19 at 21:41, wrote:
> Slightly RFC:
>
> 1) I've not worked out exactly what the
>
> v->vcpu_info = (void *)&d->shared_info->compat.vcpu_info[0];
>
>line is supposed to be doing and whether it is needed, but it doesn't
>appear to matter. It is perhaps another redundant
On 07/02/2019 12:58, Jan Beulich wrote:
On 06.02.19 at 21:41, wrote:
>> Slightly RFC:
>>
>> 1) I've not worked out exactly what the
>>
>> v->vcpu_info = (void *)&d->shared_info->compat.vcpu_info[0];
>>
>>line is supposed to be doing and whether it is needed, but it doesn't
>>appe
On 07/02/2019 14:29, Andrew Cooper wrote:
> On 07/02/2019 12:58, Jan Beulich wrote:
> On 06.02.19 at 21:41, wrote:
>>> Slightly RFC:
>>>
>>> 1) I've not worked out exactly what the
>>>
>>> v->vcpu_info = (void *)&d->shared_info->compat.vcpu_info[0];
>>>
>>>line is supposed to be doing
>>> On 07.02.19 at 14:29, wrote:
> On 07/02/2019 12:58, Jan Beulich wrote:
> On 06.02.19 at 21:41, wrote:
>>> 2) The reported
>>>
>>> Dom0 alloc.: 3e80->3ec0 (240470 pages to be
>>> allocated)
>>>
>>>line changes by 1 page because of the alloc_domheap_page(
On 07/02/2019 14:45, Jan Beulich wrote:
On 07.02.19 at 14:29, wrote:
>> On 07/02/2019 12:58, Jan Beulich wrote:
>> On 06.02.19 at 21:41, wrote:
2) The reported
Dom0 alloc.: 3e80->3ec0 (240470 pages to be
allocated)
line cha
On 07/02/2019 13:56, Juergen Gross wrote:
> On 07/02/2019 14:45, Jan Beulich wrote:
>>
> @@ -606,23 +598,14 @@ int __init dom0_construct_pv(struct domain *d,
> {
> maddr_to_page(mpt_alloc)->u.inuse.type_info = PGT_l4_page_table;
> l4start = l4tab = __va(mpt_al
On Thu, Feb 07, 2019 at 05:58:56AM -0700, Jan Beulich wrote:
> >>> On 06.02.19 at 21:41, wrote:
> > Slightly RFC:
> >
> > 1) I've not worked out exactly what the
> >
> > v->vcpu_info = (void *)&d->shared_info->compat.vcpu_info[0];
> >
> >line is supposed to be doing and whether it is n
>>> On 13.02.19 at 19:07, wrote:
> On Thu, Feb 07, 2019 at 05:58:56AM -0700, Jan Beulich wrote:
>> >>> On 06.02.19 at 21:41, wrote:
>> > Slightly RFC:
>> >
>> > 1) I've not worked out exactly what the
>> >
>> > v->vcpu_info = (void *)&d->shared_info->compat.vcpu_info[0];
>> >
>> >line
On Thu, Feb 14, 2019 at 01:11:49AM -0700, Jan Beulich wrote:
> >>> On 13.02.19 at 19:07, wrote:
> > On Thu, Feb 07, 2019 at 05:58:56AM -0700, Jan Beulich wrote:
> >> >>> On 06.02.19 at 21:41, wrote:
> >> > Slightly RFC:
> >> >
> >> > 1) I've not worked out exactly what the
> >> >
> >> > v-
>>> On 14.02.19 at 11:30, wrote:
> On Thu, Feb 14, 2019 at 01:11:49AM -0700, Jan Beulich wrote:
>> >>> On 13.02.19 at 19:07, wrote:
>> > On Thu, Feb 07, 2019 at 05:58:56AM -0700, Jan Beulich wrote:
>> >> >>> On 06.02.19 at 21:41, wrote:
>> >> > Slightly RFC:
>> >> >
>> >> > 1) I've not worked o
11 matches
Mail list logo
