xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Anisov <andrii.anisov@gmail.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: arm: xl vcpu-pin leads to oom-killer slashing processes
Date: Wed, 5 Dec 2018 12:28:00 +0200	[thread overview]
Message-ID: <97cc37c3-cff2-5128-b052-276b9147ef7d@gmail.com> (raw)
In-Reply-To: <2c2385f9-515d-1c13-2618-d22d52901abc@gmail.com>

It happens with credit and credit2 schedulers, with old and new vgic.

On 05.12.18 12:26, Andrii Anisov wrote:
> Hello,
> 
> On the current
>      6d8ffac (xenbits/master) xen/arm: gic: Remove duplicated comment in do_sgi
> and
>      7073942 (xenbits/staging, xenbits/smoke, xenbits/coverity-tested/smoke) pci: apply workaround for Intel errata HSE43 and BDF2/BDX2
> 
> `xl vcpu-pin` leads to oom-killer becomes mad and slashing all processes:
> 

-- 
Sincerely,
Andrii Anisov.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-12-05 10:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 10:26 arm: xl vcpu-pin leads to oom-killer slashing processes Andrii Anisov
2018-12-05 10:28 ` Andrii Anisov [this message]
2018-12-05 10:49 ` Julien Grall
2018-12-05 10:59   ` Andrii Anisov
2018-12-05 11:45     ` Julien Grall
2018-12-05 11:59       ` Andrii Anisov
2018-12-05 12:15         ` Julien Grall
2018-12-05 12:40           ` Andrii Anisov
2018-12-05 13:13             ` Julien Grall
2018-12-05 14:46               ` Andrii Anisov
2018-12-13 14:13                 ` Andrii Anisov
2018-12-13 16:37                   ` Juergen Gross
2018-12-14 10:36                     ` Andrii Anisov

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=97cc37c3-cff2-5128-b052-276b9147ef7d@gmail.com \
    --to=andrii.anisov@gmail.com \
    --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 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).