Re: [Xen-devel] Cpu pools discussion

To:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] Cpu pools discussion
From:	Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date:	Tue, 28 Jul 2009 12:19:14 +0200
Cc:	George Dunlap <dunlapg@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Tue, 28 Jul 2009 03:19:39 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1248776323; x=1280312323; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Juergen=20Gross=20<juergen.gross@xxxxxxxxxxxxxx> \|Subject:=20Re:=20[Xen-devel]=20Cpu=20pools=20discussion \|Date:=20Tue,=2028=20Jul=202009=2012:19:14=20+0200 \|Message-ID:=20<4A6ED0A2.3010108@xxxxxxxxxxxxxx>\|To:=20Ke ir=20Fraser=20<keir.fraser@xxxxxxxxxxxxx>\|CC:=20George=20 Dunlap=20<dunlapg@xxxxxxxxx>,=20=0D=0A=20"xen-devel@lists .xensource.com"=20<xen-devel@xxxxxxxxxxxxxxxxxxx> \|MIME-Version:=201.0\|Content-Transfer-Encoding:=207bit \|In-Reply-To:=20<C6947ECD.10AE5%keir.fraser@xxxxxxxxxxxxx >\|References:=20<C6947ECD.10AE5%keir.fraser@xxxxxxxxxxxxx >; bh=J1/mm//vNazSJm/4wZMkSOMGg5SorWO8Vd3xysqW2U0=; b=KtUMpDg6k2QJce1YLFnlRN2YRzrSeKkFJGeDTcYZtoa8eWJo4Bzut4H/ ih+BKDQuJKndPJBcnKmHXxE1G+3JAnHGZDmnqGzE8INM8RoT3DaucYeCV lzgWOXu3X1g4qumNt5/uhfscVhNRneQ/Q4UM9mRYZ6FSC+T2jUYbW83hq KnPR/jeiXsfUjNB1i8jEzblfgM5SZaBWJLVp6yQDw3xFqTBbhl3p544J/ uYQeemVeTzuF9K8tv7r5libGRgmKg;
Domainkey-signature:	s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=QVqmV4XvPi+j/9qMxIWx8Fx4/Vjc3j2dKvK9DDg0EvI5Ib3B4FCmqGvt 3WHk/3+LlmMftKxv+XP1fDu8QzndnkWi5adpga77ESxptoxE7rnwHRr/4 NJZRk58R60N7ifm0YCQzzX7B7Qd5dPydmwTyKuz5V1XRTuy3+1BAk0Y/A 4Dh7g+7I0WGAbS2uqe24OWuiNFRiXBFK7esz2sYGxoWJ/PCS9Rm0bByR9 xBAM7FKLNXK0dbLYaYscpLC2iNEE9;
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<C6947ECD.10AE5%keir.fraser@xxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization:	Fujitsu Technology Solutions
References:	<C6947ECD.10AE5%keir.fraser@xxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mozilla-Thunderbird 2.0.0.22 (X11/20090707)

Keir Fraser wrote:
> On 28/07/2009 06:40, "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxx> wrote:
> 
>> BTW: continue_hypercall_on_cpu() exists on x86 only and it isn't really much
>> better than my usage of it:
>> - remember old pinning state of current vcpu
>> - pin it temporarily to the cpu it should continue on
>> - continue the hypercall
>> - remove temporary pinning
>> - re-establish old pinning (if any)
>> Pretty much the same as my solution above ;-)
> 
> If your solution locks the pinning, as we do already, so that it cannot be
> changed while the continue_hypercall_on_cpu() is running, then that is fine.
> If it's not locked then it's not safe.

Locking in my solution should be okay.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 636 47950
Fujitsu Technolgy Solutions               e-mail: juergen.gross@xxxxxxxxxxxxxx
Otto-Hahn-Ring 6                        Internet: ts.fujitsu.com
D-81739 Muenchen                 Company details: ts.fujitsu.com/imprint.html

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] Cpu pools discussion