From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Alex Thorlton <athorlton@sgi.com>,
Jan Beulich <jbeulich@suse.com>
Subject: ACPI fixmap overflow
Date: Tue, 15 Nov 2016 14:34:28 -0500 [thread overview]
Message-ID: <c0b2cc84-3b0f-7860-d051-6166616f8a5f@oracle.com> (raw)
In addition to running out of e820 entries on that large machine that
Alex was referring to in [0] he is also running out of ACPI fixmap space
while parsing MADT (the box has *lots* of processors). The
quick-and-dirty solution is to increase NUM_FIXMAP_ACPI_PAGES but I
wonder whether we should move to dynamic memory allocation.
-boris
[0]
https://lists.xenproject.org/archives/html/xen-devel/2016-11/msg01077.html
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-11-15 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 19:34 Boris Ostrovsky [this message]
2016-11-15 19:45 ` ACPI fixmap overflow Andrew Cooper
2016-11-15 20:39 ` Boris Ostrovsky
2016-11-15 20:44 ` Andrew Cooper
2016-11-15 20:51 ` Boris Ostrovsky
2016-11-16 10:08 ` Jan Beulich
2016-11-17 15:01 ` Boris Ostrovsky
2016-11-17 16:04 ` Alex Thorlton
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=c0b2cc84-3b0f-7860-d051-6166616f8a5f@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=athorlton@sgi.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xen.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).