From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xen devel <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: vmalloc_sync_all() patch problems?
Date: Tue, 11 Oct 2011 13:28:38 -0400 [thread overview]
Message-ID: <20111011172838.GA32406@phenom.oracle.com> (raw)
In-Reply-To: <B7DFE1B1-2506-422C-B5C0-F4334BF700F8@theshore.net>
On Tue, Oct 11, 2011 at 11:18:12AM -0400, Christopher S. Aker wrote:
> On Oct 10, 2011, at 11:51 AM, Konrad Rzeszutek Wilk wrote:
> > On Fri, Sep 30, 2011 at 11:38:23AM -0400, Christopher S. Aker wrote:
> >> On 9/28/11 1:04 PM, David Vrabel wrote:
> >>> On 28/09/11 17:02, Christopher S. Aker wrote:
> >>>> I've restarted the tests to see if I can reproduce, but I'm certain that
> >>>> if it happened once, it'll happen again.
> >>
> >> I was able to reproduce it.
> >>
> >>> Instead of the vmalloc_sync_all() patch you could try this series instead.
> >>>
> >>> http://lists.xensource.com/archives/html/xen-devel/2011-09/msg01343.html
> >>
> >> I'll rebuild using this series and reset the tests. Will let you know!
> >
> > ping?
>
> With that patchset applied: 6 days of thrashing, 30000 domains cycled, and no crashes. I'd say it worked.
Excellent. You got any more bugs that we should be aware off ? (hopefully not).
next prev parent reply other threads:[~2011-10-11 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 14:28 vmalloc_sync_all() patch problems? Christopher S. Aker
2011-09-28 14:45 ` David Vrabel
2011-09-28 16:02 ` Christopher S. Aker
2011-09-28 17:04 ` David Vrabel
2011-09-30 15:38 ` Christopher S. Aker
2011-10-10 15:51 ` Konrad Rzeszutek Wilk
2011-10-11 15:18 ` Christopher S. Aker
2011-10-11 17:28 ` Konrad Rzeszutek Wilk [this message]
2011-10-12 19:37 ` Christopher S. Aker
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=20111011172838.GA32406@phenom.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=caker@theshore.net \
--cc=david.vrabel@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.