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: pv_ops dom0 USB fixed

To: "Ian Campbell" <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: pv_ops dom0 USB fixed
From: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
Date: Fri, 12 Dec 2008 11:36:54 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Aviv Grafi <aviv@xxxxxxxxxxxx>
Delivery-date: Fri, 12 Dec 2008 03:37:16 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=8O2dx+M1WM5GUTMWQSLPhURlPlB/+RbxpXC7EpTiPhw=; b=YEPlqYdZym4mBq33zp7M9xOgXDtip5vTzXEzbh+vgI93A0v+2LPJmPDwG+vGbiHtDx CRxVZvdzk2y5ZmFpuh4/1rLHoyqBZ4Z7EjLYB/H2ukwOGQVn0b7XwjRwgtP9KI4ybIxJ wNmReQKY3mpRtfGo1c+lP1lfyKkJW+TaBGcdA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=W75krWm0+AB6Q7dL//+sjyxAsK5RUgb82AAzD4cReo3jk/qldUAo/qxEGkoDH2Yvy5 XU/To8du9OKTKxZ1Y2mKoWImOik044LW5LTtfD4gxLk2jbPq1U3jANQmuN3O1hOtjSx8 fXs/GyaXFwbosmGzluRnWgSC2skh7sT2THAiY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1229080507.25349.33.camel@xxxxxxxxxxxxxxxxxxxxxx>
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: <4940210C.1060401@xxxxxxxx> <1e16a9ed0812111147h3416cbb5uc11a8b9f5f0d0e80@xxxxxxxxxxxxxx> <1229025794.2770.32.camel@xxxxxxxxxxxxxxxxxxxxx> <1e16a9ed0812111220h40e62ee1ma27f48c5207bc735@xxxxxxxxxxxxxx> <49417755.4050703@xxxxxxxx> <1e16a9ed0812111312p2547884cgf4020eb9ea92ddde@xxxxxxxxxxxxxx> <4941930B.2010605@xxxxxxxx> <1e16a9ed0812111427i3626b94cu7ce56550d654227a@xxxxxxxxxxxxxx> <f4527be0812120112y13e74752kbd3d17d7daa98848@xxxxxxxxxxxxxx> <1229080507.25349.33.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Dec 12, 2008 at 11:15 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Fri, 2008-12-12 at 09:12 +0000, Andrew Lyon wrote:
>> (XEN) Xen-e820 RAM map:
>> (XEN)  0000000000000000 - 000000000009ec00 (usable)
>> (XEN)  00000000000f0000 - 0000000000100000 (reserved)
>> (XEN)  0000000000100000 - 00000000cfdff800 (usable)
>> (XEN)  00000000cfdff800 - 00000000cfe53c00 (ACPI NVS)
>> (XEN)  00000000cfe53c00 - 00000000cfe55c00 (ACPI data)
>> (XEN)  00000000cfe55c00 - 00000000d0000000 (reserved)
>> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
>> (XEN)  00000000fec00000 - 00000000fed00400 (reserved)
>> (XEN)  00000000fed20000 - 00000000feda0000 (reserved)
>> (XEN)  00000000fee00000 - 00000000fef00000 (reserved)
>> (XEN)  00000000ffb00000 - 0000000100000000 (reserved)
>> (XEN)  0000000100000000 - 0000000128000000 (usable)
>> BIOS-provided physical RAM map:
>>  Xen: 0000000000000000 - 00000000000a0000 (usable)
>>  Xen: 00000000000a0000 - 0000000000100000 (reserved)
>>  Xen: 0000000000100000 - 000000000087d000 (usable)
>>  Xen: 000000000087d000 - 0000000000fd1000 (reserved)
>>  Xen: 0000000000fd1000 - 00000000ea567000 (usable)
>
> It's only peripherally related (and a bit of a stab in the dark) but
> since you have plenty of host RAM your pseudo-physical addresses overlap
> with the ACPI tables and such so it would be worth trying out the patch
> I just pushed to reserve these. Although I saw actual warnings and you
> don't seem to it's possible there are other failures due to the
> conflicts. Alternatively you could try limiting the domain 0 memory,
> e.g. with dom0_mem=3G on the Xen command line.
>
> Ian.
>
>

I tried with dom0_mem=3G and =1G, neither seems to make any
difference, I also tried libata.force=noncq.

Is it still worth trying your patch?

I followed the instructions on the wiki to download the pv_ops source
tree, what method can I use to update the source to the latest commits
without downloading it all from scratch?

Andy

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