From: Jason Gunthorpe <jgg@nvidia.com>
To: Ankit Agrawal <ankita@nvidia.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Igor Mammedov <imammedo@redhat.com>,
Vikram Sethi <vsethi@nvidia.com>,
Shameer Kolothum Thodi <skolothumtho@nvidia.com>,
"alex@shazbot.org" <alex@shazbot.org>,
"anisinha@redhat.com" <anisinha@redhat.com>,
Aniket Agashe <aniketa@nvidia.com>, Neo Jia <cjia@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
"Tarun Gupta (SW-GPU)" <targupta@nvidia.com>,
Zhi Wang <zhiw@nvidia.com>, Matt Ochs <mochs@nvidia.com>,
Krishnakant Jaju <kjaju@nvidia.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v1 1/1] hw/acpi/pci.c: preserve generic initiator insertion order
Date: Tue, 24 Feb 2026 10:58:50 -0400 [thread overview]
Message-ID: <aZ28qvehl7Lleo2a@nvidia.com> (raw)
In-Reply-To: <SA1PR12MB7199847A879D66527B03DB1CB074A@SA1PR12MB7199.namprd12.prod.outlook.com>
On Tue, Feb 24, 2026 at 02:51:42PM +0000, Ankit Agrawal wrote:
> Now the kernel parse it in the sequence of their occurrence. A jumbled up
> sequence thus results in a jumbled up assignment.
But what is the actual failure mode here? So the numa IDs are all in a
weird order, what goes wrong from that?
Jason
next prev parent reply other threads:[~2026-02-24 14:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260222020812.26475-1-ankita@nvidia.com>
2026-02-23 7:28 ` [PATCH v1 1/1] hw/acpi/pci.c: preserve generic initiator insertion order Igor Mammedov
[not found] ` <SA1PR12MB7199F0C2E1D2325B0062B004B077A@SA1PR12MB7199.namprd12.prod.outlook.com>
2026-02-23 9:44 ` Igor Mammedov
2026-02-23 11:13 ` Jonathan Cameron via qemu development
2026-02-24 13:51 ` Jason Gunthorpe
2026-02-24 14:01 ` Michael S. Tsirkin
2026-02-24 14:42 ` Jason Gunthorpe
2026-02-24 14:48 ` Michael S. Tsirkin
2026-02-24 14:51 ` Ankit Agrawal
2026-02-24 14:54 ` Michael S. Tsirkin
2026-02-24 14:58 ` Jason Gunthorpe [this message]
2026-02-24 16:22 ` Ankit Agrawal
2026-02-24 16:30 ` Michael S. Tsirkin
2026-02-24 16:41 ` Jonathan Cameron via qemu development
2026-02-24 17:13 ` Jonathan Cameron via qemu development
2026-02-24 14:54 ` Jonathan Cameron via qemu development
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=aZ28qvehl7Lleo2a@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex@shazbot.org \
--cc=aniketa@nvidia.com \
--cc=anisinha@redhat.com \
--cc=ankita@nvidia.com \
--cc=cjia@nvidia.com \
--cc=imammedo@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=kjaju@nvidia.com \
--cc=kwankhede@nvidia.com \
--cc=mochs@nvidia.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=skolothumtho@nvidia.com \
--cc=targupta@nvidia.com \
--cc=vsethi@nvidia.com \
--cc=zhiw@nvidia.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.