WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

[Xen-devel] Re: [PATCH] 2nd try: 2/2 VCPU creation and allocation

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] 2nd try: 2/2 VCPU creation and allocation
From: Ryan Harper <ryanh@xxxxxxxxxx>
Date: 2005年10月12日 11:15:31 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: 2005年10月12日 16:13:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8a1ee1a6fae5f2217438c742318c4d1a@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20051010151651.GK17358@xxxxxxxxxx> <bf24a942f6b45d1ca73cf693b4cdf11d@xxxxxxxxxxxx> <20051010152821.GN17358@xxxxxxxxxx> <3f428c67eaeb9dd543c246e55a156fd3@xxxxxxxxxxxx> <20051010160538.GO17358@xxxxxxxxxx> <f2c38fb2e629d2867f0a00e083c5813a@xxxxxxxxxxxx> <20051010162354.GP17358@xxxxxxxxxx> <e03426a13ac8e7d1aa04b6d34258d661@xxxxxxxxxxxx> <20051011151656.GT17358@xxxxxxxxxx> <8a1ee1a6fae5f2217438c742318c4d1a@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
* Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> [2005年10月12日 11:05]:
>
> On 11 Oct 2005, at 16:16, Ryan Harper wrote:
>
> >Allocation map.
>
> What does this patch buy us, given that we already support per-vcpu 
> maps? If I understand correctly, this adds a per-domain map, which 
> seems redundant to me.
I guess not as much as it did before we had build-time vcpu creation. I
can easily translate the allocation map in the configuration file into a
set of pincpu ops before allocating domain memory and achieve the same
effect as the patch does without the changes to the domain structure and
pincpu dom0_op. 
I'll resend without the changes to xen.
-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@xxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] kernel version , Stephan Böni
Next by Date: [Xen-devel] Daily Xen Builds , David F Barrera
Previous by Thread: [Xen-devel] Re: [PATCH] 2nd try: 2/2 VCPU creation and allocation , Keir Fraser
Next by Thread: RE: [Xen-devel] [PATCH] 0/2 VCPU creation and allocation , Ian Pratt
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /