linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: DuanZhenzhong <zhenzhong.duan@oracle.com>
To: "Juergen Groß" <jgross@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: dom0 panic with Upstream Linux 4.1 tree
Date: Wed, 26 Aug 2015 15:06:03 +0800	[thread overview]
Message-ID: <55DD655B.6010606@oracle.com> (raw)
In-Reply-To: <55DB55B4.7090107@suse.com>

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

  reply	other threads:[~2015-08-26  7:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17  7:32 dom0 panic with Upstream Linux 4.1 tree Zhenzhong Duan
2015-08-24 17:34 ` Juergen Groß
2015-08-26  7:06   ` DuanZhenzhong [this message]
2015-08-26  7:06   ` DuanZhenzhong
  -- strict thread matches above, loose matches on Subject: below --
2015-08-17  8:32 Zhenzhong Duan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55DD655B.6010606@oracle.com \
    --to=zhenzhong.duan@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).