From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Huang, FangSheng (Jerry)" <FangSheng.Huang@amd.com>,
Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, gourry@gourry.net, philmd@mailo.com,
Zhigang.Luo@amd.com, Lianjie.Shi@amd.com
Subject: Re: [PATCH v10 1/4] hw/mem: add sp-mem device for Specific Purpose Memory
Date: Wed, 10 Jun 2026 12:09:16 +0200 [thread overview]
Message-ID: <d0ed5bc6-5dc6-455f-87ff-111fcf0adca5@kernel.org> (raw)
In-Reply-To: <f50e7303-e600-410a-bec7-58f756e0efa7@amd.com>
On 6/10/26 09:03, Huang, FangSheng (Jerry) wrote:
>
>
> On 6/9/2026 5:03 PM, Igor Mammedov wrote:
>> On Fri, 5 Jun 2026 18:46:06 +0800
>> fanhuang <FangSheng.Huang@amd.com> wrote:
>>
>>> + 'memaddr': 'size',
>>
>> why not 'addr', like DIMM?
>>
>
> Will rename to 'addr' to match PCDIMMDeviceInfo.
Note that we had to use "memaddr" for virtio-mem etc, because their proxy device
(e.g., virtio-mem-pci) already had "addr" taken for other purposes.
I suspect we don't expect any proxy devices in the future? (similar to DIMMs)
Then, using "addr" is just fine.
--
Cheers,
David
next prev parent reply other threads:[~2026-06-10 10:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 10:46 [PATCH v10 0/4] hw/mem: add sp-mem device for Specific Purpose Memory fanhuang
2026-06-05 10:46 ` [PATCH v10 1/4] " fanhuang
2026-06-05 15:10 ` David Hildenbrand (Arm)
2026-06-05 21:22 ` Gregory Price
2026-06-09 9:03 ` Igor Mammedov
2026-06-10 7:03 ` Huang, FangSheng (Jerry)
2026-06-10 10:09 ` David Hildenbrand (Arm) [this message]
2026-06-05 10:46 ` [PATCH v10 2/4] i386/acpi-build: partition device_memory SRAT umbrella for sp-mem fanhuang
2026-06-05 21:27 ` Gregory Price
2026-06-09 3:53 ` Huang, FangSheng (Jerry)
2026-06-09 11:14 ` Igor Mammedov
2026-06-10 7:07 ` Huang, FangSheng (Jerry)
2026-06-05 10:46 ` [PATCH v10 3/4] hw/i386: hook sp-mem into the pc machine plug path fanhuang
2026-06-09 11:52 ` Igor Mammedov
2026-06-10 7:16 ` Huang, FangSheng (Jerry)
2026-06-05 10:46 ` [PATCH v10 4/4] MAINTAINERS: cover sp-mem under Memory devices, add R: tag fanhuang
2026-06-09 11:53 ` Igor Mammedov
2026-06-09 12:51 ` David Hildenbrand (Arm)
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=d0ed5bc6-5dc6-455f-87ff-111fcf0adca5@kernel.org \
--to=david@kernel.org \
--cc=FangSheng.Huang@amd.com \
--cc=Lianjie.Shi@amd.com \
--cc=Zhigang.Luo@amd.com \
--cc=gourry@gourry.net \
--cc=imammedo@redhat.com \
--cc=philmd@mailo.com \
--cc=qemu-devel@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.