Re: [Xen-devel] How to build vmlinuz-2.6.29-rc5-tip ?

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

Did all stuf from scratch

rm -fr linux.tree.git
mkdir linux.tree.git || exit -1
cd linux.tree.git

git init
# Add Linus's tree as a remote
git remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

# Add the -tip tree as a remote

git remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
git remote update

. . . . .

Updating tip
remote: Counting objects: 19569, done.
remote: Compressing objects: 100% (7482/7482), done.
remote: Total 18172 (delta 14981), reused 12843 (delta 10122)
Receiving objects: 100% (18172/18172), 3.54 MiB | 109 KiB/s, done.
Resolving deltas: 100% (14981/14981), completed with 1157 local objects.
From git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen
 * [new branch]      acpi/map   -> tip/acpi/map
 * [new branch]      mainline/mm -> tip/mainline/mm
 * [new branch]      mainline/net -> tip/mainline/net
 * [new branch]      master     -> tip/master
 * [new branch]      push/xen/dom0/core -> tip/push/xen/dom0/core
 * [new branch]      tip/fixups -> tip/tip/fixups
 * [new branch]      x86/apic   -> tip/x86/apic
 * [new branch]      x86/cpa    -> tip/x86/cpa
 * [new branch]      x86/unify  -> tip/x86/unify
 * [new branch]      x86/unify-base -> tip/x86/unify-base
 * [new branch]      x86/unify-irq -> tip/x86/unify-irq
 * [new branch]      x86/unify-irq-base -> tip/x86/unify-irq-base
 * [new branch]      x86/unify-kmemcheck -> tip/x86/unify-kmemcheck
 * [new branch]      x86/unify-kmemcheck-base -> tip/x86/unify-kmemcheck-base
 * [new branch]      x86/untangle -> tip/x86/untangle
 * [new branch]      x86/untangle2 -> tip/x86/untangle2
 * [new branch]      xen/core   -> tip/xen/core
 * [new branch]      xen/dev-evtchn -> tip/xen/dev-evtchn
 * [new branch]      xen/dom0/apic -> tip/xen/dom0/apic
 * [new branch]      xen/dom0/backend/blkback -> tip/xen/dom0/backend/blkback
 * [new branch]      xen/dom0/backend/core -> tip/xen/dom0/backend/core
 * [new branch]      xen/dom0/backend/netback -> tip/xen/dom0/backend/netback
 * [new branch]      xen/dom0/core -> tip/xen/dom0/core
 * [new branch]      xen/dom0/hackery -> tip/xen/dom0/hackery
 * [new branch]      xen/dom0/mtrr -> tip/xen/dom0/mtrr
 * [new branch]      xen/dom0/pci -> tip/xen/dom0/pci
 * [new branch]      xen/dom0/swiotlb -> tip/xen/dom0/swiotlb
 * [new branch]      xen/dom0/xenfs -> tip/xen/dom0/xenfs
 * [new branch]      xen/frontend/blkfront -> tip/xen/frontend/blkfront
 * [new branch]      xen/fs     -> tip/xen/fs
 * [new branch]      xen/hg-queue-import -> tip/xen/hg-queue-import
 * [new branch]      xen/irq    -> tip/xen/irq
 * [new branch]      xen/master -> tip/xen/master
 * [new branch]      xen/pvhvm  -> tip/xen/pvhvm
 * [new branch]      xen/xenbus -> tip/xen/xenbus

 . . . . . . . . .

So, new branch obtained.

As far as i understood Ian :-

git checkout -b xen-latest tip/xen/master

"make menuconfig" still doesn't show options for Xen Dom0 support

Something was done wrong.

 Option "[*] Enable Xen privileged domain support"   is abcent     


************************************************************************

The most recent picture on Mercurial (after applying patch queue)

************************************************************************
  --- Paravirtualized guest support                                                           
   
      [*]   Xen guest support                                                    
      (32)    Maximum allowed size of a domain in gigabytes                      
      [*]     Enable Xen debug and tuning parameters in debugfs                  
      [*]     Enable Xen privileged domain support                  

--- On Tue, 2/17/09, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:

From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] How to build vmlinuz-2.6.29-rc5-tip ?
To: "bderzhavets@xxxxxxxxx" <bderzhavets@xxxxxxxxx>
Cc: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Tuesday, February 17, 2009, 3:28 AM

On Tue, 2009-02-17 at 03:15 -0500, Boris Derzhavets wrote:
> 
> root@ServerXen331:/usr/src/linux.trees.git# git checkout -b tip-latest
> tip/master
> warning: You appear to be on a branch yet to be born.
> warning: Forcing checkout of tip/master.
> Checking out files: 100% (26687/26687), done.
> Branch tip-latest set up to track remote branch
> refs/remotes/tip/master.
> Switched to a new branch "tip-latest"
> 
> 
> "make menuconfig" still  doesn't show options for Xen Dom0
support.
> 

In Jeremy's announcement of the git tree he said:

> 
> If you want to get started, either xen/dom0/hackery or xen/master are 
> the places to
 start;
> 
> xen/dom0/hackery
>     Master dom0 branch.  This is all the interesting dom0-related topic
>     branches merged together, and is a superset of xen/master.
> xen/master
>     Master domU branch, with everything interesting merged in.  This is
>     likely to be more stable and closer to upstream than dom0/hackery

So I think you want the xen/dom0/hackery branch which would become
tip/xen/dom0/hackery in your repo (and xen/master=>tip/xen/master not
tip/master).

Ian.


_______________________________________________
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