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

Re: [Xen-devel] Re: PCI BAR register space written with garbage in HVM

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: PCI BAR register space written with garbage in HVM guest.
From: Dan Gora <dan.gora@xxxxxxxxx>
Date: Thu, 18 Mar 2010 16:56:09 -0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 18 Mar 2010 12:57:12 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=RXbFl3PrIivFLhfxp3lVcxO2JLg3XwTWC/IRz4He7/E=; b=kBRDoFepjUJmrUzPbVi9dc8gFJWNNpI6h94Y477f3VpsfkLMe08HPw10jK3wZGxMNw +6sCFGIdZcg7ecJB7f+0lRHLM6JwICFPsWL7nVcqIrth2xQTk/hNxn45VxhKtBoIqeu4 63scxsvaAXZKZNVZqeV1f1wd6m5OOgcwAuzWk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=f7bk3zMNWhBUA51Fz9dTqUYl/ixyrBB/HV/3evaY0GwfNrKzk85/8Iazqzcj7dA3Ye ueky53Gbe8XPSYKOWWzEA8LiGgL8n7531imRk5CobNJ+rdemBdk4Selu3OfoNriUYM2U IKAbRAvlba+RjG1PfAnOqkH5hzr5EVM0ryHY4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100318181008.GA32657@xxxxxxxxxxxxxxxxxxx>
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: <4779de451003151809n6cec813dp32d77fee34b1bda2@xxxxxxxxxxxxxx> <4779de451003161714x45dbca6dh80a9eed56e4fb0c2@xxxxxxxxxxxxxx> <4779de451003171914u2f8da58etc698f07dc91c853f@xxxxxxxxxxxxxx> <20100318143207.GF14445@xxxxxxxxxxxxxxxxxxx> <4779de451003181127m210171e9xc5fc4ff1772f4782@xxxxxxxxxxxxxx> <20100318181008.GA32657@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Mar 18, 2010 at 3:10 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> That is not what I expected, but I am glad to hear that it
> makes it possible for you to continue with your project.
>

yeah me either.. :)

> It is good to know that the failure path is contained in the r8169
> implementation. If it wouldn't be too much trouble, could you send an
> e-mail to the QEMU mailing list this thread and your solution in
> case there is somebody there itching to work on this.

done, but there doesn't seem to be much uptake there..

thanks
dan

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