CVS log for src/sys/arch/xen/xen/xenmem.c
Up to [cvs.NetBSD.org] / src / sys / arch / xen / xen
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Revision 1.5: download - view: text, markup, annotated - select for diffs
Wed Dec 20 15:34:46 2023 UTC (15 months ago) by thorpej
Branches: MAIN
CVS tags: perseant-exfatfs-base-20240630,
perseant-exfatfs-base,
perseant-exfatfs,
HEAD
Diff to: previous 1.4: preferred, colored
Changes since revision 1.4: +2 -3
lines
Remove unnecessary <sys/malloc.h>.
Revision 1.4: download - view: text, markup, annotated - select for diffs
Fri Sep 2 05:09:49 2022 UTC (2 years, 6 months ago) by kre
Branches: MAIN
CVS tags: thorpej-ifq-base,
thorpej-ifq,
thorpej-altq-separation-base,
thorpej-altq-separation,
netbsd-10-base,
netbsd-10-1-RELEASE,
netbsd-10-0-RELEASE,
netbsd-10-0-RC6,
netbsd-10-0-RC5,
netbsd-10-0-RC4,
netbsd-10-0-RC3,
netbsd-10-0-RC2,
netbsd-10-0-RC1,
netbsd-10,
bouyer-sunxi-drm-base,
bouyer-sunxi-drm
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +3 -3
lines
Fix the syntax of the non _LP64 code fragment to match that in the
_LP64 fragment, so hopefully 32 bit ports with XEN (i386) will
build again.
Revision 1.3: download - view: text, markup, annotated - select for diffs
Thu Sep 1 16:28:08 2022 UTC (2 years, 6 months ago) by bouyer
Branches: MAIN
Diff to: previous 1.2: preferred, colored
Changes since revision 1.2: +6 -4
lines
Call extent_alloc_subregion() with EX_MALLOCOK; under heavy I/O load we need
lots of them and the preallocatted extent descriptors are not enough.
Revision 1.2: download - view: text, markup, annotated - select for diffs
Wed Aug 31 12:53:27 2022 UTC (2 years, 6 months ago) by bouyer
Branches: MAIN
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +2 -29
lines
Remove XENPV support from xenmem; it's only used for !XENPV at this time.
Revision 1.1: download - view: text, markup, annotated - select for diffs
Wed Aug 31 12:51:56 2022 UTC (2 years, 6 months ago) by bouyer
Branches: MAIN
Work in progress on dom0 PVH support: ioctl support for tools.
Basically, in PVH mode (where XENFEAT_auto_translated_physmap is enabled),
the hypervisor will not map foreing ressources in our virtual address
space for us. Instead, we have to pass it an address in our physical
address space (but not mapped to some RAM) where the ressource will show up
and then enter this PA in pour page table.
For this, introduce xenmem_* which manage the PA space. In PVH mode this
is just allocated from the iomem_ex extent.
With this, I can start a PV domU, and the guest's kernel boots (and
the console works). It hangs because the backend driver can't map the
frontend ressources (yet).
Note that, per https://xenbits.xen.org/docs/unstable/support-matrix.html,
dom0 PVH support is still considered experimental by Xen.
CVSweb <webmaster@jp.NetBSD.org>