xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Sander Eikelenboom <linux@eikelenboom.it>, andre.przywara@amd.com
Cc: Robert Phillips <robert.phillips@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Ben Guthro <ben@guthro.net>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: dom0 linux 3.6.0-rc4, crash due to ballooning althoug dom0_mem=X, max:X set
Date: Mon, 17 Sep 2012 15:23:37 -0400	[thread overview]
Message-ID: <20120917192336.GC18552@phenom.dumpdata.com> (raw)
In-Reply-To: <83845768.20120917211452@eikelenboom.it>

On Mon, Sep 17, 2012 at 09:14:52PM +0200, Sander Eikelenboom wrote:
> Thursday, September 13, 2012, 3:32:14 PM, you wrote:
> 
> >> > Sander, could you please let me know if it fixes the problem for you?
> >> 
> >> It does !
> >> 
> >> Tested-By: Sander Eikelenboom <linux@eikelenboom.it>
> 
> > Excellent. Applied. Thx for reporting and testing.
> 
> Hi Konrad,
> 
> Could it be that i haven't seen a pull request for this one for the 3.6.0 kernel yet ?

Correct. I am waiting for Andre Przyrwa to give me heads up on the AMD
NUMA bugfix so I can push two bug-fixes to Linus ASAP.

> 
> --
> 
> Sander
> 

  reply	other threads:[~2012-09-17 19:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 16:37 dom0 linux 3.6.0-rc4, crash due to ballooning althoug dom0_mem=X, max:X set Sander Eikelenboom
2012-09-04 16:33 ` Konrad Rzeszutek Wilk
2012-09-04 17:19   ` Sander Eikelenboom
2012-09-04 18:07     ` Ben Guthro
2012-09-04 18:22       ` Konrad Rzeszutek Wilk
2012-09-04 18:57         ` Sander Eikelenboom
2012-09-04 19:34       ` Sander Eikelenboom
2012-09-04 20:27         ` Robert Phillips
2012-09-05 14:06           ` Konrad Rzeszutek Wilk
2012-09-05 14:38             ` Sander Eikelenboom
2012-09-05 20:19               ` Konrad Rzeszutek Wilk
2012-09-05 22:52                 ` Sander Eikelenboom
2012-09-06 10:57                   ` Konrad Rzeszutek Wilk
2012-09-06 11:16                     ` Sander Eikelenboom
2012-09-06 16:46                     ` Sander Eikelenboom
2012-09-11 16:02             ` Stefano Stabellini
2012-09-12 10:28               ` Sander Eikelenboom
2012-09-12 11:28                 ` Stefano Stabellini
2012-09-13 13:32                 ` Konrad Rzeszutek Wilk
2012-09-13 13:42                   ` Robert Phillips
2012-09-14 14:53                   ` Conny Seidel
2012-09-14 17:00                     ` Konrad Rzeszutek Wilk
2012-09-14 17:38                       ` Conny Seidel
2012-09-17 19:14                   ` Sander Eikelenboom
2012-09-17 19:23                     ` Konrad Rzeszutek Wilk [this message]
2012-09-04 16:39 ` Konrad Rzeszutek Wilk
2012-09-04 18:02   ` Sander Eikelenboom
2012-09-04 17:58     ` Konrad Rzeszutek Wilk
2012-09-04 19:01       ` Sander Eikelenboom
2012-09-04 20:13       ` Sander Eikelenboom
2012-09-04 21:23       ` Sander Eikelenboom

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=20120917192336.GC18552@phenom.dumpdata.com \
    --to=konrad@kernel.org \
    --cc=andre.przywara@amd.com \
    --cc=ben@guthro.net \
    --cc=konrad.wilk@oracle.com \
    --cc=linux@eikelenboom.it \
    --cc=robert.phillips@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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).