WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] pv_ops polish: remove fsys.S changes

Hi. I created the new branch xen-ia64-domu-minimal-2008mar06
from the c/s b5d0753da4b1d67490efa63c790024351add42a0.
Please switch to the new branch.
I suppose the new branch is what you want.
It doesn't include any dom0 stuff, fsys.S and gate page stuff.

On Fri, Mar 14, 2008 at 06:16:03PM +0800, Dong, Eddie wrote:
> Isaku Yamahata wrote:
> > Hi Eddie.
> > Thank you for your patch.
> > the change is already isolated as the commit of
> > d81f732b0d57371bfc220b1a1027ab18ea9a5265.
> > So what we need to do is just dropping the change set.
> > The same would apply to the gate page paravirtualization change set.
> > I'll take care of it.
> > 
> > Do you have any other changesets to be dropped for minimal domU?
> > 
> 
> Commit a07b265c618c279a84bac8f75f5acba1c1646200 is quit intrusive, it
> removed code
> from entry.S to a new file switch_entry.S and create 1000 lines of
> patch.
> 
> At least we stay in original file, not? 

At least xen/ia64 needs to paravirtualize ia64_swtich_to,
ia64_leave_syscall and ia64_leave_kernel.
The discussion for hand written assembly code indicates that single
source and multiple compile.
I think the clean way to do for those three functions is to split out
them from entry.S. Cluttering out entry.S by ifdef would be uglry.
Do you have better idea?

-- 
yamahata

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel