|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] RE: dom0/xen boot problem
> I believe it is already in the Greg KH 2.6.37.x bug-fix branch. But ... we
> don't actually
> have a 2.6.37.x development branch. We do have a 2.6.38 one - wherein the
> patch is present.
I thought xen/next-2.6.37 branch under
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy.xen.git is the 2.6.37
development branch.
Is xen/next-2.6.38 under
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy.xen.git the development
branch for 2.6.38?
Base on the attached email from you, that too also has missing bug fixes. It
sounds the best pvops tree to use is:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
devel/next-2.6.38
I will give this a try.
-----Original Message-----
From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx]
Sent: Friday, February 25, 2011 11:36 AM
To: Kay, Allen M; Jeremy Fitzhardinge
Cc: Stefano Stabellini; Keir Fraser; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: dom0/xen boot problem
On Fri, Feb 25, 2011 at 11:22:24AM -0800, Kay, Allen M wrote:
> Jeremy/Konrad,
>
> Thanks for Stefano's help, dom0/xen boot failure on my Sandybridge desktop
> SDP has been isolated to the following patch that is missing in both 2.6.32
> and 2.6.37 PVOPS branches. According to PVOPS wiki 2.6.32 and 2.6.37 are
> suppose to be active branches. Can you back port this patch to both 2.6.32
> and 2.6.37 branches?
I believe it is already in the Greg KH 2.6.37.x bug-fix branch. But ... we
don't actually
have a 2.6.37.x development branch. We do have a 2.6.38 one - wherein the
patch is present.
Under 2.6.32.x.. Jeremy, I've stuck this patch and another in
for-2.6.32/bug-fixes. Could you pull it please?
>
> I'm surprised that I'm the only person encountering this problem. Not being
> able use either printk or xen_raw_printk in
> xen_build_dynamic_phys_to_machine() does not help debugging either. I was
> going to save max_pfn in a global variable and then print it out later in
> xen_build_mfn_list_list() before Stefano pointed out this patch. :-)
Oh man, what a headache.
>
> Allen
>
> ----- missing patch -------
>
> commit cf04d120d9413de581437cf9a29f138ec1178f65
> Author: Stefan Bader <stefan.bader@xxxxxxxxxxxxx>
> Date: Thu Jan 27 10:03:14 2011 -0500
>
> xen/p2m: Mark INVALID_P2M_ENTRY the mfn_list past max_pfn.
>
> In case the mfn_list does not have enough entries to fill
> a p2m page we do not want the entries from max_pfn up to
> the boundary to be filled with unknown values. Hence
> set them to INVALID_P2M_ENTRY.
>
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
>
> ----- active pvops branches from pvops wiki page -----
>
> Current active branches are:
>
> xen/stable-2.6.32.x - this is the long term maintained branch, tracking
> upstream kernel.org 2.6.32.x stable updates. This branch has Xen dom0 patches
> added. This is the recommended branch for most users. Changelog:
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/stable-2.6.32.x
> .
> xen/next-2.6.32 - This is a branch for next 2.6.32 version and gets migrated
> to the stable branch once automatic tests have succeeded. Changelog:
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/next-2.6.32
> .
> xen/next-2.6.37 - this is the current development branch based on Linux
> 2.6.37. Changelog:
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/next-2.6.37
> .
--- Begin Message ---
On Thu, Feb 24, 2011 at 01:00:56PM +0100, Rafal Wojtczuk wrote:
> Hello,
> it looks like some patches are missing in the current xen/next-2.6.38. E.g.
> IRQF_FORCE_RESUME is used but not defined.
Brave soul :-)
For right now take my tree:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/next-2.6.38
It has the dom0 + lots of patches (including the pciback and netback).
No blkback yet.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
--- End Message ---
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|