qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: berrange@redhat.com, Eduardo Habkost <ehabkost@redhat.com>,
	qemu-stable@nongnu.org, qemu-devel@nongnu.org,
	mhohmann@physnet.uni-hamburg.de, pbonzini@redhat.com
Subject: Re: [PATCH] hostmem: don't use mbind() if host-nodes is epmty
Date: Mon, 11 May 2020 22:03:45 +0200	[thread overview]
Message-ID: <db2c1505-d5fb-9310-7805-6c3be2435c04@redhat.com> (raw)
In-Reply-To: <20200511212442.6e3f4509@redhat.com>

On 5/11/20 9:24 PM, Igor Mammedov wrote:
> On Mon, 11 May 2020 18:00:01 +0200
> Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
> 
>> Hi Eduardo,
>>
>> On 5/4/20 5:44 PM, Eduardo Habkost wrote:
>>> On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
>>>> Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
>>>> The backend however calls mbind() which is typically NOP
>>>> in case of default policy/absent host-nodes bitmap.
>>>> However when runing in container with black-listed mbind()
>>>> syscall, QEMU fails to start with error
>>>>    "cannot bind memory to host NUMA nodes: Operation not permitted"
>>>> even when user hasn't provided host-nodes to pin to explictly
>>>> (which is the case with -m option)
>>>>
>>>> To fix issue, call mbind() only in case when user has provided
>>>> host-nodes explicitly (i.e. host_nodes bitmap is not empty).
>>>> That should allow to run QEMU in containers with black-listed
>>>> mbind() without memory pinning. If QEMU provided memory-pinning
>>>> is required user still has to white-list mbind() in container
>>>> configuration.
>>>>
>>>> Reported-by: Manuel Hohmann <mhohmann@physnet.uni-hamburg.de>
>>>> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
>>>
>>> Queued on machine-next, thanks!
>>
>> I've been debugging this issue again today and figured it was not
>> merged, if possible can you add the "Cc: qemu-stable@nongnu.org" tag
>> before sending your pull request?
> it's CCed already, so my impression was that will should picked up once it was reviewed.

Correct, however some distributions find easier to grep for the 'Cc: 
qemu-stable@nongnu.org' merged tag before qemu-stable is released.

> 
>>
>> Thanks,
>>
>> Phil.
>>
> 



      reply	other threads:[~2020-05-11 20:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 15:46 [PATCH] hostmem: don't use mbind() if host-nodes is epmty Igor Mammedov
2020-04-30 16:42 ` Philippe Mathieu-Daudé
2020-05-01  7:28   ` Manuel Hohmann
2020-05-01  8:57 ` Daniel P. Berrangé
2020-05-04 14:31   ` Philippe Mathieu-Daudé
2020-05-04 15:44 ` Eduardo Habkost
2020-05-11 16:00   ` Philippe Mathieu-Daudé
2020-05-11 19:24     ` Igor Mammedov
2020-05-11 20:03       ` Philippe Mathieu-Daudé [this message]

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=db2c1505-d5fb-9310-7805-6c3be2435c04@redhat.com \
    --to=philmd@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mhohmann@physnet.uni-hamburg.de \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.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).