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

Re: [Xen-devel] RE: dom0/xen boot problem



On Fri, Feb 25, 2011 at 11:54:38AM -0800, Kay, Allen M wrote:
> > 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.

We thought about it, but then 2.6.38 has so many neat stuff in it that it just 
seems easier to do it
on top of 2.6.38.

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

Or better, use git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git 
#master

(as it is the "stable" version). The devel/next-2.6.38 is a kitchensink right 
now.
> 
> I will give this a try.

Thank you!

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

Received: from rrsmsx606.amr.corp.intel.com (10.31.1.130) by
        orsmsx605.amr.corp.intel.com (10.22.226.10) with Microsoft SMTP Server
        (TLS) id 8.2.254.0; Thu, 24 Feb 2011 07:48:44 -0800
Received: from fmsmga002.fm.intel.com (10.253.24.26) by
        RRSMSX606-1.rr.intel.com (10.31.1.130) with Microsoft SMTP Server id
        8.2.254.0; Thu, 24 Feb 2011 08:48:43 -0700
Received: from fmsmga101.fm.intel.com ([10.1.193.65])  by
        fmsmga002-1.fm.intel.com with ESMTP; 24 Feb 2011 07:48:43 -0800
Received: from lists.colo.xensource.com (HELO lists.xensource.com)
        ([70.42.241.110])  by mga01.intel.com with ESMTP;
        24 Feb 2011 07:48:43 -0800
Received: from localhost ([127.0.0.1] helo=lists.colo.xensource.com)    by
        lists.xensource.com with esmtp (Exim 4.43)      id 1PsdQo-0007ZF-My;
        Thu, 24 Feb 2011 07:48:42 -0800
Received: from spam.xensource.com ([70.42.241.90])      by lists.xensource.com 
with
        esmtp (Exim 4.43) id 1PsdQN-0007SR-9k   for
        xen-devel@xxxxxxxxxxxxxxxxxxx; Thu, 24 Feb 2011 07:48:15 -0800
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by
        spam.xensource.com with ESMTP id n0VgWBd8ink2WV4I       (version=TLSv1
        cipher=AES256-SHA bits=256 verify=NO)
        for     <xen-devel@xxxxxxxxxxxxxxxxxxx>; 
        Thu, 24 Feb 2011 07:48:14 -0800 (PST)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125])     
by
        rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP
        id      p1OFm9d4027739
        (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
        Thu, 24 Feb 2011 15:48:11 GMT
Received: from acsmt355.oracle.com (acsmt355.oracle.com [141.146.40.155])       
by
        rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id
        p1OFm8ip020467; Thu, 24 Feb 2011 15:48:08 GMT
Received: from abhmt015.oracle.com by acsmt353.oracle.com       with ESMTP id
        1083839291298562413; Thu, 24 Feb 2011 07:46:53 -0800
Received: from phenom (/209.6.55.207) by default (Oracle Beehive Gateway v4.0)
        with ESMTP ; Thu, 24 Feb 2011 07:46:53 -0800
Received: by phenom (Postfix, from userid 1000) id 94C46445B; Thu, 24 Feb 2011
        10:46:52 -0500 (EST)
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
To: Rafal Wojtczuk <rafal@xxxxxxxxxxxxxxxxxxxxxx>
CC: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Sender: "xen-devel-bounces@xxxxxxxxxxxxxxxxxxx"
        <xen-devel-bounces@xxxxxxxxxxxxxxxxxxx>
Content-Class: urn:content-classes:message
Date: Thu, 24 Feb 2011 07:46:52 -0800
Subject: Re: [Xen-devel] tip of jeremy/xen.git xen/next-2.6.38 fails to compile
Thread-Topic: [Xen-devel] tip of jeremy/xen.git xen/next-2.6.38 fails to
        compile
Thread-Index: AcvUOlEJ5+J/nqwTSACVDrVlT4pwRA==
Message-ID: <20110224154652.GB6893@xxxxxxxxxxxx>
References: <20110224120056.GC2221@email>
List-Help: <mailto:xen-devel-request@xxxxxxxxxxxxxxxxxxx?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
        <mailto:xen-devel-request@xxxxxxxxxxxxxxxxxxx?subject=subscribe>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
        <mailto:xen-devel-request@xxxxxxxxxxxxxxxxxxx?subject=unsubscribe>
In-Reply-To: <20110224120056.GC2221@email>
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: RRSMSX606.amr.corp.intel.com
X-MS-Has-Attach: 
X-Auto-Response-Suppress: All
X-MS-TNEF-Correlator: 
x-ironport-av: E=Sophos;i="4.62,219,1297065600"; d="scan'208";a="833931283"
x-ironport-anti-spam-filtered: true
x-ironport-anti-spam-result: 
Al8BAE0MZk1GKvFukWdsb2JhbACmPwEBAgkLCgcRBCC9dYVgBIUQhXc
x-virus-scanned: by bsmtpd at xensource.com
x-beenthere: xen-devel@xxxxxxxxxxxxxxxxxxx
x-mailman-version: 2.1.5
list-id: Xen developer discussion <xen-devel.lists.xensource.com>
list-post: <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx>
errors-to: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
x-asg-debug-id: 1298562494-6d03170e0001-8pertM
x-barracuda-envelope-from: konrad@xxxxxxxxxxxx
x-asg-orig-subj: Re: [Xen-devel] tip of jeremy/xen.git xen/next-2.6.38 fails
        to      compile
x-barracuda-connect: rcsinet10.oracle.com[148.87.113.121]
x-barracuda-start-time: 1298562494
x-barracuda-url: http://spam.xensource.com:8000/cgi-mod/mark.cgi
user-agent: Mutt/1.5.20 (2009-06-14)
x-barracuda-spam-score: 0.00
x-barracuda-spam-status: No, SCORE=0.00 using per-user scores of
        TAG_LEVEL=3.5   QUARANTINE_LEVEL=6.0 KILL_LEVEL=1000.0
        tests=UNPARSEABLE_RELAY
x-source-ip: acsmt355.oracle.com [141.146.40.155]
x-ct-refid: str=0001.0A090206.4D667DB9.0070:SCFMA4539814,ss=1,fgs=0
x-auth-type: Internal IP
x-barracuda-spam-report: Code version 3.2, rules version 3.2.2.56272    Rule
        breakdown below pts rule name              description  ----
        ----------------------  
--------------------------------------------------
        0.00 UNPARSEABLE_RELAY Informational: message has unparseable
        relay   lines
x-barracuda-encrypted: AES256-SHA
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
> 
> 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

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


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


 


Rackspace

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