From: Oliver <oohall@gmail.com>
To: Stephen Bates <sbates@raithlin.com>
Cc: Balbir Singh <bsingharora@gmail.com>,
Logan Gunthorpe <logang@deltatee.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: lpar issue for ZONE_DEVICE p2pmem in 4.14-rc
Date: Thu, 26 Oct 2017 01:34:26 +1100 [thread overview]
Message-ID: <CAOSf1CGx2E3dOPPSrKOxHahGcu8BjRq02xeyEitPmiwoFcdo+w@mail.gmail.com> (raw)
In-Reply-To: <C65BF19B-49B3-480E-9435-17949645B992@raithlin.com>
On Tue, Oct 24, 2017 at 7:17 AM, Stephen Bates <sbates@raithlin.com> wrote=
:
>
>> [ 3.537780] lpar: Attempting to resize HPT to shift 21
>> [ 3.539251] Unable to resize hash page table to target order 21: -1
>> [ 3.541079] Unable to create mapping for hot added memory 0xc00021000=
0000000..0xc000210004000000: -2
>
>> For #1 above please check if your qemu supports H_RESIZE_HPT_* hcalls?
>
> Balbir do you have any suggestions as to how to test for this support? No=
te I am running this on my x86_64 host so there is no virtualization hardwa=
re in my QEMU. My qemu is very recent (QEMU emulator version 2.10.50 (v2.10=
.0-1026-gd8f932c-dirty)).
Honestly I'd just ignore the resize error. The hash table stores PTE
entries so it should be sized based on the amount of memory in the
system. If it's drastically under sized there'll be a performance hit,
but everything should still work.
>> For create mapping failures, the rc is -ENOENT. Can you help debug this =
further? We could do hcall tracing or enable debugging.
>
> Sure I can help debug. My original email also had all you needed to recre=
ate this issue so that=E2=80=99s an option too?
I'm not too sure what's happening there. My hunch is that the
hypervisor (qemu in this case) is rejecting the attempt to map the PCI
device MMIO space as cachable memory. On bare metal systems this can
result in cache paradoxes which will kill the system so the hypervisor
has an incentive to prevent that situation.
>
> Stephen
>
>
next prev parent reply other threads:[~2017-10-25 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 20:38 lpar issue for ZONE_DEVICE p2pmem in 4.14-rc Stephen Bates
2017-10-17 21:29 ` Balbir Singh
2017-10-21 15:03 ` Stephen Bates
2017-10-23 2:53 ` Balbir Singh
2017-10-23 20:17 ` Stephen Bates
2017-10-25 14:34 ` Oliver [this message]
2017-10-27 8:07 ` Oliver
2017-10-28 20:54 ` Stephen Bates
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=CAOSf1CGx2E3dOPPSrKOxHahGcu8BjRq02xeyEitPmiwoFcdo+w@mail.gmail.com \
--to=oohall@gmail.com \
--cc=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=logang@deltatee.com \
--cc=sbates@raithlin.com \
/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).