public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: <qemu-devel@nongnu.org>,  <anisa.su@samsung.com>,
	<berrange@redhat.com>,  <eblake@redhat.com>,
	<jonathan.cameron@huawei.com>,  <linux-cxl@vger.kernel.org>,
	<linuxarm@huawei.com>,  <lizhijian@fujitsu.com>,
	 <mst@redhat.com>, <pbonzini@redhat.com>,  <gourry@gourry.net>,
	 <nifan.cxl@gmail.com>, <me@linux.beauty>
Subject: Re: [PATCH 1/9] hw/mem: Add tag support to generic host memory backends
Date: Thu, 26 Mar 2026 14:01:06 +0100	[thread overview]
Message-ID: <87bjgag2y5.fsf@pond.sub.org> (raw)
In-Reply-To: <20260326112921.000028e6.alireza.sanaee@huawei.com> (Alireza Sanaee's message of "Thu, 26 Mar 2026 11:29:21 +0000")

Alireza Sanaee <alireza.sanaee@huawei.com> writes:

> On Thu, 26 Mar 2026 11:42:17 +0100
> Markus Armbruster <armbru@redhat.com> wrote:
>
> Hi Markus,
>
>> Alireza Sanaee <alireza.sanaee@huawei.com> writes:
>> 
>> > Add a string tag property to HostMemoryBackend so that backends can be
>> > identified by a user-assigned name at runtime. Expose the property through
>> > QOM and add a host_memory_backend_find_by_tag() helper that walks the
>> > object tree to locate a backend by its tag.  
>> 
>> Why can't you use the QOM ID?
>> 
>> $ qemu-system-x86_64 -S -display none -monitor stdio -object memory-backend-ram,id=fred,size=1M
>> QEMU 10.2.90 monitor - type 'help' for more information
>> (qemu) info qom-tree /objects/fred
>> /fred (memory-backend-ram)
>>   /fred[0] (memory-region)
>> 
>>  
>
> Fair question. The ID would have been a solution if it had accepted GUIDs. CXL spec 
> requires GUIDs for extents as identification, hence new tag property.

Your commit message should state that this needs to be a GUID and why.

> alireza@blue-ocean:~/Downloads$ qemu-system-x86_64 -s -display none -monitor std
> io -object memory-backend-ram,id=02bb2436-e87d-4aa1-b2be-aaffdd76bb79,size=1M
> qemu-system-x86_64: -object memory-backend-ram,id=02bb2436-e87d-4aa1-b2be-aaffdd
> 76bb79,size=1M: Parameter 'id' expects an identifier
> Identifiers consist of letters, digits, '-', '.', '_', starting with a letter.
>
> Thanks,
> Ali



  reply	other threads:[~2026-03-26 13:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 18:42 [QEMU PATCH 0/9] Application Specific Tagged Memory Support in CXL Type 3 Devices Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 1/9] hw/mem: Add tag support to generic host memory backends Alireza Sanaee via qemu development
2026-03-26 10:42   ` Markus Armbruster
2026-03-26 11:29     ` Alireza Sanaee via qemu development
2026-03-26 13:01       ` Markus Armbruster [this message]
2026-03-26 13:04         ` Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 2/9] hw/cxl: Allow initializing type3 device with no backing device Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 3/9] hw/cxl: Hook up tagged host memory backends at runtime for DC extents Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 4/9] hw/cxl: Carry backend metadata in DC extent records Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 5/9] hw/cxl: Map lazy memory backend after host acceptance Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 6/9] hw/cxl: Create direct fixed-window aliases for accepted extents Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 7/9] hw/cxl: Add release-time teardown for direct-mapped extents Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 8/9] hw/cxl: Add tag-based dynamic-capacity release support Alireza Sanaee via qemu development
2026-03-25 18:42 ` [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity extent release Alireza Sanaee 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=87bjgag2y5.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alireza.sanaee@huawei.com \
    --cc=anisa.su@samsung.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=gourry@gourry.net \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lizhijian@fujitsu.com \
    --cc=me@linux.beauty \
    --cc=mst@redhat.com \
    --cc=nifan.cxl@gmail.com \
    --cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox