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: Changeset 20209 causes an issue in xen_in_range()

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: [Xen-devel] RE: Changeset 20209 causes an issue in xen_in_range()
From: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
Date: 2010年1月14日 21:13:53 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Delivery-date: 2010年1月14日 05:14:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C774BEC2.6629%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>
References: <EB8593BCECAB3D40A8248BE0B6400A38355E3523@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C774BEC2.6629%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqVC7WojRF7R9KjTMmsbJaWBuv/iwAA6WDaAADpL+AAAJGbyAABgWyg
Thread-topic: Changeset 20209 causes an issue in xen_in_range()
Okay, seems a cleanup patch for that is needed, otherwise the related logic 
maybe misleading... 
Xiantao
Keir Fraser wrote:
> At some point we will introduce hotplug notifiers and have per-cpu
> areas set up only for present CPUs. The possible_map is basically
> deprecated/obsolete. 
>
> -- keir
>
> On 14/01/2010 12:19, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx> wrote:
>
>> I am curious that all bits of cpu_possible_map are all set to 1, so
>> the related checks in percpu_free_unused_areas are unnecessary ?
>> Xiantao
>> 
>> 
>> Keir Fraser wrote:
>>> On 14/01/2010 11:21, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>>> 
>>>>>> However, in iommu_set_dom0_mapping(), xen_in_range() is still
>>>>>> True for the freed pages above, so devices in Dom0 can meet with
>>>>>> DMA fault.
>>>>> 
>>>>> Should be fixed by c/s 20803.
>>>> 
>>>> Do you really think so? Masking "start" with PERCPU_SIZE-1 doesn't
>>>> make sense, as it may be arbitrarily before __percpu_start and
>>>> not aligned. Below my take on it.
>>> 
>>> How about c/s 20806?
>>> 
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [PATCH] RE: [Xen-devel] Failed to create a domain with xen-unstable (Error 22:Invalid argument) , Jan Beulich
Next by Date: [Xen-devel] Re: Changeset 20209 causes an issue in xen_in_range() , Keir Fraser
Previous by Thread: [Xen-devel] Re: Changeset 20209 causes an issue in xen_in_range() , Keir Fraser
Next by Thread: [Xen-devel] Re: Changeset 20209 causes an issue in xen_in_range() , Keir Fraser
Indexes: [Date] [Thread] [Top] [All Lists]

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

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