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-devel] [PATCH 2/3] remove saving/restoring method in Xend.

To: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 2/3] remove saving/restoring method in Xend.
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 23 Apr 2009 10:01:02 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ross Philipson <Ross.Philipson@xxxxxxxxxx>, Kouya Shimura <kouya@xxxxxxxxxxxxxx>
Delivery-date: Thu, 23 Apr 2009 02:01:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090423163429.9197.27C06F64@xxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnD7WnZdzIpjnYBRUuxL97e8vfLVAABJzs3
Thread-topic: [Xen-devel] [PATCH 2/3] remove saving/restoring method in Xend.
User-agent: Microsoft-Entourage/
On 23/04/2009 09:27, "Yuji Shimada" <shimada-yxb@xxxxxxxxxxxxxxx> wrote:

> OK, I understand that my patches are also big. But I'm worried about
> one problem for Xen 3.4. The problem is that devices are deassigned
> before the reset on current Xen. Dom0 memory may be broken by DMA if
> the problem is not fixed.
> My patches fix the problem. I mean that devices are deassigned after
> the reset with my patches.
> I can work on making the patch just changing order of resetting/
> deassigning devices if you need the fix for Xen 3.4.

If we stick with the existing pciback mechanisms and interfaces for 3.4
(which is preferable at this point) will we simply break 3.4 branch as soon
as the new pciback patches go into linux-2.6.18-xen when 3.5 opens? Or is
there a story on backward compatibility between different pciback/xend

 -- Keir

Xen-devel mailing list