All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: William Dauchy <william@gandi.net>
Cc: konrad@kernel.org, xen-devel@lists.xenproject.org
Subject: Re: 3.10 xenU memleaks
Date: Fri, 7 Feb 2014 10:02:24 -0500	[thread overview]
Message-ID: <20140207150224.GA3605@phenom.dumpdata.com> (raw)
In-Reply-To: <20140207124607.GE19084@gandi.net>

On Fri, Feb 07, 2014 at 01:46:07PM +0100, William Dauchy wrote:
> Hello,
> 
> I am facing random memleaks with a xenU 3.10.x pv (x86_64);
> sometimes without issue and sometimes after a reboot, the
> kernel starts to memleak a lot until OOM.
> 
> config: hypervisor xen4.1, dom0 v3.4.x (x86_32)
> 
> I got no issue with a xenU v3.12.x pv; the only difference in dmesg was
> about APIC.
> 
> I manually backported the following patch:
> 6efa20e xen: Support 64-bit PV guest receiving NMIs
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -427,8 +427,7 @@ static void __init xen_init_cpuid_mask(void)
>  
>         if (!xen_initial_domain())
>                 cpuid_leaf1_edx_mask &=
> -                       ~((1 << X86_FEATURE_APIC) |  /* disable local APIC */
> -                         (1 << X86_FEATURE_ACPI));  /* disable ACPI */
> +                       ~((1 << X86_FEATURE_ACPI));  /* disable ACPI */
> 
> 
> and my issue is completely fixed. Should it backported for stable?

That does not make sense. What are the leaks? What are the messages
that you see about APIC?

> 
> Thanks,
> -- 
> William

  reply	other threads:[~2014-02-07 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 12:46 3.10 xenU memleaks William Dauchy
2014-02-07 15:02 ` Konrad Rzeszutek Wilk [this message]
2014-02-07 15:38   ` William Dauchy
2014-02-07 16:04     ` Konrad Rzeszutek Wilk
2014-02-07 16:09       ` William Dauchy
2014-02-07 16:19         ` Konrad Rzeszutek Wilk
2014-02-07 16:28           ` William Dauchy

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=20140207150224.GA3605@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=konrad@kernel.org \
    --cc=william@gandi.net \
    --cc=xen-devel@lists.xenproject.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 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.