Port-xen archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: amd64 MP (was Re: pae MP on cherry-xenmp)
On 10/12/11 23:49, David Howland wrote:
> On 9/9/11 4:57 AM, Cherry G. Mathew wrote:
>> Just to say I've checked in amd64 support. Do give it a spin, and let
>> us know (on list) how it goes.
>>
>> I haven't tested this on dom0.
>
> You, Sir, are my hero.
>
> I'm checking in with my results so far...
>
> I am running on an Intel Xeon platform, Debian squeeze dom0 (Xen 4.0)
> with 2 vcpu's and 2GB allocated to NetBSD domU. My domU is running 5.1
> userland with cherry-xenmp kernel, compiled like this (code was checked
> out October 12th):
>
> cvs checkout -r cherry-xenmp src
> ./build.sh -m amd64 tools
> ./build.sh -m amd64 kernel=XEN3_DOMU
>
> Status: working fine, but I haven't loaded it much yet. I am running
> GNOME in Xvnc and I'm able to poke around and browse the web just fine.
> I'll try to build /src with -j4.
>
> -d
Is this for an amd64 domU ?
I lost the thread on this subject some weeks ago. Been setting up a pet
dom0 to test this out, and was going with i386+PAE.
Regarding dom0 support (which Cherry says he hasn't tested), and just to
confirm: will compiling this code yield a MP-aware dom0, even though it
may have stabilility/performance issues?
Generally speaking, is the difference between the MP code for dom0 and
domU big enough that the dom0 typical workload would trigger bugs that a
domU likely wouldn't?
I ask to determine the best path of action: if MP-domU is likely to
trigger the same class of bugs as MP-dom0, then it might make more sense
to run this code on a test domU (exclusively) first (not having the dom0
crash all the time helps with testing)
Regards,
Hugo
Home |
Main Index |
Thread Index |
Old Index