From: "Carsten Schiers" <carsten@schiers.de>
To: linux <linux@eikelenboom.it>
Cc: xen-devel <xen-devel@lists.xensource.com>,
"konrad.wilk" <konrad.wilk@oracle.com>
Subject: AW: Re: AW: Re: AW: Load increase after memory upgrade?
Date: Mon, 27 Jun 2011 22:46:15 +0200 [thread overview]
Message-ID: <H0000067000b47f5.1309207574.uhura.space.zz@MHS> (raw)
In-Reply-To: <1733648145.20110627222009@eikelenboom.it>
>I'm running konrad's master
tree(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) with
a additional patch that's the last one in his "devel/xen-pciback-0.6.1"
tree >(xen/pciback: revert the name of the PCI driver to ...).
>The patch is necessary, otherwise the xen toolstack doesn't see the
devices being owned by pciback.
Forget what I just mailed. It's a head. I am not very used to all these
git thingies...
Is there an easy way to describe the steps to do after
git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
?
Carsten.
next prev parent reply other threads:[~2011-06-27 20:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 11:29 AW: Load increase after memory upgrade? Carsten Schiers
2011-06-27 13:46 ` Konrad Rzeszutek Wilk
2011-06-27 15:37 ` Sander Eikelenboom
2011-06-27 20:00 ` AW: " Carsten Schiers
2011-06-27 20:20 ` Sander Eikelenboom
2011-06-27 20:44 ` AW: " Carsten Schiers
2011-06-27 20:46 ` Carsten Schiers [this message]
2011-06-28 14:57 ` Konrad Rzeszutek Wilk
2011-06-28 20:17 ` AW: " Carsten Schiers
2011-06-28 20:22 ` Carsten Schiers
2011-06-28 20:34 ` Konrad Rzeszutek Wilk
2011-06-29 21:17 ` AW: " Carsten Schiers
2011-06-30 22:00 ` Konrad Rzeszutek Wilk
2011-06-28 14:50 ` Konrad Rzeszutek Wilk
2011-06-28 20:34 ` AW: " Carsten Schiers
2011-06-27 19:56 ` Carsten Schiers
2011-06-28 14:49 ` 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=H0000067000b47f5.1309207574.uhura.space.zz@MHS \
--to=carsten@schiers.de \
--cc=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--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.