| Message ID | cover.1692181079.git.oleksii.kurochko@gmail.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Enable build of full Xen for RISC-V | expand |
On 16.08.2023 12:19, Oleksii Kurochko wrote: > This patch series performs all of the additions necessary to drop the > build overrides for RISCV and enable the full Xen build. Except in cases > where compatibile implementations already exist (e.g. atomic.h and > bitops.h), the newly added definitions are simple. > > Also the patch series has open question described in the patch 57 > > Patch 56 is only needed for test purposes and will be removed. > > Oleksii Kurochko (57): > xen/riscv:introduce asm/byteorder.h > xen/riscv: add public arch-riscv.h > xen/riscv: introduce spinlock.h > xen/riscv: introduce fence.h > xen/riscv: introduce arch-riscv/hvm/save.h > xen/riscv: introduce paging.h > xen/riscv: introduce asm/cpufeature.h > xen/riscv: introduce asm/device.h > xen/riscv: introduce asm/event.h > xen/riscv: introduce asm/grant_table.h > xen/riscv: introduce asm/guest_atomics.h > xen/riscv: introduce asm/hypercall.h > xen/riscv: introduce asm/iocap.h > xen/riscv: introduce asm/iommu.h > xen/riscv: introduce asm/mem_access.h > xen/riscv: introduce asm/nospec.h > xen/riscv: introduce asm/pci.h > xen/riscv: introduce asm/random.h > xen/riscv: introduce asm/setup.h > xen/riscv: introduce asm/system.h > xen/riscv: introduce asm/xenoprof.h > xen/riscv: introduce bitops.h > xen/riscv: introduce flushtlb.h > xen/riscv: introduce asm/percpu.h > xen/riscv: introduce asm/smp.h > xen/riscv: introduce asm/atomic.h > xen/riscv: introduce cmpxchg.h > xen/riscv: introduce asm/io.h > xen/riscv: introduce asm/hardirq.h > xen/riscv: introduce div64.h > xen/riscv: define bug frame tables in xen.lds.S > xen/riscv: introduce bit operations > xen/riscv: introduce asm/altp2m.h > xen/riscv: introduce asm/delay.h > xen/riscv: introduce asm/domain.h > xen/riscv: introduce asm/guest_access.h > xen/riscv: introduce asm/irq.h > xen/riscv: introduce asm/monitor.h > xen/riscv: introduce asm/numa.h > xen/riscv: introduce asm/p2m.h > xen/riscv: introduce asm/regs.h > xen/riscv: introduce asm/softirq.h > xen/riscv: introduce asm/time.h > xen/riscv: introduce asm/vm_event.h > xen/riscv: add definition of __read_mostly > xen/riscv: define an address of frame table > xen/riscv: add required things to asm/current.h > xen/riscv: add minimal stuff to asm/page.h to build full Xen > xen/riscv: add minimal stuff to asm/processor.h to build full Xen > xen/riscv: add minimal stuff to asm/smp.h to build full Xen > xen: add RISCV support for pmu.h > xen: add necessary headers to common to build full Xen for RISC-V > xen/riscv: add minimal stuff to asm/mm.h to build full Xen > xen/rirscv: add minimal amount of stubs to build full Xen > xen/riscv: enable full Xen build > test only riscv > xxxen/riscv: WIP ( need advise ) Just to clarify: With the later 29-patch series superseding fair parts of this, is there still any need to look at this (version of this) series in any detail? Jan
On Thu, 2023-10-19 at 13:53 +0200, Jan Beulich wrote: > On 16.08.2023 12:19, Oleksii Kurochko wrote: > > This patch series performs all of the additions necessary to drop > > the > > build overrides for RISCV and enable the full Xen build. Except in > > cases > > where compatibile implementations already exist (e.g. atomic.h and > > bitops.h), the newly added definitions are simple. > > > > Also the patch series has open question described in the patch 57 > > > > Patch 56 is only needed for test purposes and will be removed. > > > > Oleksii Kurochko (57): > > xen/riscv:introduce asm/byteorder.h > > xen/riscv: add public arch-riscv.h > > xen/riscv: introduce spinlock.h > > xen/riscv: introduce fence.h > > xen/riscv: introduce arch-riscv/hvm/save.h > > xen/riscv: introduce paging.h > > xen/riscv: introduce asm/cpufeature.h > > xen/riscv: introduce asm/device.h > > xen/riscv: introduce asm/event.h > > xen/riscv: introduce asm/grant_table.h > > xen/riscv: introduce asm/guest_atomics.h > > xen/riscv: introduce asm/hypercall.h > > xen/riscv: introduce asm/iocap.h > > xen/riscv: introduce asm/iommu.h > > xen/riscv: introduce asm/mem_access.h > > xen/riscv: introduce asm/nospec.h > > xen/riscv: introduce asm/pci.h > > xen/riscv: introduce asm/random.h > > xen/riscv: introduce asm/setup.h > > xen/riscv: introduce asm/system.h > > xen/riscv: introduce asm/xenoprof.h > > xen/riscv: introduce bitops.h > > xen/riscv: introduce flushtlb.h > > xen/riscv: introduce asm/percpu.h > > xen/riscv: introduce asm/smp.h > > xen/riscv: introduce asm/atomic.h > > xen/riscv: introduce cmpxchg.h > > xen/riscv: introduce asm/io.h > > xen/riscv: introduce asm/hardirq.h > > xen/riscv: introduce div64.h > > xen/riscv: define bug frame tables in xen.lds.S > > xen/riscv: introduce bit operations > > xen/riscv: introduce asm/altp2m.h > > xen/riscv: introduce asm/delay.h > > xen/riscv: introduce asm/domain.h > > xen/riscv: introduce asm/guest_access.h > > xen/riscv: introduce asm/irq.h > > xen/riscv: introduce asm/monitor.h > > xen/riscv: introduce asm/numa.h > > xen/riscv: introduce asm/p2m.h > > xen/riscv: introduce asm/regs.h > > xen/riscv: introduce asm/softirq.h > > xen/riscv: introduce asm/time.h > > xen/riscv: introduce asm/vm_event.h > > xen/riscv: add definition of __read_mostly > > xen/riscv: define an address of frame table > > xen/riscv: add required things to asm/current.h > > xen/riscv: add minimal stuff to asm/page.h to build full Xen > > xen/riscv: add minimal stuff to asm/processor.h to build full Xen > > xen/riscv: add minimal stuff to asm/smp.h to build full Xen > > xen: add RISCV support for pmu.h > > xen: add necessary headers to common to build full Xen for RISC-V > > xen/riscv: add minimal stuff to asm/mm.h to build full Xen > > xen/rirscv: add minimal amount of stubs to build full Xen > > xen/riscv: enable full Xen build > > test only riscv > > xxxen/riscv: WIP ( need advise ) > > Just to clarify: With the later 29-patch series superseding fair > parts of this, > is there still any need to look at this (version of this) series in > any detail? > It depends on if headers mentioned in 29-patch series should be in asm- generic folder or in arch specific folder. I think we can start look at 29-patch series and after it will be merged ( or finished in some way ) I'll resend this one patch series. ~ Oleksii