From: "Tom Cranbrook" <tcranbrook@australia.edu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
tcranbrook@australia.edu, Rik van Riel <riel@redhat.com>,
"Mark A. Williamson" <mark.williamson@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.netIan.Pratt@cl.cam.ac.uk
Subject: Re: Mixing patches
Date: Wed, 06 Oct 2004 14:42:04 -0400 [thread overview]
Message-ID: <416517b4.32a4.0@australia.edu> (raw)
>I haven't looked at the patch, but it sounds like it would want
>to do some pretty gross stuff.
>
>As a quick way to apply the patch, you might want to take a look
>at the fakei386xen script in tools/misc. It basically renames
>arch xen to arch i386 so the patch without modification. I wrote
>it to enable me to build an external module supplied with a very
>dumb Makefile.
>
>
Well, the script certainly ends up the equivilant of my first suggestion,
but a number of the files the w4l patch expects are gone. This is a list
of files that it touches:
patching file kernel/sched.c
patching file mm/vmscan.c
patching file arch/i386/Kconfig
patching file arch/i386/kernel/apm.c
patching file arch/i386/kernel/cpu/common.c
patching file arch/i386/kernel/entry.S
patching file arch/i386/kernel/head.S
patching file arch/i386/kernel/process.c
patching file arch/i386/kernel/signal.c
patching file arch/i386/kernel/vm86.c
patching file arch/i386/Makefile
patching file arch/i386/mki/Makefile
patching file arch/i386/mki/mki.c
patching file arch/i386/mm/fault.c
patching file include/asm-i386/desc.h
patching file include/asm-i386/mki.h
patching file include/asm-i386/mkiversion.h
patching file include/asm-i386/segment.h
patching file include/asm-i386/thread_info.h
patching file include/linux/init_task.h
patching file include/linux/sched.h
Most of this seems to be hooks to a branch added to arch/i386 called
mki-adaptor in a second pacth. This appears to be the interface to
netraverse's binary.
Did all the i386 specific stuff move to the xen kernel? I thought that the
idea of paravirtualization was the simularity between the abstraction and
the hardware. Are these files things that have been moved to the xen
kernel and abstracted out of the domain environment?
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next reply other threads:[~2004-10-06 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 18:42 Tom Cranbrook [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-05 22:27 Mixing patches Tom Cranbrook
2004-10-06 6:32 ` Ian Pratt
2004-10-04 17:03 Tom Cranbrook
2004-10-05 2:33 ` Rik van Riel
2004-10-02 16:26 Tom Cranbrook
2004-10-02 17:01 ` Mark A. Williamson
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=416517b4.32a4.0@australia.edu \
--to=tcranbrook@australia.edu \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=riel@redhat.com \
--cc=xen-devel@lists.sourceforge.netIan.Pratt \
/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.