Re: arch/xen is a bad idea

From: Andi Kleen (ak_at_suse.de)
Date: 02/25/05

  • Next message: shabanip: "Re: how to capture kernel panics" 
    Date:	Fri, 25 Feb 2005 16:01:38 +0100
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>

    > Phase 1 is for us to submit a load of patches that squeeze out the low
    > hanging fruit in unifying xen/i386 and i386. Most of these will be
    > strict cleanups to i386, and the result will be to almost halve the
    > number of files that we need to modify.

    Sounds good. I would try to track that for x86-64 too then when
    possible to make the later x86-64 merge easier.

    >
    > The next phase is that we re-organise the current arch/xen as follows:
    >
    > We move the remaining (reduced) contents of arch/xen/i386 to
    > arch/i386/xen (ditto for x86_64). We then move the xen-specific files

    What would these files be?

    > that are shared between all the different xen architectures to
    > drivers/xen/core. I know this last step is a bit odd, but it's the best
    > location that Rusty Russel and I could come up with.
    >
    > At this point, I'd hope that we could get xen into the main-line tree.
    >
    > The final phase is to see if we can further unify more native and xen
    > files. This is going to require some significant i386 code refactoring,
    > and I think its going to be much easier to do if all the code is in the
    > main-line tree so that people can see the motivation for what's going
    > on.

    Hmm, I would prefer to do that during the merge. I'm not sure there
    will be that much push afterwards to unify stuff, and then we might
    be stuck with an inferior setup.

    I don't think it makes much difference for review if the previous
    code is in mainline or not.

    -Andi
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: shabanip: "Re: how to capture kernel panics"

    Relevant Pages

    • Re: kgdb for mainline kernel: core-lite [patch 1/3]
      ... This feature lets gdb hook onto a kernel function to detect loading and ... unloading of modules and preserves module section information for later use ... The one in my tree also apparently works to some ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • [RFC] removal of legacy cdrom drivers (Re: [PATCH] mcdx.c insanity removal)
      ... bar and baz and fairly long expressions. ... if we want to keep the FPOS in the tree. ... Driver is obviously ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [BK] upgrade will be needed
      ... > tree. ... automatic real-time gateway with no license problems. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: arch/xen is a bad idea
      ... > The Xen team still believe that it's best to keep arch/xen, ... I'd hope that we could get xen into the main-line tree. ... This is going to require some significant i386 code refactoring, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test9-mjb1
      ... > scheduler callers profiling ... any e1000 fixes you have, please forward them to me and Intel ... rather than letting them languish in a tree. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)