[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86/32on64: fix physical addressrestriction

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Thu, 12 Jun 2008 16:46:52 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 12 Jun 2008 08:47:01 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 12.06.08 17:06 >>>
>I tweaked this before checking in as c/s 17836. Please take a look and see
>whether it looks okay to you. If so I'll also backport to xen-3.2-testing.

Looks good - even better, because the calculation is now more correct - I
hadn't realized so far that the old calculation didn't account for the 2M
hole right below 4G.

Jan


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

References:
- [Xen-devel] [PATCH] x86/32on64: fix physical address restriction
  - From: Jan Beulich
- Re: [Xen-devel] [PATCH] x86/32on64: fix physical address restriction
  - From: Keir Fraser

Prev by Date: Re: [Xen-devel] [PATCH, resend] x86: remove use of per-domain lock from page table entry handling
Next by Date: Re: [Xen-devel] [PATCH] reduce useless output from 'd' consolecommand
Previous by thread: Re: [Xen-devel] [PATCH] x86/32on64: fix physical address restriction
Next by thread: [Xen-devel] [PATCH] x86: defer a panic call during dom0 construction
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.