All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: please pull xen-ia64-unstable.hg
Date: Wed, 25 Oct 2006 16:47:57 -0600	[thread overview]
Message-ID: <1161816477.11112.51.camel@lappy> (raw)

Hi Keir,

   Please pull:

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

The tree is merged up to xen-unstable.hg cset 11923:abee5c6b930d.  We
were busy during the 3.0.3 freeze, so there's a lot of stuff here.
Notable improvements include switching to the Tristan's xencomm
interface for hypercalls, which solves several random hypercall
failures, and incorporation of Isaku's performance tuning patches,
improving our dom0 -> domU networking up to about 2Gb/s.  We also have
many, many bug fixes, code cleanups and smaller optimizations.  This
pull will also fix the current build breakages for ia64 in the
xen-unstable.hg tree.

   You may want to check the following cset before pulling as it does
venture slightly out of ia64 specific code.  This just links in a couple
extra c files for the PV-on-HVM build and an ifdef'd startup hook:

http://xenbits.xensource.com/ext/xen-ia64-unstable.hg?cs=7c2a5f96a192

Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.

             reply	other threads:[~2006-10-25 22:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 22:47 Alex Williamson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-17 15:01 Please pull xen-ia64-unstable.hg Alex Williamson
2007-05-21 20:36 ` Alex Williamson
2007-04-24 16:57 Alex Williamson
2007-04-13 15:01 Alex Williamson
2007-04-12 17:44 Alex Williamson
2007-04-11 14:23 Alex Williamson
2007-04-09 20:41 Alex Williamson
2007-04-06 16:50 Alex Williamson
2007-04-03 19:46 Alex Williamson
2007-03-27 21:21 Alex Williamson
2007-03-28  2:34 ` Isaku Yamahata
2007-03-22 16:46 Alex Williamson
2007-02-22 18:12 Alex Williamson
2007-02-07 19:18 Alex Williamson
2007-01-18  5:59 please " Alex Williamson
2006-12-08 20:36 Alex Williamson
2006-12-09 13:47 ` Keir Fraser
2006-12-14 17:28   ` Alex Williamson
2006-11-14 22:54 Alex Williamson
2006-09-10 22:17 Alex Williamson
2006-09-12 18:54 ` Alex Williamson
2006-08-29 15:47 Alex Williamson
2006-08-09 16:57 Alex Williamson
2006-07-27 18:09 Alex Williamson
2006-07-28  9:53 ` Keir Fraser
2006-07-28 12:26   ` Alex Williamson
2006-06-28 21:32 Alex Williamson
2006-06-16 16:57 Alex Williamson
2006-05-31 22:44 Alex Williamson
2006-05-22 21:32 Alex Williamson
2006-04-26 19:54 Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1161816477.11112.51.camel@lappy \
    --to=alex.williamson@hp.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.