All of lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: Re: pvops kernel branches - 2.6.36 options, stable/next/etc?
Date: Wed, 10 Nov 2010 14:43:02 -0500	[thread overview]
Message-ID: <20101110194302.GA25849@dumpdata.com> (raw)
In-Reply-To: <AANLkTimYoNQKZtm+eBtWVMCdcHop0g-o=wSBjbrHBkRu@mail.gmail.com>

> It's not a patch on konrad's stable/xen-pcifront-0.8.2 branch which was
> looking very good around the 10/21 timeframe, but which has also developed
> it's own set of instabilities recently.

Oooh, share please.

> I haven't reported any of the symptoms as I thought I'd let the dist settle
> before starting the bug reporting.
> 
> Is there some other branch that developers working on PCI device drivers in
> a pvops domU should be following?

Well, I am working on a PCI E820 hole thingie, but those patches are in the
infancy period. There are some fixes:

stable/xen-pcifront-fixes

but they aren't that .. sophisticated.
> 
> I realize that we're tracking unstable trees, but it's either that or hvm.
> We'd like to stick with the benefits that pvops provides, but I'm running
> out of branches to try.
> 
> The last stable domU I built was:
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git -
> stable/xen-pcifront-0.8.2
>  8029255fcc3a7925ad8ee9f5fdc0764b6662301e

Hmm, so the difference between that and the upstream is the PVonHVM and
the initial domain 0 support (all in Stefano's tree).

  parent reply	other threads:[~2010-11-10 19:43 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 [this message]
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
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=20101110194302.GA25849@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=bruce.edge@gmail.com \
    --cc=jeremy@goop.org \
    --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.