All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	david@gibson.dropbear.id.au,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] ppc: Yet another fix for the huge page support detection mechanism
Date: Mon, 18 Jul 2016 11:21:41 +0200	[thread overview]
Message-ID: <6a34fdcb-dfdf-9839-4f76-22ebb194402d@redhat.com> (raw)
In-Reply-To: <20160715112857.275e2c85@bahia.lan>

On 15.07.2016 11:28, Greg Kurz wrote:
> On Fri, 15 Jul 2016 10:10:25 +0200
> Thomas Huth <thuth@redhat.com> wrote:
> 
>> Commit 86b50f2e1bef ("Disable huge page support if it is not available
>> for main RAM") already made sure that huge page support is not announced
>> to the guest if the normal RAM of non-NUMA configurations is not backed
>> by a huge page filesystem. However, there is one more case that can go
>> wrong: NUMA is enabled, but the RAM of the NUMA nodes are not configured
>> with huge page support (and only the memory of a DIMM is configured with
>> it). When QEMU is started with the following command line for example,
>> the Linux guest currently crashes because it is trying to use huge pages
>> on a memory region that does not support huge pages:
>>
>>  qemu-system-ppc64 -enable-kvm ... -m 1G,slots=4,maxmem=32G -object \
>>    memory-backend-file,policy=default,mem-path=/hugepages,size=1G,id=mem-mem1 \
>>    -device pc-dimm,id=dimm-mem1,memdev=mem-mem1 -smp 2 \
>>    -numa node,nodeid=0 -numa node,nodeid=1
>>
>> To fix this issue, we've got to make sure to disable huge page support,
>> too, when there is a NUMA node that is not using a memory backend with
>> huge page support.
>>
>> Fixes: 86b50f2e1befc33407bdfeb6f45f7b0d2439a740
> 
> According to http://patchwork.ozlabs.org/patch/584741/ , it is best worded
> 
> "Broken in commit 86b50f2e1bef"

Using the "Fixes:" syntax is a well-known practise with the Linux kernel
(see
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=HEAD#n187),
so I don't see the point why we should introduce another syntax for QEMU
here. And if we do, it should be documented on
http://qemu-project.org/Contribute/SubmitAPatch at least.

 Thomas

  reply	other threads:[~2016-07-18  9:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15  8:10 [Qemu-devel] [PATCH] ppc: Yet another fix for the huge page support detection mechanism Thomas Huth
2016-07-15  8:35 ` David Gibson
2016-07-15 12:28   ` Thomas Huth
2016-07-15 15:18     ` Greg Kurz
2016-07-15 15:54       ` Thomas Huth
2016-07-15 16:31         ` Greg Kurz
2016-07-15  9:28 ` Greg Kurz
2016-07-18  9:21   ` Thomas Huth [this message]
2016-07-18  9:36     ` Greg Kurz
2016-07-18  0:52 ` David Gibson
2016-07-18  8:59   ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2016-07-18  9:04     ` Thomas Huth
2016-07-18  9:26       ` Greg Kurz
2016-07-18  9:33         ` Thomas Huth
2016-07-18 10:44           ` Greg Kurz
2016-07-18 13:16             ` [Qemu-devel] assert in memory.c line 1934 (was: Yet another fix for the huge page support detection mechanism) Thomas Huth
2016-07-18 13:23             ` [Qemu-devel] [Qemu-ppc] [PATCH] ppc: Yet another fix for the huge page support detection mechanism Greg Kurz
2016-07-18  9:21     ` David Gibson
2016-07-18 10:01       ` Greg Kurz

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=6a34fdcb-dfdf-9839-4f76-22ebb194402d@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 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.