Message-ID: <4874E379.3060609@goop.org>
Date: Wed, 09 Jul 2008 09:12:41 -0700
From: Jeremy Fitzhardinge <jeremy@goop.org>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Ingo Molnar <mingo@elte.hu>
CC: LKML <linux-kernel@vger.kernel.org>, x86@kernel.org,
       Stephen Tweedie <sct@redhat.com>, Eduardo Habkost <ehabkost@redhat.com>,
       Mark McLoughlin <markmc@redhat.com>
Subject: Re: [PATCH 00 of 55] xen64: implement 64-bit Xen support
References: <patchbomb.1215554782@localhost> <20080709111219.GA24874@elte.hu>
In-Reply-To: <20080709111219.GA24874@elte.hu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2695
Lines: 64

Ingo Molnar wrote:
> thanks Jeremy, applied.
>
> Since they depend on the generic-ipi infrastructure changes, i've 
> created a separate, new tip/xen-64bit branch. The tip/x86/xen-64bit got 
> merged into tip/x86/core and thus is headed for upstream. I have added 
> your patches to the new topic branch - see the shortlog further below.
>   

Speaking of generic-ipi, did you see the bugfix I posted for 
generic_smp_function_interrupt the other day?

I'm also seeing bad pointer dereferences in 
generic_smp_function_interrupt with some kernel configurations, which 
look like RCU failures (either oopses on following the next pointer in 
the list, or a bad function pointer for the call).  Other kernel configs 
are completely stable.  I haven't identified what the difference between 
working and not working is yet.

>> Following that are the Xen-specific changes to implement 64-bit 
>> support.  It works fairly well, but I know of a couple of bugs:
>>
>>  - 32-bit emulation doesn't work properly yet.  Something goes wrong
>>    with %gs, and a userspace %gs: reference segfaults.
>>
>>  - It crashes when bringing up secondary CPUs under some combinations
>>    of config.  I think it isn't quite setting up all the CPU sibling
>>    topology stuff for the various scheduler policies.  It's trying to
>>    set up the most simple of arrangements (every CPU is a singleton
>>    with no shared cache or anything else).  It was quite tricky to
>>    arrange this...
>>
>> I hope to have followup patches to address both of these in the next 
>> couple of days.  I expect both fixes will be small.
>>     
>
> that's OK, it should only affect 64-bit Xen, correct?
>   

Yep.  And if you avoid those two problem areas, it all seems pretty 
stable (16 vcpu kernbench runs with no problems, etc).

> Right now we need to get the generic impact of these patches tested, 
> fixes to xen64 functionality can be done later on in an add-on manner.
>
> Testing: i've done a trial merge of tip/xen-64bit to tip/master - not 
> pushed out yet. If it holds up in testing i'll put the integration rule 
> into tip/master.
>
> tip/xen-64bit (which i've just pushed out) can be cleanly git-merged 
> into tip/master, so if you send updates then please send it against such 
> a merged tree - even if tip/master does not have tip/xen-64bit yet. 
> These patches will need at least half a day of testing before i can push 
> them out.
>   

OK, thanks.

    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/