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] add one page attribute to indicate this page

To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel][PATCH] add one page attribute to indicate this page is physical IO page
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Mon, 29 Sep 2008 12:21:05 +0900
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 28 Sep 2008 20:21:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <F7C8A4D3A9905B45A80E4C194793FA6501ABAC1503@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: <F7C8A4D3A9905B45A80E4C194793FA6501ABAC1503@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
Hi Anthony.

I guess you are working on VT-d support for IA64.
You've sent out those patches independently which seem to
be preparation for VT-d support.

However it is very difficult to guess how you are planning to use those
modifications eventually. So it's very difficult to review those patches.
At this moment I can comment only on patch style which isn't essential.

If you already have working patches, could you please send them
as a series of patches? (Even un-cleaned patches would help to understand.)
If not, could you provide overview of the design or something like 
that which helps me to understand its overview and how VT-d patches
will be implemented.

At this moment the followings come into my mind. (Random thoughts)
- One of the Xen/IA64 features is lockless P2M table unlike x86 case.
  I think it would be very difficult to maintain the VT-d translation table 
  consistent with the p2m and m2p tables without lock.

- What scope are you aiming?
  Now x86 supports VT-d for VMM protection, dom0, PV domU and HVM
  with balloon.
  On the other hand ia64 doesn't support balloon for HVM because
  the p2m for HVM domain is assumed to be read-only.
  How about MSI(-X)?

thanks,

On Sun, Sep 28, 2008 at 12:48:48PM +0800, Xu, Anthony wrote:
> Add _PAGE_DIRECT_IO page attribute to indicate this page is physical IO page
> 
> Signed-off-by; Anthony Xu < anthony.xu@xxxxxxxxx >


> _______________________________________________
> 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>