All of lore.kernel.org
 help / color / mirror / Atom feed
From: tam00 <tam00@comcast.net>
To: Steven Smith <sos22-xen@srcf.ucam.org>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com,
	sos22@srcf.ucam.org
Subject: Re: unmodified_drivers build fails in latest unstable version
Date: Thu, 09 Nov 2006 18:57:03 -0600	[thread overview]
Message-ID: <4553CE5F.7060804@comcast.net> (raw)
In-Reply-To: <20061109163519.GA3829@cam.ac.uk>

Steven,

I was trying to build inside Dom0, which is a Xen aware kernel.  Am I 
supposed to boot back into SusE and build the drivers there?  Perhaps, I
need to build the drivers in the VM itself? 

Also, am I using the proper syntax for the build?  And has the build 
been known to work on an x64 based system?

Thanks for your help.



Steven Smith wrote:
>> SLES10x64:/tmp/xen-unstable.hg/unmodified_drivers/linux-2.6 # 
>> ./mkbuildtree Defaulting to this machine's architecture, x86_64, for 
>> linking.
>> This may be overridden on the command line (i386,x86_64,ia64).
>> SLES10x64:/tmp/xen-unstable.hg/unmodified_drivers/linux-2.6 # make -C 
>> /lib/modules/2.6.16.29-xen/build M=$PWD modules
>>     
> Is 2.6.16.29-xen a native kernel?  The unmodified drivers are intended
> to be loaded into non-Xen-aware kernels running in fully-virtualised
> HVM domains.  They're unlikely to work if compiled against a Xen aware
> kernel, and wouldn't be terribly useful in that case, since the
> ordinary drivers do the same thing better.
>
> Steven.
>   

  reply	other threads:[~2006-11-10  0:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 13:13 [PATCH] Crash VMX when guest NMI Li, Xin B
2006-11-08 13:23 ` unmodified_drivers build fails in latest unstable version tam00
2006-11-09 16:35   ` Steven Smith
2006-11-10  0:57     ` tam00 [this message]
2006-11-08 15:00 ` [PATCH] Crash VMX when guest NMI Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4553CE5F.7060804@comcast.net \
    --to=tam00@comcast.net \
    --cc=sos22-xen@srcf.ucam.org \
    --cc=sos22@srcf.ucam.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.