qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, qemu-trivial@nongnu.org,
	"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [PATCH] hw/ppc/Kconfig: NVDIMM is a hard requirement for the pseries machine
Date: Fri, 5 May 2023 07:41:28 -0300	[thread overview]
Message-ID: <32418990-82eb-a6d7-1695-db64e191f30b@gmail.com> (raw)
In-Reply-To: <1cf86174-b3eb-0674-7669-1bc7b4bc3eac@redhat.com>



On 5/5/23 05:03, Thomas Huth wrote:
> On 04/05/2023 23.19, Daniel Henrique Barboza wrote:
>>
>>
>> On 5/4/23 15:05, Thomas Huth wrote:
>>> When building QEMU with "--without-default-devices", the pseries
>>> machine fails to start even when running with the --nodefaults option:
>>>
>>>   $ ./qemu-system-ppc64 --nodefaults -M pseries
>>>   Type 'spapr-nvdimm' is missing its parent 'nvdimm'
>>>   Aborted (core dumped)
>>>
>>> Looks like NVDIMM is a hard requirement for this machine nowadays.
>>
>> Ouch.
>>
>> I believe this has to do with this comment in hw/ppc/spapr.c, in
>> spapr_instance_init():
>>
>>      /*
>>       * NVDIMM support went live in 5.1 without considering that, in
>>       * other archs, the user needs to enable NVDIMM support with the
>>       * 'nvdimm' machine option and the default behavior is NVDIMM
>>       * support disabled. It is too late to roll back to the standard
>>       * behavior without breaking 5.1 guests.
>>       */
>>      if (mc->nvdimm_supported) {
>>          ms->nvdimms_state->is_enabled = true;
>>      }
>>
>> It seems like you found out another side effect of this nvdimm situation that Igor
>> documented 2 years ago in 55810e90 ("ppc/spapr: cleanup -machine pseries,nvdimm=X
>> handling").
>>
>>
>> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
>>
>>
>> I'll send a PPC PR in the next few days. Let me know if you want me to queue it.
> 
> Yes, please add it to your queue!

Queued. Thanks,


Daniel

> 
>   Thanks,
>    Thomas
> 


      reply	other threads:[~2023-05-05 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 18:05 [PATCH] hw/ppc/Kconfig: NVDIMM is a hard requirement for the pseries machine Thomas Huth
2023-05-04 21:19 ` Daniel Henrique Barboza
2023-05-05  8:03   ` Thomas Huth
2023-05-05 10:41     ` Daniel Henrique Barboza [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=32418990-82eb-a6d7-1695-db64e191f30b@gmail.com \
    --to=danielhb413@gmail.com \
    --cc=clg@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.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 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).