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 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] [PATCH] Fix some IPF Xen VT-d bugs

To: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [PATCH] Fix some IPF Xen VT-d bugs
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Tue, 6 Jan 2009 18:03:34 +0900
Cc: "'xen-ia64-devel@xxxxxxxxxxxxxxxxxxx'" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 06 Jan 2009 01:03:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EADF0A36011179459010BDF5142A45750463D2E9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <EADF0A36011179459010BDF5142A45750458C323@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20081224045307.GD16150%yamahata@xxxxxxxxxxxxx> <EADF0A36011179459010BDF5142A45750458C840@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20081224060440.GE16150%yamahata@xxxxxxxxxxxxx> <EADF0A36011179459010BDF5142A4575045D47B3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090105055151.GF32353%yamahata@xxxxxxxxxxxxx> <EADF0A36011179459010BDF5142A45750463CCA8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090105095713.GG32353%yamahata@xxxxxxxxxxxxx> <EADF0A36011179459010BDF5142A45750463D2E9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
applied, thanks.

On Tue, Jan 06, 2009 at 03:56:07PM +0800, Cui, Dexuan wrote:
> Isaku Yamahata wrote:
> > On Mon, Jan 05, 2009 at 05:39:52PM +0800, Cui, Dexuan wrote:
> >> Isaku Yamahata wrote:
> >>> On x86 case p2m_lock/unlock() avoids the race, but ia64 doesn't
> >>> have such lock. At this moment, the only HVM domain would be
> >>> supported. 
> >> OK, I understand we can't support pv iommu before resolving the
> >> lockless p2m issue. 
> >> 
> >>> The issue is dom0 case. I suppose it can be supported by mapping
> >>> all the pages except xen pages at boot time and not iommu
> >>> mapping/unmapping because those pages are already mapped to dom0
> >>> by intel_iommu_domain_init().
> >> I think actually we do this.
> >> For the special pv guest Dom0, I think there is no issue here because
> >>  dom0->need_iommu is actually always 0 (when Dom0 boots up and xen
> >> assigns all the devices to Dom0, xen doesn't invoke assign_device(),
> >> and invoking iommu_domain_init()/intel_iommu_domain_init() doesn't
> >> cause need_iommu(dom0) to be 1).   
> > 
> > Okay, I missed that.
> 
> Hi Isaku, so could you please check in the attached patch (the same as the 
> old one I posted and updated the comment) first?
> 
> For the calc_dom0_size() and the memory hole issues, we can fix them in a 
> later patch.
> 
> Thanks,
> -- Dexuan
> 


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

-- 
yamahata

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

<Prev in Thread] Current Thread [Next in Thread>