linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
To: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>,
	"Bowman, Terry" <terry.bowman@amd.com>,
	"Fontenot, Nathan" <nafonten@amd.com>,
	David Hildenbrand <david@redhat.com>,
	Fan Ni <nifan.cxl@gmail.com>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"alison.schofield@intel.com" <alison.schofield@intel.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"gourry@gourry.net" <gourry@gourry.net>,
	"PradeepVineshReddy.Kodamati@amd.com"
	<PradeepVineshReddy.Kodamati@amd.com>,
	"Yasunori Gotou (Fujitsu)" <y-goto@fujitsu.com>,
	Alison Schofield <alison.schofield@intel.com>
Subject: RE: [PATCH v2 1/4] kernel/resource: Introduce managed SOFT RESERVED resources
Date: Sun, 23 Mar 2025 08:33:33 +0000	[thread overview]
Message-ID: <TY1PR01MB1562BBB0BD9235811B3DEA66A5A52@TY1PR01MB1562.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TY1PR01MB156225EF913E7568F3B12E05A5A52@TY1PR01MB1562.jpnprd01.prod.outlook.com>

Terry,

My apologies, Tthis reply should have been addressed to you. I hope you don't mind. :)


> -----Original Message-----
> From: Zhijian Li (Fujitsu) <lizhijian@fujitsu.com>
> Sent: Sunday, March 23, 2025 4:25 PM
> To: Bowman, Terry <terry.bowman@amd.com>; Fontenot, Nathan
> <nafonten@amd.com>; David Hildenbrand <david@redhat.com>; Fan Ni
> <nifan.cxl@gmail.com>
> Cc: linux-cxl@vger.kernel.org; dan.j.williams@intel.com;
> alison.schofield@intel.com; linux-mm@kvack.org; gourry@gourry.net;
> PradeepVineshReddy.Kodamati@amd.com; Gotou, Yasunori/五島 康文 <y-
> goto@fujitsu.com>; Alison Schofield <alison.schofield@intel.com>
> Subject: RE: [PATCH v2 1/4] kernel/resource: Introduce managed SOFT
> RESERVED resources
> 
> Hi Nathan
> 
> > Nathan asked me to finish the patchset submission in his place. He has
> > the
> > v3 iteration ready and I plan to send this for review next week.
> 
> I have a new update in QEMU which allows QEMU to automatically
> programing the device HDM decoders and the Host-bridge HDM decoder
> 
> With this update, after the QEMU guest booted,  we can see that the kernel
> will automatically construct a Cxl region for the emulated memory device
> according the programed HDM decoders.
> 
> If you are interested in it, please check following branch:
> https://github.com/zhijianli88/qemu/tree/program-decoder
> 
> Note:
> Only one host-bridge + one memdev topo is tested
> 
> An CXL qemu command line example:
> -device pcie-root-port,id=pci-root,slot=4,bus=pcie.0,chassis=0 \ -device pxb-
> cxl,id=pxb-cxl.0,bus=pcie.0,bus_nr=0x35,hdm_for_passthrough=true \ -device
> cxl-rp,id=cxl-rp-hb0rp0,bus=pxb-cxl.0,chassis=0,slot=0,port=0 \ -device cxl-
> type3,bus=cxl-rp-hb0rp0,volatile-memdev=cxl-mem0,id=cxl-type3-cxl-
> pmem0,program-hdm-decoder=true \ -object memory-backend-file,id=cxl-
> mem0,share=on,mem-path=/home/lizhijian/images/cxltest0.raw,size=4G \ -
> M cxl=on,cxl-fmw.0.targets.0=pxb-cxl.0,cxl-fmw.0.size=64G,cxl-
> fmw.0.interleave-granularity=8k \ -bios /home/lizhijian/seabios/out/bios.bin
> 
> I would also like to express my gratitude to Goto-san(Cc'ing) for his
> contributions to the code regarding soft-reserved emulation, which includes
> work on both QEMU and SeaBIOS.
> 
> Finally, it would be greatly appreciated if you could share status of your V3
> patch.
> 
> 
> Thanks
> Zhijian
> 
> > -----Original Message-----
> > From: Bowman, Terry <terry.bowman@amd.com>
> > Sent: Saturday, March 8, 2025 7:05 AM here at home YouTube we'll see
> > what happens
> > To: Li, Zhijian/李 智坚 <lizhijian@fujitsu.com>; Fontenot, Nathan
> > <nafonten@amd.com>; David Hildenbrand <david@redhat.com>; Fan Ni
> > <nifan.cxl@gmail.com>
> > Cc: linux-cxl@vger.kernel.org; dan.j.williams@intel.com;
> > alison.schofield@intel.com; linux-mm@kvack.org; gourry@gourry.net;
> > PradeepVineshReddy.Kodamati@amd.com
> > Subject: Re: [PATCH v2 1/4] kernel/resource: Introduce managed SOFT
> > RESERVED resources
> >
> >
> > Hi Zhijian,
> >
> > Nathan asked me to finish the patchset submission in his place. He has
> > the
> > v3 iteration ready and I plan to send this for review next week.
> >
> > Can you share the QEMU changes for simulating the situation? Using
> > QEMU would be very helpful.
> >
> > Thanks for offering to help test and review.
> >
> > Regards,
> > Terry
> >
> >
> >


  reply	other threads:[~2025-03-23  8:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 17:42 [PATCH v2 0/4] Add managed SOFT RESERVE resource handling Nathan Fontenot
2025-01-16 17:42 ` [PATCH v2 1/4] kernel/resource: Introduce managed SOFT RESERVED resources Nathan Fontenot
2025-01-21  8:19   ` David Hildenbrand
2025-01-21 18:57     ` Fontenot, Nathan
2025-01-22  6:03       ` Fan Ni
2025-01-23 15:49         ` Fontenot, Nathan
2025-01-27 14:40           ` David Hildenbrand
2025-01-27 18:46             ` Fontenot, Nathan
2025-03-07  5:56               ` Zhijian Li (Fujitsu)
2025-03-07 16:47                 ` Alison Schofield
2025-03-10  5:52                   ` Li Zhijian
2025-03-07 23:05                 ` Bowman, Terry
2025-03-10  6:00                   ` Zhijian Li (Fujitsu)
2025-03-23  8:24                   ` Zhijian Li (Fujitsu)
2025-03-23  8:33                     ` Zhijian Li (Fujitsu) [this message]
2025-01-22  5:52   ` Fan Ni
2025-01-23 15:55     ` Fontenot, Nathan
2025-01-16 17:42 ` [PATCH v2 2/4] cxl: Update Soft Reserve resources upon region creation Nathan Fontenot
2025-01-16 17:42 ` [PATCH v2 3/4] dax: Update hmem resource/device registration Nathan Fontenot
2025-01-16 22:28   ` Ira Weiny
2025-01-21 18:49     ` Fontenot, Nathan
2025-01-21 23:14       ` Ira Weiny
2025-01-23 16:01         ` Fontenot, Nathan
2025-01-27 18:44           ` Fontenot, Nathan
2025-01-16 17:42 ` [PATCH v2 4/4] Add SOFT RESERVE resource notification chain Nathan Fontenot

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=TY1PR01MB1562BBB0BD9235811B3DEA66A5A52@TY1PR01MB1562.jpnprd01.prod.outlook.com \
    --to=lizhijian@fujitsu.com \
    --cc=PradeepVineshReddy.Kodamati@amd.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=gourry@gourry.net \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nafonten@amd.com \
    --cc=nifan.cxl@gmail.com \
    --cc=terry.bowman@amd.com \
    --cc=y-goto@fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox