From: Miroslav Ruda <ruda@ics.muni.cz>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, Steven Hand <Steven.Hand@cl.cam.ac.uk>
Subject: Re: openafs not supported?
Date: Wed, 09 Mar 2005 16:49:25 +0100 [thread overview]
Message-ID: <422F1B05.4030906@ics.muni.cz> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3539@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
> We've used openafs with 2.4.29-xen0 without problems. I seem to recall
> that getting it to build against xen/i386 rather than plain i386 was
> somewhat tricky, as setting ARCH=xen was insufficient due to a busted
> Makefile. I think I resorted to renaming arch/xen to arch/i386 and the
> same for include/asm-xen.
I wish it's so easy. However, renaming of include/asm-xen to include/asm-i386
doesn't work, because some include files from asm-xen (param.h for example)
include ../asm-i386/ files too :-) Moreover, my guess is that it's still not
sufficient, see bellow.
Openafs' Makefile creates symlinks to several kernel-source/include directories
including asm-i386 (others are include/net, include/linux, include/asm).
I was easily able to change this makefile to use asm-xen instead and I was able
to compile openafs with such setup. And this version
creates oops I have sent to xen mailing list. However, I don't see any other
usage of kernel source and therefore I don't understand what is missing to
create "xen-enabled" binaries.
--
Mirek Ruda
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-09 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 14:45 openafs not supported? Ian Pratt
2005-03-09 15:49 ` Miroslav Ruda [this message]
2005-03-09 15:54 ` Kris Van Hees
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 16:58 Ian Pratt
2005-03-09 17:19 ` Kris Van Hees
2005-03-09 22:39 ` Miroslav Ruda
2005-03-09 23:06 ` Kris Van Hees
2005-03-09 15:56 Ian Pratt
2005-03-09 16:54 ` Miroslav Ruda
2005-03-01 14:55 Miroslav Ruda
2005-03-02 14:35 ` Steven Hand
2005-03-02 15:52 ` Miroslav Ruda
2005-03-03 15:05 ` Miroslav Ruda
2005-03-09 13:20 ` Miroslav Ruda
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=422F1B05.4030906@ics.muni.cz \
--to=ruda@ics.muni.cz \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.