Re: [Xen-devel] Xen 3.1.1 -- initial patchqueue

[Alex Williamson <alex.williamson@xxxxxx>]

On Mon, 2007-09-10 at 09:56 +0100, Keir Fraser wrote:
> Hi,
> 
> A provisional patchqueue for Xen 3.1.1 is available at
> http://xenbits.xensource.com/xen-3.1-testing.pq.hg. This pq partners with
> http://xenbits.xensource.com/xen-3.1-testing.hg.
> 
> Please kick this pq around and check whether the patches you want to see in
> 3.1.1 are included.

Hi Keir,

   Here's a proposed list of patches for ia64:

Must have fixes:

http://xenbits.xensource.com/xen-unstable.hg?rev/51f5bea7b0d8
15348:51f5bea7b0d8 - adds free_irq(), necessary for build

http://xenbits.xensource.com/xen-unstable.hg?rev/b46c2ff6dfb0
15331:b46c2ff6dfb0 - fixes boot on NUMA systems

http://xenbits.xensource.com/xen-unstable.hg?rev/f536eb8576ee
15579:f536eb8576ee - fix VTI domain shutdown

http://xenbits.xensource.com/xen-unstable.hg?rev/d4f59e652078
15096:d4f59e652078 - fix pcifront with CONFIG_NUMA

http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/1483ef74511b
linux/56:1483ef74511b - update for acm interface changes

http://lists.xensource.com/archives/html/xen-ia64-devel/2006-11/msg00358.html
ia64-sal-get-state-info - Avoid GFP_KERNEL allocation from interrupt
context.  This was only recently fixed in upstream and is dependent on
other patches.  This is the simple fix proposed on the mailing list.
Patch attached.

These are all related to working out bugs and save location for NVRAM
support (must have):

http://xenbits.xensource.com/xen-unstable.hg?rev/71377eab1874
15349:71377eab1874 - white space cleanup - necessary for subsequent
patches

http://xenbits.xensource.com/xen-unstable.hg?rev/634b7f7f8584
*15265:634b7f7f8584 - allow domu nvram saving to fail gracefully

http://xenbits.xensource.com/xen-unstable.hg?rev/1623f5f5094f
15364:1623f5f5094f - don't save NVRAM on PV guests

http://xenbits.xensource.com/xen-unstable.hg?rev/33cc64dcaead
15365:33cc64dcaead - create NVRAM save directory

http://xenbits.xensource.com/xen-unstable.hg?rev/fd0103b55504
15366:fd0103b55504 - error checking for creat NVRAM save directory

http://xenbits.xensource.com/xen-unstable.hg?rev/38d061886873
15555:38d061886873 - avoid saving garbage to NVRAM on config error

http://xenbits.xensource.com/xen-unstable.hg?rev/2a5b463f2e8d
15557:2a5b463f2e8d - fix NVRAM save on reboot

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg?rev/6644d8486266
ia64/15762:6644d8486266 - cleanup NVRAM failure case

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg?rev/f88eea67a469
*ia64/15764:f88eea67a469 - move NVRAM from /usr to /var

These add the PCI Controller backend (high want - driver domains on some
systems won't work without this):

http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/93a955c2bebb
linux/46:93a955c2bebb - introduces controller backend

http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/a62cfa35d3b5
*linux/55:a62cfa35d3b5 - add hypercall to register i/o spaces

http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/452c5d4a5537
*linux/61:452c5d4a5537 - enable controller as default PCI backend

http://xenbits.xensource.com/xen-unstable.hg?rev/601509daabfc
*15353:601509daabfc - xen side support for multiple i/o spaces

Patches with an asterisk above require some modification to apply (white
space/file location/invalid chunks).  I've attached the modified
versions below.  Also note that 15265 is intentionally applied after
15349 above.  There's some screwiness around a merge for these and it
was easier to modify the white space in the smaller one and apply it
later.

   Other ia64'ers, please speak up if there's something else missing.
Thanks,

        Alex


-- 
Alex Williamson                             HP Open Source & Linux Org.

15265-634b7f7f8584-mod
Description: Text document

ia64-15764-f88eea67a469-mod
Description: Text document

linux-55-a62cfa35d3b5-mod
Description: Text document

linux-61-452c5d4a5537-mod
Description: Text document

15353-601509daabfc-mod
Description: Text document

ia64-sal-get-state-info
Description: Text document

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