Re: CXL memory pooling emulation inqury

2025-04-10 Thread Fan Ni
On Wed, Mar 12, 2025 at 03:33:12PM -0400, Gregory Price wrote: > On Wed, Mar 12, 2025 at 06:05:43PM +, Jonathan Cameron wrote: > > > > Longer term I remain a little unconvinced by whether this is the best > > approach > > because I also want a single management path (so fake CCI etc) and that

Re: CXL memory pooling emulation inqury

2025-03-13 Thread Fan Ni
On Wed, Mar 12, 2025 at 03:33:12PM -0400, Gregory Price wrote: > On Wed, Mar 12, 2025 at 06:05:43PM +, Jonathan Cameron wrote: > > > > Longer term I remain a little unconvinced by whether this is the best > > approach > > because I also want a single management path (so fake CCI etc) and that

Re: CXL memory pooling emulation inqury

2025-03-12 Thread Gregory Price
On Wed, Mar 12, 2025 at 06:05:43PM +, Jonathan Cameron wrote: > > Longer term I remain a little unconvinced by whether this is the best approach > because I also want a single management path (so fake CCI etc) and that may > need to be exposed to one of the hosts for tests purposes. In the cu

Re: CXL memory pooling emulation inqury

2025-03-12 Thread Jonathan Cameron via
On Mon, 10 Mar 2025 16:02:45 +0800 Junjie Fu wrote: > > Note though that there is a long way to go before we can do what you > > want. The steps I'd expect to see along the way: > > > > 1) Emulate an Multi Headed Device. > >Initially connect two heads to different host bridges on a single QE

CXL memory pooling emulation inqury

2025-03-11 Thread Junjie Fu
> Note though that there is a long way to go before we can do what you > want. The steps I'd expect to see along the way: > > 1) Emulate an Multi Headed Device. >Initially connect two heads to different host bridges on a single QEMU >machine. That lets us test most of the code flows witho