From: Ryan Harper <ryanh@us.ibm.com>
To: "Subrahmanian, Raj" <raj.subrahmanian@unisys.com>
Cc: Ryan Harper <ryanh@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: Numa=on broken?
Date: Thu, 3 May 2007 18:10:05 -0500 [thread overview]
Message-ID: <20070503231005.GP27552@us.ibm.com> (raw)
In-Reply-To: <94C8C9E8B25F564F95185BDA64AB05F605025E4C@USTR-EXCH5.na.uis.unisys.com>
* Subrahmanian, Raj <raj.subrahmanian@unisys.com> [2007-05-03 17:30]:
> All,
> It looks like numa=on is broken.
> I have tried with the tip of the tree, with the changeset 14676 (which
> fixes the numa=on problem) and the two patches that Ryan sent out.
> I am running with boot options acpi=on and numa=on.
> I am running on an ES7000 with 2 nodes (2 cells of 8 processors and 32
> GB memory each).
>
> Thanks
> Raj
> PS. We(Unisys) are going to start running our weekly tests with default
> numa=on. This weeks' tests brought out this problem.
>
> \ \/ /___ _ __ |___ / / _ \ _ _ _ __ ___| |_ __ _| |__ | | ___
> \ // _ \ '_ \ |_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
> / \ __/ | | | ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | | __/
> /_/\_\___|_| |_| |____(_)___/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
>
> http://www.cl.cam.ac.uk/netos/xen
> University of Cambridge Computer Laboratory
>
> Xen version 3.0-unstable (root@site) (gcc version 4.1.2 20070115
> (prerelease) (SUSE Linux)) Thu May 3 16:58:28 EDT 2007
> Latest ChangeSet: Thu May 03 11:22:58 2007 +0100 15007:c857bf38f015
>
> (XEN) Command line: /boot/xen.gz com1=115200,8n1 apic_verbosity=debug
> dom0_mem=512M acpi=on numa=on
> (XEN) 0000000000000000 - 000000000009d000 (usable)
> (XEN) 000000000009d800 - 00000000000a0000 (reserved)
> (XEN) 00000000000ce000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 0000000037e70000 (usable)
> (XEN) 0000000037e70000 - 0000000037ed8000 (ACPI data)
> (XEN) 0000000037ed8000 - 0000000037f00000 (ACPI NVS)
> (XEN) 0000000037f00000 - 00000000f0000000 (usable)
> (XEN) 00000000f8000000 - 00000000fec00000 (reserved)
> (XEN) 00000000fffc0000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000001008000000 (usable)
> (XEN) System RAM: 65407MB (66976820kB)
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 2!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 2!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 2!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 2!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 2!
what repo and what changeset? We fixed this issue a while ago,
I just booted:
changeset: 15020:6f37c763bc0f from http://xenbits.xensource.com/xen-3.1-testing.hg
and
changeset: 15009:3a5722420de7 from http://xenbits.xensource.com/xen-unstable.hg
with no issues on my numa hardware.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2007-05-03 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B05D2E415E8CC94897BB44233D14EE6805A01ED6@USTR-EXCH5.na.uis.unisys.com>
2007-05-03 19:25 ` Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFIsPhysical (takes no arguments) Krysan, Susan
2007-05-03 20:29 ` Keir Fraser
2007-05-03 22:29 ` Numa=on broken? Subrahmanian, Raj
2007-05-03 23:10 ` Ryan Harper [this message]
2007-05-04 2:39 ` Subrahmanian, Raj
2007-05-04 6:23 ` Subrahmanian, Raj
2007-05-04 13:33 ` Ryan Harper
2007-05-04 13:38 ` Ryan Harper
2007-05-04 17:32 ` Subrahmanian, Raj
2007-05-07 20:24 ` Subrahmanian, Raj
2007-05-07 20:43 ` Ryan Harper
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=20070503231005.GP27552@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=raj.subrahmanian@unisys.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.