| |
|
 |
|
 |
|
|
|
| |
|
|
xen-merge
RE: [Xen-merge] xen-merge mailing list
> I've started by simply creating an i386 sub-arch and moving bits
over.
> (nowhere near compiling, just trying to get a handle on how
> much work there is and how it will split out). I use this
> dumb script that basically diffs arch/xen/i386/* against
> arch/i386/*, for example, to generate the actual changes.
> This could literally go file by file with an eye for basic
> cleanups. We've had a few suggestions about the cleanups,
> such as ifdefs based on some config which essentially says
> physical machine, to effectively comment code out for Xen, or
> actual inlines and macros that are populated by the sub-arch.
> Likely both are options depending on the specifics. For
> example, x86_64 has method for alternative apic, I wonder if
> such a scheme might not be useful for i386 as well?
Is it worth us setting up one or more Linux 2.6 mercurial tress on
xenbits that we can use to show each other what we're doing? Patches for
this sort of thing aren't easy to read. (Just send me an ssh v2 public
key to set up 'push' access).
BTW, the people currently on this list are:
ian.pratt@xxxxxxxxxxxx
christian.limpach@xxxxxxxxxxxx
keir.fraser@xxxxxxxxxxxx
vincent.hanquez@xxxxxxxxxxxx
chrisw@xxxxxxxx
jun.nakajima@xxxxxxxxx
mbligh@xxxxxxxxxx
ak@xxxxxxx
kurt@xxxxxxxxxx
riel@xxxxxxxxxx
> > Anyone interested in a trip to Cambridge to work on this
> stuff? It's a
> > nice time of year for a visit -- nice warm summer evenings
> sitting in
> > beer gardens...
>
> Hmm, quite tempting.
Give it some serious thought...
Cheers,
Ian
_______________________________________________
Xen-merge mailing list
Xen-merge@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-merge
|
|
|
| |
|
Home