From: "Reese Faucette" <reese@myri.com>
To: xen-devel@lists.xensource.com
Subject: Re: Xen 3.0.3 Kernel 2.6.18
Date: Tue, 2 Jan 2007 10:32:46 -0800 [thread overview]
Message-ID: <055d01c72e9c$66e44400$58c31fac@bart> (raw)
In-Reply-To: 459A948D.76E4.0078.0@novell.com
Claes Lindblom asked:
>Where can I get working patches for the latest kernel 2.6.18.x?
Atsushi SAKAI replied:
> It is better to see FC6 SRPM.
> http://download.fedora.redhat.com/pub/fedora/linux/core/development/source/SRPMS/
So, I downloaded this SRPM and applied all the patches. I modified
buildconfigs/mk.linux-2.6-xen to say:
LINUX_VER = 2.6.18.3
then "make world"
I get lots of errors about duplicate definitions, e.g. alt_instr and
LOCK_PREFIX from
linux-2.6-xen-sparse/include/asm-x86_64/mach-xen/asm/system.h
I tried fixing those piecemeal, but the hits just keep on coming. Should I
not be using 2.6.18.3 ? Is there some other magic incantation I need?
Sorry for what's probably a newb question, but I did search the archives and
googled all over first. I'm trying 2.8.18.1 in parallel with this email,
but my confidence is not high. I have spent a while on this already, but I
am running out of time. I'm racing the deadline for getting out a paper on
Myrinet performance over Xen (it's very good so far with 3.0.3 on 2.6.16)
for the IEEE conference in June.
thanks in advance,
-reese
next prev parent reply other threads:[~2007-01-02 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 16:21 [PATCH 4/4] swiotlb abstraction (e.g. for Xen) Jan Beulich
2007-01-02 16:21 ` Jan Beulich
2007-01-02 16:21 ` Jan Beulich
2007-01-02 18:32 ` Reese Faucette [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-21 11:58 Re: Getting xen to recognise large disks Keir Fraser
2006-11-21 12:14 ` Xen 3.0.3 Kernel 2.6.18 Claes Lindblom
2006-11-21 12:25 ` Atsushi SAKAI
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='055d01c72e9c$66e44400$58c31fac@bart' \
--to=reese@myri.com \
--cc=xen-devel@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.