All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Itaru Kitayama <itaru.kitayama@linux.dev>
Cc: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>, <qemu-devel@nongnu.org>
Subject: Re: CXL emulation on aarch64
Date: Thu, 16 Jan 2025 10:58:33 +0000	[thread overview]
Message-ID: <20250116105833.000056da@huawei.com> (raw)
In-Reply-To: <88E9D774-A760-45F7-A173-24A07BB55733@linux.dev>

On Thu, 16 Jan 2025 15:04:53 +0900
Itaru Kitayama <itaru.kitayama@linux.dev> wrote:

> Hi Jonathan,
> 
> > On Jan 14, 2025, at 19:26, Jonathan Cameron <Jonathan.Cameron@huawei.com> wrote:
> > 
> > On Tue, 14 Jan 2025 12:03:03 +0900
> > Itaru Kitayama <itaru.kitayama@linux.dev> wrote:
> >   
> >> Hi Jonathan, 
> >>   
> >>> On Jan 10, 2025, at 21:31, Jonathan Cameron <Jonathan.Cameron@huawei.com> wrote:
> >>> 
> >>> On Fri, 10 Jan 2025 09:20:54 +0000
> >>> "Zhijian Li (Fujitsu)" via <qemu-devel@nongnu.org> wrote:
> >>>   
> >>>> On 10/01/2025 13:29, Itaru Kitayama wrote:    
> >>>>> Hi,
> >>>>> Is anybody working on the CXL emulation on aarch64?      
> >>>> 
> >>>> I'm not currently working on the CXL emulation on aarch64.
> >>>> 
> >>>> However, IIRC the CXL maintainer's tree should work.
> >>>> https://gitlab.com/jic23/qemu/    
> >>> 
> >>> Pick up latest branch from there. I'm prepping a rebased version
> >>> with some new stuff but might take a few more days.    
> >> 
> >> Thanks for sharing your work with us.  Your master and cxl-2024-11-27 branches give:
> >> 
> >> $ qemu-system-aarch64: -accel tcg,cxl=on: Property 'tcg-accel.cxl' not found  
> > 
> > cxl is a machine property not a accel one. So needs to be after virt
> > There are tests in the tree for bios tables. Copy the command line from those.
> >   
> >> 
> >> My commands are below:
> >> $HOME/projects/qemu/build/qemu-system-aarch64 \
> >>        -M virt,virtualization=on,gic-version=3 \
> >>        -M acpi=off -cpu max,sme=off -m 8G -smp 4 \
> >>        -accel tcg,cxl=on \
> >>        -nographic \
> >>        -bios $HOME/cca-v4/out/bin/flash.bin \
> >>        -kernel Image-cca \
> >>        -drive format=raw,if=none,file=$HOME/cca-v4/out-or/images/rootfs.ext2,id=hd0 \
> >>        -device virtio-blk-pci,drive=hd0 \
> >>        -append root=/dev/vda \
> >>        -nodefaults \
> >>        --serial tcp:localhost:54320 \
> >>         -serial tcp:localhost:54321 \
> >>         -append "root=/dev/vda earlycon console=hvc0" \
> >>         -device virtio-net-pci,netdev=net0 \
> >>         -netdev user,id=net0 \
> >>         -device virtio-9p-device,fsdev=shr0,mount_tag=shr0 \
> >>         -fsdev local,security_model=none,path=../../,id=shr0
> >> 
> >> Yes, I’m using Linaro’s CCA capable OP-TEE builds above.  
> > 
> > I'm a little curious why optee is relevant for this but shouldn't matter as long
> > as an appropriate EDK2 is loaded.
> >   
> 
> I picked up your tree’s “master” and “cxl-next” as of today, and only the latter at least booted.
> The former gives:
> 
> qemu-system-aarch64: Property 'virt-9.2-machine.cxl' not found
> 
> Should I stick with the cxl-next? My concern is that the base QEMU version is a bit old
> 7.0.50.

Always use the latest dated branch on that tree.  I release whenever there
is something new to carry or a major rebase needed.

cxl-<date> is the right branch to use. Hope that helps.

Jonathan

> 
> Thanks,
> Itaru.
> 
> > Jonathan
> >   
> >> 
> >> Let me know which branch you were suggesting.
> >> 
> >> Thanks,
> >> Itaru. 
> >>   
> >>> 
> >>> Note my main development work is on arm64 so that tends to work
> >>> more reliably than x86 which I only lightly test for stuff that
> >>> isn't ready for upstream yet.
> >>> 
> >>> Give me a shout if you run into any problems.
> >>> 
> >>> The main blocker on upstreaming this is resolving the missing device tree
> >>> support for PCI expander bridges.  I've not made any progress on this since
> >>> talk at Linaro connect in 2023.
> >>> 
> >>> Jonathan
> >>> 
> >>>   
> >>>> 
> >>>> 
> >>>> Thanks
> >>>> Zhijian
> >>>>   
> >>>>> If there’s a WIP branch, a pointer would be appreciated.
> >>>>> 
> >>>>> Itaru      
> 
> 



  reply	other threads:[~2025-01-16 10:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  5:29 CXL emulation on aarch64 Itaru Kitayama
2025-01-10  9:20 ` Zhijian Li (Fujitsu) via
2025-01-10 12:31   ` Jonathan Cameron via
2025-01-14  3:03     ` Itaru Kitayama
2025-01-14 10:26       ` Jonathan Cameron via
2025-01-16  6:04         ` Itaru Kitayama
2025-01-16 10:58           ` Jonathan Cameron via [this message]
2025-01-17  0:24             ` Itaru Kitayama
2025-01-17  9:34               ` Jonathan Cameron via
2025-01-17  1:13             ` Itaru Kitayama
2025-01-17  9:43               ` Jonathan Cameron via
2025-01-22 14:07                 ` Jonathan Cameron via
2025-01-29  1:14                   ` Itaru Kitayama
2025-01-29 17:16                     ` Jonathan Cameron via
2025-01-29 23:06                       ` Itaru Kitayama

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=20250116105833.000056da@huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=itaru.kitayama@linux.dev \
    --cc=lizhijian@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 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.