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


Re: [Xen-ia64-devel] RE: [Xen-devel] [PATCH] blkif include fixes

To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Subject: Re: [Xen-ia64-devel] RE: [Xen-devel] [PATCH] blkif include fixes
From: Arun Sharma <arun.sharma@xxxxxxxxx>
Date: Thu, 11 Aug 2005 15:46:32 -0700
Cc: "Ling, Xiaofeng" <xiaofeng.ling@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 11 Aug 2005 22:44:46 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <mailman.1123537013.20478@xxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <516F50407E01324991DD6D07B0531AD55F66C4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> None None <mailman.1123537013.20478@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Magenheimer, Dan (HP Labs Fort Collins) wrote:
Moving this to xen-ia64-devel...

I think it would be great if we could all start working
together on getting the virtual drivers working (for both
VTI and non-VTI), [..]
Any suggestions on how to divide up this work and

Hi Dan, I posted two patch series today that might be interesting:

The first series is a bunch of include file cleanups similar to what Matt Chapman posted.

The second is a build hook + sparse tree for building xen drivers against unmodified linux.

The status is that it compiles ok, but doesn't work yet (although an earlier version of the same code worked several months ago). We just wanted to get community feedback as quickly as possible.

What we have not figured out is, how to handle the case where the
netfront driver tries to transfer the ownership of a page to another domain. It does this by writing to the phys_to_machine_mapping[] array.

While we can easily map the phys_to_machine table into a VMX guest, it's not clear that:

a) allowing the guest to modify it is safe
b) How should device models (qemu-dm) handle this. Right now it maps all
   of guest physical upfront and is not notified when phys_to_machine
   mapping changes.


Xen-ia64-devel mailing list

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