please pull xen-ia64-unstable

please pull xen-ia64-unstable

[Alex Williamson]

Hi Keir,

   Please pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

This is sync'd up to xen-unstable cset 9375.  Updates include hypercall
security fixes, domU reboots, VTI domain destruction fixes, code
cleanups, and building of xen_sysfs.  Thanks,

	Alex


PS - VTI qemu fixes touching common code are not included in the tree
since we have disagreement whether this interim change is meant for
upstream.

-- 
Alex Williamson                             HP Linux & Open Source Lab

please pull xen-ia64-unstable

[Alex Williamson]

Hi Keir,

   Please pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

This is sync'd up to xen-unstable cset 9267.  Updates include the
removal of many compiler warnings in the ia64 xen tree, many bug fixes,
and we are now able to destroy domains and reclaim their memory.
Thanks,

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab

Re: please pull xen-ia64-unstable

[Keir Fraser]

On 17 Mar 2006, at 23:36, Alex Williamson wrote:

>
> This is sync'd up to xen-unstable cset 9267.  Updates include the
> removal of many compiler warnings in the ia64 xen tree, many bug fixes,
> and we are now able to destroy domains and reclaim their memory.
> Thanks,

Done.

  K.

Re: please pull xen-ia64-unstable

[Alex Williamson]

On Sat, 2006-03-18 at 10:11 +0000, Keir Fraser wrote:
> On 17 Mar 2006, at 23:36, Alex Williamson wrote:
> 
> >
> > This is sync'd up to xen-unstable cset 9267.  Updates include the
> > removal of many compiler warnings in the ia64 xen tree, many bug fixes,
> > and we are now able to destroy domains and reclaim their memory.
> > Thanks,
> 
> Done.

Keir,

   We seem to have lost a few new empty files in the merge.  Could you
please touch and hg add these empty files:

xen/include/asm-ia64/linux-null/linux/mmzone.h
xen/include/asm-ia64/linux-null/linux/page-flags.h

Thanks,

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Includes catchup with various xen-unstable changes through
9023, various bug fixes and cleanups, some preparatory work
for moving domain0 from p==m to VP, and default to SMP host.

Thanks,
Dan

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Includes catchup with various xen-unstable changes through
8589 and some bug fixes (including getting SMP working again).

Thanks,
Dan

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Includes some bug fixes plus changes to allow Xen/ia64
to build with latest unstable.

Thanks,
Dan

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Sorry.  I see you have already deleted the code.
If/when it needs to go back in, we will put the
code elsewhere.

Thanks,
Dan 

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] 
> Sent: Wednesday, December 21, 2005 12:16 PM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel list; xen-ia64-devel@lists.xensource.com
> Subject: Re: Please pull xen-ia64-unstable
> 
> 
> On 21 Dec 2005, at 18:48, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> 
> > Please pull
> >
> > http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> >
> > Included are critical bug fixes for domU and SMP,
> > ia64 sync with a recent change in evtchn stuff,
> > plus many other minor bug fixes and enhancements.
> 
> Where does acpi_table_count_madt (in xen/drivers/acpi/table.c) come 
> from? It doesn't appear in the Linux sources as far as I can tell.
> 
> That file is kept in sync with its Linux parent, so you'll 
> need to move 
> that function to arch/ia64 (if you really need it at all).
> 
> Taken for now, but it needs to be moved/deleted.
> 
>   -- Keir
> 
> 

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Included are critical bug fixes for domU and SMP,
ia64 sync with a recent change in evtchn stuff,
plus many other minor bug fixes and enhancements.

Thanks,
Dan

Re: Please pull xen-ia64-unstable

[Keir Fraser]

On 21 Dec 2005, at 18:48, Magenheimer, Dan (HP Labs Fort Collins) wrote:

> Please pull
>
> http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
>
> Included are critical bug fixes for domU and SMP,
> ia64 sync with a recent change in evtchn stuff,
> plus many other minor bug fixes and enhancements.

Where does acpi_table_count_madt (in xen/drivers/acpi/table.c) come 
from? It doesn't appear in the Linux sources as far as I can tell.

That file is kept in sync with its Linux parent, so you'll need to move 
that function to arch/ia64 (if you really need it at all).

Taken for now, but it needs to be moved/deleted.

  -- Keir

Re: Please pull xen-ia64-unstable

[Masaki Kanno]

Hi Keir, Dan,

Sorry.

>On 21 Dec 2005, at 18:48, Magenheimer, Dan (HP Labs Fort Collins) wrote:
>
>> Please pull
>>
>> http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
>>
>> Included are critical bug fixes for domU and SMP,
>> ia64 sync with a recent change in evtchn stuff,
>> plus many other minor bug fixes and enhancements.
>
>Where does acpi_table_count_madt (in xen/drivers/acpi/table.c) come 
>from? It doesn't appear in the Linux sources as far as I can tell.

Yes, It's the function that I created it.

>That file is kept in sync with its Linux parent, so you'll need to move 
>that function to arch/ia64 (if you really need it at all).
>
>Taken for now, but it needs to be moved/deleted.

I see.
I will make the patch that moves the function. 

>
>  -- Keir
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel

Best Regard,
 Kan

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull
 
http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Included are your grant table merge, serial input,
an initial physinfo implementation (so xm info now
works), better ACPI emulation, improved PAL support,
plus various bug fixes and cleanups.

All are ia64-specific csets except for one addition of
an include file in xen/include/public/io/blkif.h.

Merged and tested up thru xen-unstable cset 8169.

Booting domU requires the strange workaround* discussed
with Ewan which will hopefully go away when he checks
in his changes later today(?).

Assuming Ewan's fix works and no post-8169 csets result
in ia64 breakage, this should be the final ia64 pull
for 3.0.

Thanks,
Dan

* /etc/xen/xmdefconfig: replace w with w! in disk= line
  /etc/hotplug/xen-backend.agent and /etc/xen/scripts/block
  require logging to be enabled: add -x after /bin/sh in
  first line, followed by a line containing "exec 2>>/tmp/file"

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull
 
http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Several nasty Xen/ia64 corner case hypervisor bug fixes.

Merged and tested up thru xen-unstable cset 7895.

Thanks,
Dan

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

> > This includes changes to adapt to your new binding
> > interface (thanks Kevin!), a fix to adapt to the
> > new config option where blkfront can be built as
> > a module, one more driver change (ifdef __ia64__)
> > and a couple other minor tweaks.
> 
> I'm not too worried about a few short-term ifdef's as long as 
> they get 
> followed up and result in appropriate changes to interfaces. Clearly 
> you need some changes to the gnttab interface, just as you 
> needed some 
> to the evtchn interface.

Yes.  Actually that specific line (as submitted by Kevin Tian)
didn't have an ifdef, because on x86 the gnttab_map_vaddr macro
translates in  a way such that assignment is redundant.  I put
the ifdef and comment in: 1) to call attention to the fact that
the ia64 interface for GNTTABOP_map_grant_ref (as designed by
Matt Chapman) is slightly different, though compatible with x86
and 2) because if something on x86 changed behind the curtains
(e.g. in the x86 version of the macro), this new line of code
might break x86 in a way which would be difficult to debug.

Note that xen/arch/ia64/xen/grant_table.c is almost identical
to xen/common/grant_table.c, except for a few ifdef's plus
some formatting/renaming changes that haven't been tracked
in the ia64 side.  (I fear one or two other subtle differences
have crept in that may result in problems in ia64.)  It has
been on our to-do list to merge this back together and clarify
the differences in the gnttab interface, but we were delaying
until ia64 multiple domains were stable again (or post-3.0).

Dan

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull 

http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg

This includes changes to adapt to your new binding
interface (thanks Kevin!), a fix to adapt to the
new config option where blkfront can be built as
a module, one more driver change (ifdef __ia64__)
and a couple other minor tweaks.

Assuming new xen-unstable cset's from today don't
result in more fixes required, this will be the
first time Xen/ia64 will be able to run multiple
domains directly from a xen-unstable tree.

Thanks,
Dan
 

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] 
> Sent: Tuesday, November 08, 2005 8:08 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel@lists.xensource.com
> Subject: Re: Please pull xen-ia64-unstable
> 
> 
> On 7 Nov 2005, at 18:45, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> 
> > Please pull
> >
> > http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> >
> > Merged up thru xen-unstable cset 7642.
> 
> Okay, pulled through. I noticed that the event-channel 
> interfaces still 
> cause problems (bind_virq_to_irq in particular). I've had 
> another go at 
> rationalising the binding interface in light of this, so you now need 
> to implement:
>   bind_evtchn_to_irq --- same as it ever was
>   bind_virq_to_irqhandler --- replaces bind_virq_to_irq
>   bind_ipi_to_irqhandler --- replaces bind_ipi_to_irq
>   unbind_from_irqhandler --- common unbind function that replaces 
> unbind_evtchn_from_irqhandler, unbind_virq_from_irq and 
> unbind_ipi_from_irq
> 
> This interface eliminates all evtchn-related ia64 ifdefs in 
> common code.
> 
>   -- Keir
> 
> 

Re: Please pull xen-ia64-unstable

[Keir Fraser]

On 10 Nov 2005, at 22:09, Magenheimer, Dan (HP Labs Fort Collins) wrote:

>
> This includes changes to adapt to your new binding
> interface (thanks Kevin!), a fix to adapt to the
> new config option where blkfront can be built as
> a module, one more driver change (ifdef __ia64__)
> and a couple other minor tweaks.

I'm not too worried about a few short-term ifdef's as long as they get 
followed up and result in appropriate changes to interfaces. Clearly 
you need some changes to the gnttab interface, just as you needed some 
to the evtchn interface.

  -- Keir

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Great, thanks!  Are these new interfaces checked into
xen-unstable yet?  I can't find the changeset. 

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] 
> Sent: Tuesday, November 08, 2005 8:08 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel@lists.xensource.com
> Subject: Re: Please pull xen-ia64-unstable
> 
> 
> On 7 Nov 2005, at 18:45, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> 
> > Please pull
> >
> > http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> >
> > Merged up thru xen-unstable cset 7642.
> 
> Okay, pulled through. I noticed that the event-channel 
> interfaces still 
> cause problems (bind_virq_to_irq in particular). I've had 
> another go at 
> rationalising the binding interface in light of this, so you now need 
> to implement:
>   bind_evtchn_to_irq --- same as it ever was
>   bind_virq_to_irqhandler --- replaces bind_virq_to_irq
>   bind_ipi_to_irqhandler --- replaces bind_ipi_to_irq
>   unbind_from_irqhandler --- common unbind function that replaces 
> unbind_evtchn_from_irqhandler, unbind_virq_from_irq and 
> unbind_ipi_from_irq
> 
> This interface eliminates all evtchn-related ia64 ifdefs in 
> common code.
> 
>   -- Keir
> 
> 

Re: Please pull xen-ia64-unstable

[Keir Fraser]

On 8 Nov 2005, at 15:41, Magenheimer, Dan (HP Labs Fort Collins) wrote:

> Great, thanks!  Are these new interfaces checked into
> xen-unstable yet?  I can't find the changeset.

They have to get through our automatic regression tests. Assuming all 
goes well the changes should be pushed in less than an hour,

  -- Keir

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Please pull
 
http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
 
Merged up thru xen-unstable cset 7642.

Re: Please pull xen-ia64-unstable

[Keir Fraser]

On 7 Nov 2005, at 18:45, Magenheimer, Dan (HP Labs Fort Collins) wrote:

> Please pull
>
> http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
>
> Merged up thru xen-unstable cset 7642.

Okay, pulled through. I noticed that the event-channel interfaces still 
cause problems (bind_virq_to_irq in particular). I've had another go at 
rationalising the binding interface in light of this, so you now need 
to implement:
  bind_evtchn_to_irq --- same as it ever was
  bind_virq_to_irqhandler --- replaces bind_virq_to_irq
  bind_ipi_to_irqhandler --- replaces bind_ipi_to_irq
  unbind_from_irqhandler --- common unbind function that replaces 
unbind_evtchn_from_irqhandler, unbind_virq_from_irq and 
unbind_ipi_from_irq

This interface eliminates all evtchn-related ia64 ifdefs in common code.

  -- Keir

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Can you still pull this please?

Thanks,
Dan

> -----Original Message-----
> From: Magenheimer, Dan (HP Labs Fort Collins) 
> Sent: Monday, October 24, 2005 11:49 AM
> To: 'Keir Fraser'
> Cc: 'xen-devel@lists.xensource.com'
> Subject: Please pull xen-ia64-unstable
> 
> Please pull
> 
> http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
>  
> Merged up thru xen-unstable cset 7483.
> 
> Includes: first round of SMP support, bug fixes,
> more VTI merge code.
> 
> Thanks,
> Dan
> 

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Please pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
 
Merged up thru xen-unstable cset 7483.

Includes: first round of SMP support, bug fixes,
more VTI merge code.

Thanks,
Dan

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Please pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Merged up thru xen-unstable cset 7313.

Mostly catchup to the rapid changes in the core
tools/drivers, but also some bug fixes, cleanup,
and performance changes.  No affect on anything
outside of ia64 directories.

Thanks,
Dan

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

If you wouldn't mind, please again pull

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

This merges in changes from xen-unstable up through
about two hours ago, and also allows xenlinux/ia64
to be built completely within the xen-unstable tree,
making the xenlinux-ia64-2.6.12.hg tree obsolete.
(James, please don't remove it from xenbits yet
though.)

Thanks,
Dan

> -----Original Message-----
> From: Magenheimer, Dan (HP Labs Fort Collins) 
> Sent: Thursday, September 22, 2005 1:04 PM
> To: 'Keir Fraser'
> Cc: xen-devel@lists.xensource.com
> Subject: RE: Please pull xen-ia64-unstable
> 
> Oops :-} cut-and-paste error :-}
> 
> That should be:
> 
> http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> 
> Sorry...
> Dan
> 
> > -----Original Message-----
> > From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] 
> > Sent: Thursday, September 22, 2005 12:52 PM
> > To: Magenheimer, Dan (HP Labs Fort Collins)
> > Cc: xen-devel@lists.xensource.com
> > Subject: Re: Please pull xen-ia64-unstable
> > 
> > 
> > On 22 Sep 2005, at 19:17, Magenheimer, Dan (HP Labs Fort 
> > Collins) wrote:
> > 
> > > Please pull
> > > http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg
> > 
> > What am I supposed to pull it into? That's a Linux repository.
> > 
> >   -- Keir
> > 
> > 
> 

RE: Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Oops :-} cut-and-paste error :-}

That should be:

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Sorry...
Dan

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] 
> Sent: Thursday, September 22, 2005 12:52 PM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel@lists.xensource.com
> Subject: Re: Please pull xen-ia64-unstable
> 
> 
> On 22 Sep 2005, at 19:17, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> 
> > Please pull
> > http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg
> 
> What am I supposed to pull it into? That's a Linux repository.
> 
>   -- Keir
> 
> 

Re: Please pull xen-ia64-unstable

[Keir Fraser]

On 22 Sep 2005, at 20:04, Magenheimer, Dan (HP Labs Fort Collins) wrote:

> Oops :-} cut-and-paste error :-}
>
> That should be:
>
> http://xenbits.xensource.com/ext/xen-ia64-unstable.hg

Well, I'm not sure about xen_init() myself. I don't see any 
implementation of it for ia64 in your patches -- how does it actually 
work?

Also, what about your one-line patch to drivers/acpi/motherboard.c? 
That shouldn't be necessary. I'd rather not add it to our sparse tree 
if we can avoid it.

  -- Keir

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull
http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg

Includes:
- VTI merge changes (dynamically supports VTI and non-VTI
  domains)
- arch/ia64 changes to handle xenstore and console
- first phase of populating -sparse for ia64 (builds
  domain0)
- special elilo (ia64 grub-like boot tool) to allow
  domain0 to boot if initrd is required (e.g. RHEL4)
- pfmon support (had bitrotted)

The proposed xen_init changes are also included (ifdef'd
away for x86).  Even if there are different methods
proposed (just saw Hollis's message), please check this
in for now as it is harmless for x86 and required for
the next step for ia64 multiple domain... we can evolve
it if/as necessary later.

Thanks,
Dan

Re: Please pull xen-ia64-unstable

[Keir Fraser]

On 22 Sep 2005, at 19:17, Magenheimer, Dan (HP Labs Fort Collins) wrote:

> Please pull
> http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg

What am I supposed to pull it into? That's a Linux repository.

  -- Keir

Please pull xen-ia64-unstable

[Magenheimer, Dan (HP Labs Fort Collins)]

Hi Keir --

Please pull
http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg

Includes:
- VTI/non-VTI merge changes
- VTI bug fixes
- Rebasing (leveraged files) to 2.6.13
- Support CONFIG_SMP build
- Some xc tools changes to handle ia64 support
- Updates to handle changed locations
  of hypervisor.h, synch_bitops.h, etc.
- Some include file additions to drivers

Thanks!
Dan