All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: peter.maydell@linaro.org, Gavin Shan <gshan@redhat.com>,
	ehabkost@redhat.com, robh@kernel.org, qemu-devel@nongnu.org,
	qemu-arm@nongnu.org, shan.gavin@gmail.com
Subject: Re: [PATCH 1/2] numa: Set default distance map if needed
Date: Wed, 13 Oct 2021 08:29:12 +0200	[thread overview]
Message-ID: <20211013062912.ilm7bydayna6gmco@gator.home> (raw)
In-Reply-To: <20211012155321.256e8867@redhat.com>

On Tue, Oct 12, 2021 at 03:53:21PM +0200, Igor Mammedov wrote:
...
> > > 
> > > Instead of putting workaround in QEMU and then making them generic,
> > > I'd prefer to:
> > >  1. make QEMU to be able generate DT with memory-less nodes  
> > 
> > How? DT syntax doesn't allow this, because each node needs a unique
> > name which is derived from its base address, which an empty numa
> you are talking about memory@foo nodes, aren't you?

yes, memory@<address> nodes

...
> > 
> > > or use ACPI tables which can
> > >     describe memory-less NUMA nodes if fixing how DT is
> > >     parsed unfeasible.  
> > 
> > We use ACPI already for our guests, but we also generate a DT (which
> > edk2 consumes). We can't generate a valid DT when empty numa nodes
> does edk2 actually uses numa info from QEMU?
>

edk2 doesn't use it, but I'd prefer we generate a DT which describes
the user's input and what the ACPI tables describe. Maybe someday it
won't be possible, but so far we've managed.

Thanks,
drew



  parent reply	other threads:[~2021-10-13  6:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 10:22 [PATCH 0/2] hw/arm/virt: Fix qemu booting failure on device-tree Gavin Shan
2021-10-06 10:22 ` [PATCH 1/2] numa: Set default distance map if needed Gavin Shan
2021-10-06 10:35   ` Andrew Jones
2021-10-06 11:03     ` Gavin Shan
2021-10-06 11:56       ` Andrew Jones
2021-10-07 23:51         ` Gavin Shan
2021-10-08  6:07           ` Andrew Jones
2021-10-12  6:13             ` Gavin Shan
2021-10-12  9:40   ` Igor Mammedov
2021-10-12 10:31     ` Gavin Shan
2021-10-12 11:18       ` Igor Mammedov
2021-10-12 11:48       ` Andrew Jones
2021-10-12 12:34         ` Igor Mammedov
2021-10-12 13:05           ` Andrew Jones
2021-10-12 22:59             ` Gavin Shan
2021-10-12 10:37     ` Andrew Jones
2021-10-12 12:27       ` Igor Mammedov
2021-10-12 13:13         ` Andrew Jones
2021-10-12 13:53           ` Igor Mammedov
2021-10-12 23:32             ` Gavin Shan
2021-10-13  9:32               ` Igor Mammedov
2021-10-13  6:29             ` Andrew Jones [this message]
2021-10-06 10:22 ` [PATCH 2/2] hw/arm/virt: Don't create device-tree node for empty NUMA node Gavin Shan
2021-10-06 10:36   ` Andrew Jones

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=20211013062912.ilm7bydayna6gmco@gator.home \
    --to=drjones@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=gshan@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=robh@kernel.org \
    --cc=shan.gavin@gmail.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 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.