From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>, qemu-s390x@nongnu.org
Cc: qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1] numa: s390x has no NUMA
Date: Mon, 26 Feb 2018 10:25:19 +0100 [thread overview]
Message-ID: <19e19b72-ac67-8210-345b-41431f7d2075@redhat.com> (raw)
In-Reply-To: <afa4789f-8377-f033-00c8-35821a872178@de.ibm.com>
On 26.02.2018 10:20, Christian Borntraeger wrote:
>
>
> On 02/23/2018 06:36 PM, David Hildenbrand wrote:
>> Right now it is possible to crash QEMU for s390x by providing e.g.
>> -numa node,nodeid=0,cpus=0-1
>>
>> Problem is, that numa.c uses mc->cpu_index_to_instance_props as an
>> indicator whether NUMA is supported by a machine type. We don't
>> implement NUMA on s390x (and that concept also doesn't really exist).
>> We need mc->cpu_index_to_instance_props for query-cpus.
>
> Looks like we assert because of
> machine->possible_cpus == 0.
>
> Later during boot this is created in s390_possible_cpu_arch_ids. (via
> s390_init_cpus). What we (in the future) actually could provide is a
> cpu topology.
>
> So something like this also fixes the bug
Yes, but I decided to not go this way because we don't support NUMA as
of now. -numa has to bail out (just as it did before I implemented
proper query-cpus support).
What you propose is something for future support - one we have cpu
topology information exposed.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2018-02-26 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 17:36 [Qemu-devel] [PATCH v1] numa: s390x has no NUMA David Hildenbrand
2018-02-26 8:49 ` [Qemu-devel] [qemu-s390x] " Claudio Imbrenda
2018-02-26 9:20 ` [Qemu-devel] " Christian Borntraeger
2018-02-26 9:25 ` David Hildenbrand [this message]
2018-02-26 10:19 ` Cornelia Huck
2018-02-26 10:28 ` David Hildenbrand
2018-02-26 10:35 ` Cornelia Huck
2018-02-26 11:07 ` Christian Borntraeger
2018-02-26 11:12 ` David Hildenbrand
2018-02-26 11:23 ` Cornelia Huck
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=19e19b72-ac67-8210-345b-41431f7d2075@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).