From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bruce Edge <bruce.edge@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Re: pvops kernel branches - 2.6.36 options, stable/next/etc?
Date: Thu, 11 Nov 2010 11:55:27 -0500 [thread overview]
Message-ID: <20101111165527.GC30006@dumpdata.com> (raw)
In-Reply-To: <72D6B008-E913-4271-A731-BA7388E5271D@gmail.com>
> > I think bisecting the code and just running as DomU PV (without PCI passthrough)
> > and trying different kernels: 2.6.36, 2.6.35, 2.6.34 and seeing if you get the
> > same or similar hang can help us a bit. If you can get hold of Boris you could
> > both coordinate this?
>
> Any particular pvops branch, or mainline Linux?
Mainline please.
next prev parent reply other threads:[~2010-11-11 16:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 18:19 pvops kernel branches - 2.6.36 options, stable/next/etc? Bruce Edge
2010-11-08 19:14 ` Jeremy Fitzhardinge
2010-11-09 10:26 ` Thomas Goirand
2010-11-10 18:13 ` Jeremy Fitzhardinge
2010-11-12 7:43 ` Boris Derzhavets
2010-11-09 11:20 ` Boris Derzhavets
2010-11-09 15:00 ` Konrad Rzeszutek Wilk
2010-11-09 16:27 ` Boris Derzhavets
2010-11-10 18:17 ` Bruce Edge
2010-11-10 18:27 ` Jeremy Fitzhardinge
2010-11-10 19:43 ` Konrad Rzeszutek Wilk
2010-11-10 20:04 ` Bruce Edge
2010-11-11 14:58 ` Bruce Edge
2010-11-11 16:25 ` Konrad Rzeszutek Wilk
2010-11-11 16:48 ` Bruce Edge
2010-11-11 16:55 ` Konrad Rzeszutek Wilk [this message]
2010-11-11 18:09 ` Boris Derzhavets
2010-11-11 18:32 ` Bruce Edge
2010-11-11 18:50 ` Boris Derzhavets
2010-11-11 20:03 ` Boris Derzhavets
2010-11-11 20:20 ` Bruce Edge
2010-11-11 21:11 ` Konrad Rzeszutek Wilk
2010-11-11 22:06 ` Bruce Edge
2010-11-11 22:25 ` 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=20101111165527.GC30006@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bruce.edge@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=stefano.stabellini@eu.citrix.com \
--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 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.