From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Upgrade to xen-unstable-rc4
Date: Fri, 31 Aug 2012 13:39:42 -0400 [thread overview]
Message-ID: <20120831173941.GD19756@localhost.localdomain> (raw)
In-Reply-To: <1365913956.20120831193235@eikelenboom.it>
On Fri, Aug 31, 2012 at 07:32:35PM +0200, Sander Eikelenboom wrote:
>
> Friday, August 31, 2012, 7:29:11 PM, you wrote:
>
> >> > - Messages i haven't seen in dmesg with xen-4.1.3 in combination with 3.6-rc? kernel:
> >> [...ducks...]
>
> > I think that can easily be fixed. I seem to be seeing those too.
> >>
> >> > For the rest, all my domains and pci-passthrough seem to be working :-)
>
> > Oh nice. My AMD machine reboots when I tried HVM and PCI passthrough :-(
> > Hadn't yet actually done any git bisection or tried to get a serial
> > output.
>
> I'm mostly using PV and PCI passthrough, haven't tried HVM and PCI passthrough yet, but will somewhere this weekend ..
For v3.5 and later there is a bug in the Linux code (introduced by me)
which makes MSI in HVM PCI passthrough guests not work. You would need
to revert cd9db80e5257682a7f7ab245a2459648b3c8d268.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2012-08-31 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 9:44 Upgrade to xen-unstable-rc4 Sander Eikelenboom
2012-08-31 9:55 ` Ian Campbell
2012-08-31 17:29 ` Konrad Rzeszutek Wilk
2012-08-31 17:32 ` Sander Eikelenboom
2012-08-31 17:39 ` Konrad Rzeszutek Wilk [this message]
2012-08-31 17:56 ` Sander Eikelenboom
2012-08-31 12:09 ` Jan Beulich
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=20120831173941.GD19756@localhost.localdomain \
--to=konrad@kernel.org \
--cc=Ian.Campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.org \
/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.