Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1212374 > unrolled thread

Re: dom0 panic with Upstream Linux 4.1 tree

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: dom0 panic with Upstream Linux 4.1 tree Juergen Groß <jgross@suse.com> - 2015-08-24 19:40 +0200
    Re: dom0 panic with Upstream Linux 4.1 tree DuanZhenzhong <zhenzhong.duan@oracle.com> - 2015-08-26 09:10 +0200
    Re: dom0 panic with Upstream Linux 4.1 tree DuanZhenzhong <zhenzhong.duan@oracle.com> - 2015-08-26 09:10 +0200

#1212374 — Re: dom0 panic with Upstream Linux 4.1 tree

On 08/17/2015 09:32 AM, Zhenzhong Duan wrote:
> Hi Maintainers
>
> I found below panic when bootup OVM3.3.3 on HP PROLIANT DL980 G7 with
> dom0_mem=max:128G, not reproduce with dom0_mem=max:127G.
> Dom0 kernel is uek4 4.1.5-5.el6uek which is based on Upstream Linux 4.1
> tree. This looks like an upstream issue.
> Appereciate any patch/fix. Thanks

I don't think there is an easy patch in 4.1 to fix that. Your system has
half of the physical memory above the 512GB boundary making it
impossible for dom0 to use. Dom0 tries to use the memory layout of the
physical host, so it can only use memory below 512GB.

As you try to allocate 128GB for Dom0 some of the memory will end above
the magic boundary (there is only a little bit less than 128GB below
the boundary available).

For 4.3 I have posted a patch series which will eventually make it into
the kernel allowing Dom0 (and other pv-domains as well) to use memory
above the 512GB boundary.


Juergen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1213591

Juergen Groß wrote:
> On 08/17/2015 09:32 AM, Zhenzhong Duan wrote:
>> Hi Maintainers
>>
>> I found below panic when bootup OVM3.3.3 on HP PROLIANT DL980 G7 with
>> dom0_mem=max:128G, not reproduce with dom0_mem=max:127G.
>> Dom0 kernel is uek4 4.1.5-5.el6uek which is based on Upstream Linux 4.1
>> tree. This looks like an upstream issue.
>> Appereciate any patch/fix. Thanks
>
> I don't think there is an easy patch in 4.1 to fix that. Your system has
> half of the physical memory above the 512GB boundary making it
> impossible for dom0 to use. Dom0 tries to use the memory layout of the
> physical host, so it can only use memory below 512GB.
>
> As you try to allocate 128GB for Dom0 some of the memory will end above
> the magic boundary (there is only a little bit less than 128GB below
> the boundary available).
>
> For 4.3 I have posted a patch series which will eventually make it into
> the kernel allowing Dom0 (and other pv-domains as well) to use memory
> above the 512GB boundary.
Understood, thanks
Maybe the three level p2m tree need to be extended.
Where could I find above patch series? I'd like to evaluate the work of 
porting them to 4.1

zduan
> Juergen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1213595

Juergen Groß wrote:
> On 08/17/2015 09:32 AM, Zhenzhong Duan wrote:
>> Hi Maintainers
>>
>> I found below panic when bootup OVM3.3.3 on HP PROLIANT DL980 G7 with
>> dom0_mem=max:128G, not reproduce with dom0_mem=max:127G.
>> Dom0 kernel is uek4 4.1.5-5.el6uek which is based on Upstream Linux 4.1
>> tree. This looks like an upstream issue.
>> Appereciate any patch/fix. Thanks
>
> I don't think there is an easy patch in 4.1 to fix that. Your system has
> half of the physical memory above the 512GB boundary making it
> impossible for dom0 to use. Dom0 tries to use the memory layout of the
> physical host, so it can only use memory below 512GB.
>
> As you try to allocate 128GB for Dom0 some of the memory will end above
> the magic boundary (there is only a little bit less than 128GB below
> the boundary available).
>
> For 4.3 I have posted a patch series which will eventually make it into
> the kernel allowing Dom0 (and other pv-domains as well) to use memory
> above the 512GB boundary.
Understood, thanks
Maybe the three level p2m tree need to be extended.
Where could I find above patch series? I'd like to evaluate the work of 
porting them to 4.1

zduan
> Juergen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web