From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, thomas@schwinge.name
Subject: devel/merge.2.6.35-rc3 [WAS: [GIT PULL] pv/pcifront-2.6.32 + pv/pciback-2.6.32 = [INTx/MSI/MSI-X work now]]
Date: Tue, 22 Jun 2010 14:45:21 -0400 [thread overview]
Message-ID: <20100622184521.GA4784@phenom.dumpdata.com> (raw)
In-Reply-To: <359195472.20100421104336@eikelenboom.it>
On Wed, Apr 21, 2010 at 10:43:36AM +0200, Sander Eikelenboom wrote:
> Is your xen-swiotlb work also going to be merged with this?
So, I never got to answer this. The answer is: eventually. When
we get to stabilizing 2.6.34 to work as Dom0, we will be definitely using
that.
> Guess i will wait for this one to get merged by Jeremy to test and replace my dom0 and domU kernels.
For the DomU, if you feel adventurous, I've just updated two branches
with the latest Xen PCI frontend driver:
pv/merge.2.6.34
devel/merge.2.6.35-rc3
The 2.6.35-rc-3 contains the latest of the swiotlb, xen-swiotlb, xen
pcifront, etc. Lots of cleanup, merging of patches, etc. to make it
nicer for Linux Kernel Mailing List (LKML).
The outstanding bugs are:
- pvgrub isn't working well. If you specify 'iommu=soft' pvgrub breaks.
- the xen tools nor the xen pci front specify an PCI region, hence your
guess is limited to 3GB so that you have a memory region below 4GB
for 32bit guest devices.
>
> Is there anything you need to be tested upfront ?
Oh man, I like that. If you feel you have the time, booting the DomU
kernel with any hardware would be appreciated. And try to do funky
stuff. I don't think I've completely hardened the driver.
next prev parent reply other threads:[~2010-06-22 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 2:59 [GIT PULL] pv/pcifront-2.6.32 + pv/pciback-2.6.32 = [INTx/MSI/MSI-X work now] Konrad Rzeszutek Wilk
2010-04-21 8:43 ` Sander Eikelenboom
2010-06-22 18:45 ` Konrad Rzeszutek Wilk [this message]
2010-06-22 19:11 ` devel/merge.2.6.35-rc3 [WAS: [GIT PULL] pv/pcifront-2.6.32 + pv/pciback-2.6.32 = [INTx/MSI/MSI-X work now]] Konrad Rzeszutek Wilk
2010-06-27 17:35 ` Sander Eikelenboom
2010-06-27 19:36 ` Sander Eikelenboom
2010-06-30 14:59 ` Konrad Rzeszutek Wilk
2010-06-30 15:57 ` Sander Eikelenboom
2010-04-21 18:46 ` [GIT PULL] pv/pcifront-2.6.32 + pv/pciback-2.6.32 = [INTx/MSI/MSI-X work now] Konrad Rzeszutek Wilk
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=20100622184521.GA4784@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=linux@eikelenboom.it \
--cc=thomas@schwinge.name \
--cc=xen-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).