| History log of /src/sys/arch/xen/x86/xen_bus_dma.c |
| Revision | | Date | Author | Comments |
| 1.34 |
| 14-May-2024 |
andvar | fix recently committed typos by msaitoh in few more places, as well as few more.
mainly s/contigous/contiguous/ and s/miliseconds/milliseconds/ in comments.
|
| 1.33 |
| 20-Aug-2022 |
riastradh | x86: Split most of pmap.h into pmap_private.h or vmparam.h.
This way pmap.h only contains the MD definition of the MI pmap(9)
API, which loads of things in the kernel rely on, so changing x86
pmap internals no longer requires recompiling the entire kernel every
time.
Callers needing these internals must now use machine/pmap_private.h.
Note: This is not x86/pmap_private.h because it contains three parts:
1. CPU-specific (different for i386/amd64) definitions used by...
2. common definitions, including Xenisms like xpmap_ptetomach,
further used by...
3. more CPU-specific inlines for pmap_pte_* operations
So {amd64,i386}/pmap_private.h defines 1, includes x86/pmap_private.h
for 2, and then defines 3. Maybe we should split that out into a new
pmap_pte.h to reduce this trouble.
No functional change intended, other than that some .c files must
include machine/pmap_private.h when previously uvm/uvm_pmap.h
polluted the namespace with pmap internals.
Note: This migrates part of i386/pmap.h into i386/vmparam.h --
specifically the parts that are needed for several constants defined
in vmparam.h:
VM_MAXUSER_ADDRESS
VM_MAX_ADDRESS
VM_MAX_KERNEL_ADDRESS
VM_MIN_KERNEL_ADDRESS
Since i386 needs PDP_SIZE in vmparam.h, I added it there on amd64
too, just to keep things parallel.
|
| 1.32 |
| 06-May-2020 |
bouyer | Make MP-safe: make sure the xpq_queue* are flushed before making the
pages visible to UVM.
|
| 1.31 |
| 25-Apr-2020 |
bouyer | Merge the bouyer-xenpvh branch, bringing in Xen PV drivers support under HVM
guests in GENERIC.
Xen support can be disabled at runtime with
boot -c
disable hypervisor
|
| 1.30 |
| 10-Apr-2020 |
jdolecek | add and pass dma tag to PV drivers attached to xenbus, so thay can
use bus_dmamap_load_mbuf() et.al.
due to XENPV override, _BUS_BUS_TO_PHYS() dmamap segment ds_addr
gets filled with ma, so value can be directly used for e.g. grant calls
|
| 1.29 |
| 09-Apr-2020 |
jdolecek | update to __XEN_INTERFACE_VERSION__ 0x0003020a aka Xen 3.2.10
this brings grant memory v2 support:
- status separated from flags - revoking access needs just memory barrier,
no need for expensive cmpxchg16 any more
- sub-page hypervisor copy-only grants, to be used by xennet(4)
- 64-bit frame, i.e. support for DomU RAM >16TB
the grant table is now always allocated on boot to maximum size, it's now
never grown in runtime; switch back to regular kmem_alloc()/kmem_free()
code now requires v2 support, no compatibility for grant version 1 retained -
Xen v2 support predates all currently supported Xen versions
also interface for baloon changed slightly, code updated
|
| 1.28 |
| 03-Sep-2018 |
riastradh | branches: 1.28.10;
Rename min/max -> uimin/uimax for better honesty.
These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.
HOWEVER! Some subsystems have
#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))
even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.
To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.
I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:
cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))
It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.
Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)
|
| 1.27 |
| 24-Jun-2018 |
jdolecek | branches: 1.27.2;
mark with XXXSMP all remaining spl*() and tsleep() calls
|
| 1.26 |
| 30-Jun-2012 |
jym | branches: 1.26.38;
Use setter to set xenguest_handles.
|
| 1.25 |
| 30-Jun-2012 |
jym | Extend the xpmap API, as described in [1]. This change is mechanical and
avoids exposing the MD phys_to_machine/machine_to_phys tables directly.
Added:
- xpmap_ptom handles PFN (pseudo physical) to MFN (machine frame number)
translations, and is under control of the domain.
- xpmap_mtop is its counterpart (MFN to PFN), and is under control of
hypervisor.
xpmap_ptom_map() map a pseudo-phys address to a machine address
xpmap_ptom_unmap() unmap a pseudo-phys address (invalidation)
xpmap_ptom_isvalid() check for pseudo-phys address validity
The parameters are physical/machine addresses, like bus_dma/bus_space(9).
As x86 MFNs are tracked by u_long (Xen's choice) while machine addresses
can be 64 bits entities (PAE), use ptoa() to avoid truncation when bit
shifting by PAGE_SHIFT.
I kept the same namespace (xpmap_) to avoid code churn.
[1] http://mail-index.netbsd.org/port-xen/2009/05/09/msg004951.html
XXX will document ptoa/atop/trunc_page separately.
|
| 1.24 |
| 27-Jun-2012 |
jym | Retire XEN_COMPAT_030001 as detailed on port-xen@:
http://mail-index.netbsd.org/port-xen/2012/06/25/msg007431.html
The xen_p2m API comes next.
ok bouyer@.
Tested on i386 PAE and amd64 (Xen 3.3 on private test bed, and
Xen 3.4 for Amazon EC2).
FWIW, Amazon always reported:
hypervisor0 at mainbus0: Xen version 3.4.3-kaos_t1micro
multiple times for Europe and US West-1, so I guess they are now at
3.4 (32 and 64 bits).
|
| 1.23 |
| 01-Jul-2011 |
dyoung | branches: 1.23.2;
#include <sys/bus.h> instead of <machine/bus.h>.
|
| 1.22 |
| 12-Nov-2010 |
njoly | branches: 1.22.6;
Include uvm.h not uvm_extern.h following recent changes.
|
| 1.21 |
| 22-Mar-2010 |
bouyer | bus_dmamem_alloc() may not get a boundary smaller than size, but
it's perfectly valid for bus_dmamap_create() to do so (a contigous
transfers will then split in multiple segment).
Fix _xen_bus_dmamem_alloc_range() and _bus_dmamem_alloc_range() to
allow a boundary limit smaller than size:
- compute appropriate boundary for uvm_pglistalloc(), wich doesn't
accept boundary < size
- also take care of boundary when deciding to start a new segment.
While there, remove useless boundary argument to _xen_alloc_contig().
Fix the boundary-related issue of PR port-amd64/42980
|
| 1.20 |
| 09-Mar-2010 |
jym | branches: 1.20.2;
Although Xen's documentation states that the address_bits field is not used
by XENMEM_decrease_reservation, it is checked by the hypervisor. In certain
circumstances (stack leak), the field could have an improper value, leading
to a fail of the hypercall.
Set it to 0 ("no addressing restriction") to avoid that.
Patch tested by Sam Fourman and haad@.
This should fix the rare "failed allocating DMA memory" encountered
under NetBSD dom0. Will ask for a pull-up.
|
| 1.19 |
| 02-Mar-2010 |
jym | Catch the return value from the XENMEM_decrease_reservation hypercall,
and not some error value stored earlier.
While here, fix a typo in a comment.
|
| 1.18 |
| 27-Feb-2010 |
jym | Make a XENMEM_decrease_reservation DEBUG printf() more meaningful.
|
| 1.17 |
| 12-Feb-2010 |
jym | Starting with Xen 3 API, MMU_EXTENDED_COMMAND (tlb flush, cache flush, page
pinning/unpinning, set_ldt, invlpg) operations cannot be queued in the
xpq_queue[] any more, as they use their own specific hypercall, mmuext_op().
Their associated xpq_queue_*() functions already call xpq_flush_queue()
before issuing the mmuext_op() hypercall, which makes these xpq_flush_queue()
calls not necessary.
Rapidly discussed with bouyer@ in private mail. XEN3_DOM0/XEN3PAE_DOM0 tested
through a build.sh release, amd64 was only compile tested. No regression
expected.
|
| 1.16 |
| 23-Jan-2010 |
cegger | branches: 1.16.2;
fix address overflow with 32bit PAE.
Reported and tested by Mark Davies on port-xen@.
|
| 1.15 |
| 29-Jul-2009 |
cegger | remove Xen2 support.
ok bouyer@
|
| 1.14 |
| 24-Jan-2009 |
bouyer | branches: 1.14.2;
Properly check the return value of HYPERVISOR_memory_op(): it returns
the number of successfull operations, so a return value of 0 is also
a failure.
|
| 1.13 |
| 18-Dec-2008 |
cegger | remove unused malloc.h
|
| 1.12 |
| 13-Nov-2008 |
cegger | Finish preparation to new interface.
New interface not yet used by default. It needs some testing first.
|
| 1.11 |
| 04-Jun-2008 |
ad | branches: 1.11.4; 1.11.6; 1.11.8; 1.11.12;
vm_page: put TAILQ_ENTRY into a union with LIST_ENTRY, so we can use both.
|
| 1.10 |
| 28-Apr-2008 |
martin | branches: 1.10.2;
Remove clause 3 and 4 from TNF licenses
|
| 1.9 |
| 24-Feb-2007 |
bouyer | branches: 1.9.42; 1.9.44; 1.9.46;
Properly honnor bus_dma bus address range restriction for Xen3 (the Xen2
interface doesn't allow it), so that .e.g bus_dma_subregion() has a chance
to work. Unfortunably a stock Xen hypervisor won't allow a upper bound less
than 2^31 (2GB) so devices like bce(4) will need a hacked hypervisor to
work properly.
|
| 1.8 |
| 03-Sep-2006 |
bouyer | branches: 1.8.6; 1.8.8;
Wrap some printfs in #ifdef DEBUG, as we should not leak memory any more when
bus_dma memory allocation fails.
|
| 1.7 |
| 28-Aug-2006 |
bouyer | Some bus_dma(9) fixes for Xen:
- Attempt to gracefully recover from a failed decrease_reservation or
increase_reservation, by avoiding physical memory loss.
- always store a machine address in ds_addr; this avoids some mistakes
where machine address would in some case be freed at physical address, or
mapped as physical address.
|
| 1.6 |
| 15-Jan-2006 |
bouyer | branches: 1.6.2; 1.6.6; 1.6.16; 1.6.18;
Snapshot of work in progress on NetBSD port to Xen3:
- kernel (both dom0 and domU) boot, console is functionnal and it can starts
software from a ramdisk
- there is no driver front-end expect console for domU yet.
- dom0 can probe devices and ex(4) work when Xen3 is booted without acpi
and apic support. But the on-board IDE doens't get interrupts.
The PCI code still needs work (it's hardcoded to mode 1). Some of this
code should be shared with ../x86
The physical insterrupt code needs to get MPBIOS and ACPI support, and
do interrupt routing to properly interract with Xen.
To enable Xen-3.0 support, add
options XEN3
to your kernel config file (this will disable Xen2 support)
Changes affecting Xen-2.0 support (no functionnal changes intended):
- get more constants from genassym for assembly code
- remove some unneeded registers move from start()
- map the shared info page from start(), and remove the pte = 0xffffffff hack
- vector.S: in hypervisor_callback() make sure %esi points to
HYPERVISOR_shared_info before accessing the info page. Remplace some
hand-written assembly with the equivalent macro defined in frameasm.h
- more debug code, dissabled by default.
while here added my copyright on some files I worked on in 2005.
|
| 1.5 |
| 24-Dec-2005 |
perry | branches: 1.5.2;
__asm__ -> __asm
__const__ -> const
__inline__ -> inline
__volatile__ -> volatile
|
| 1.4 |
| 11-Dec-2005 |
christos | merge ktrace-lwp.
|
| 1.3 |
| 22-Aug-2005 |
bouyer | branches: 1.3.2; 1.3.8;
Fix a memory leak. Thanks to YAMAMOTO Takashi for the notice.
|
| 1.2 |
| 20-Aug-2005 |
bouyer | Also properly check the alignement and boundary constraints.
|
| 1.1 |
| 20-Aug-2005 |
bouyer | Deal with the machine address space being non-contigous in bus_dmamem_alloc():
- Define _BUS_AVAIL_END to 0xffffffff, as we don't have an easy way to
find the upper bound for our machine address space (and this can change
when we swap pages with the hypervisor).
- implement _xen_bus_dmamem_alloc_range(), which will request a contigous
set of pages to the hypervisor if the pages returned by uvm_pglistalloc()
don't fit the constraints.
We can't deal with the low/high constraints yet, because Xen doesn't offer a
way to get pages in a specific ranges of addresses.
Based on patches from Dave Thompson (in private mail), with heavy hacking
by me.
|
| 1.3.8.2 |
| 10-Nov-2005 |
skrll | Sync with HEAD. Here we go again...
|
| 1.3.8.1 |
| 22-Aug-2005 |
skrll | file xen_bus_dma.c was added on branch ktrace-lwp on 2005-11-10 14:00:34 +0000
|
| 1.3.2.5 |
| 16-Sep-2006 |
ghen | Pull up following revision(s) (requested by bouyer in ticket #1510):
sys/arch/xen/x86/xen_bus_dma.c: revision 1.7
sys/arch/xen/x86/xen_bus_dma.c: revision 1.8
sys/arch/x86/include/bus_private.h: revision 1.6
sys/arch/x86/x86/bus_dma.c: revision 1.30
sys/arch/xen/include/bus_private.h: revision 1.7
Some bus_dma(9) fixes for Xen:
- Attempt to gracefully recover from a failed decrease_reservation or
increase_reservation, by avoiding physical memory loss.
- always store a machine address in ds_addr; this avoids some mistakes
where machine address would in some case be freed at physical address, or
mapped as physical address.
Wrap some printfs in #ifdef DEBUG, as we should not leak memory any more when
bus_dma memory allocation fails.
|
| 1.3.2.4 |
| 25-Aug-2005 |
tron | Pull up following revision(s) (requested by bouyer in ticket #696):
sys/arch/xen/x86/xen_bus_dma.c: revision 1.3
Fix a memory leak. Thanks to YAMAMOTO Takashi for the notice.
|
| 1.3.2.3 |
| 25-Aug-2005 |
tron | Pull up following revision(s) (requested by bouyer in ticket #696):
sys/arch/xen/x86/xen_bus_dma.c: revision 1.2
Also properly check the alignement and boundary constraints.
|
| 1.3.2.2 |
| 25-Aug-2005 |
tron | Pull up following revision(s) (requested by bouyer in ticket #696):
sys/arch/xen/x86/xen_bus_dma.c: revision 1.1
sys/arch/xen/include/bus_private.h: revision 1.2
sys/arch/xen/conf/files.xen: revision 1.28
Deal with the machine address space being non-contigous in bus_dmamem_alloc():
- Define _BUS_AVAIL_END to 0xffffffff, as we don't have an easy way to
find the upper bound for our machine address space (and this can change
when we swap pages with the hypervisor).
- implement _xen_bus_dmamem_alloc_range(), which will request a contigous
set of pages to the hypervisor if the pages returned by uvm_pglistalloc()
don't fit the constraints.
We can't deal with the low/high constraints yet, because Xen doesn't offer a
way to get pages in a specific ranges of addresses.
Based on patches from Dave Thompson (in private mail), with heavy hacking
by me.
|
| 1.3.2.1 |
| 22-Aug-2005 |
tron | file xen_bus_dma.c was added on branch netbsd-3 on 2005-08-25 20:49:54 +0000
|
| 1.5.2.1 |
| 01-Feb-2006 |
yamt | sync with head.
|
| 1.6.18.1 |
| 14-Sep-2006 |
riz | Pull up following revision(s) (requested by bouyer in ticket #150):
sys/arch/xen/x86/xen_bus_dma.c: revision 1.7
sys/arch/xen/x86/xen_bus_dma.c: revision 1.8
sys/arch/x86/include/bus_private.h: revision 1.6
sys/arch/x86/x86/bus_dma.c: revision 1.30
sys/arch/xen/include/bus_private.h: revision 1.7
Some bus_dma(9) fixes for Xen:
- Attempt to gracefully recover from a failed decrease_reservation or
increase_reservation, by avoiding physical memory loss.
- always store a machine address in ds_addr; this avoids some mistakes
where machine address would in some case be freed at physical address, or
mapped as physical address.
Wrap some printfs in #ifdef DEBUG, as we should not leak memory any more when
bus_dma memory allocation fails.
|
| 1.6.16.4 |
| 26-Feb-2007 |
yamt | sync with head.
|
| 1.6.16.3 |
| 30-Dec-2006 |
yamt | sync with head.
|
| 1.6.16.2 |
| 21-Jun-2006 |
yamt | sync with head.
|
| 1.6.16.1 |
| 15-Jan-2006 |
yamt | file xen_bus_dma.c was added on branch yamt-lazymbuf on 2006-06-21 14:58:23 +0000
|
| 1.6.6.2 |
| 14-Sep-2006 |
yamt | sync with head.
|
| 1.6.6.1 |
| 03-Sep-2006 |
yamt | sync with head.
|
| 1.6.2.1 |
| 09-Sep-2006 |
rpaulo | sync with head
|
| 1.8.8.1 |
| 27-Feb-2007 |
yamt | - sync with head.
- move sched_changepri back to kern_synch.c as it doesn't know PPQ anymore.
|
| 1.8.6.1 |
| 13-Jun-2010 |
riz | Pull up following revision(s) (requested by jym in ticket #1388):
sys/arch/xen/x86/xen_bus_dma.c: revision 1.20
Although Xen's documentation states that the address_bits field is not used
by XENMEM_decrease_reservation, it is checked by the hypervisor. In certain
circumstances (stack leak), the field could have an improper value, leading
to a fail of the hypercall.
Set it to 0 ("no addressing restriction") to avoid that.
Patch tested by Sam Fourman and haad@.
This should fix the rare "failed allocating DMA memory" encountered
under NetBSD dom0. Will ask for a pull-up.
|
| 1.9.46.5 |
| 11-Aug-2010 |
yamt | sync with head.
|
| 1.9.46.4 |
| 11-Mar-2010 |
yamt | sync with head
|
| 1.9.46.3 |
| 19-Aug-2009 |
yamt | sync with head.
|
| 1.9.46.2 |
| 04-May-2009 |
yamt | sync with head.
|
| 1.9.46.1 |
| 16-May-2008 |
yamt | sync with head.
|
| 1.9.44.2 |
| 17-Jun-2008 |
yamt | sync with head.
|
| 1.9.44.1 |
| 18-May-2008 |
yamt | sync with head.
|
| 1.9.42.3 |
| 17-Jan-2009 |
mjf | Sync with HEAD.
|
| 1.9.42.2 |
| 05-Jun-2008 |
mjf | Sync with HEAD.
Also fix build.
|
| 1.9.42.1 |
| 02-Jun-2008 |
mjf | Sync with HEAD.
|
| 1.10.2.1 |
| 23-Jun-2008 |
wrstuden | Sync w/ -current. 34 merge conflicts to follow.
|
| 1.11.12.1 |
| 21-Apr-2010 |
matt | sync to netbsd-5
|
| 1.11.8.3 |
| 19-Nov-2010 |
riz | Pull up following revision(s) (requested by bouyer in ticket #1348):
sys/arch/x86/x86/bus_dma.c: revision 1.54
sys/arch/xen/x86/xen_bus_dma.c: revision 1.21
bus_dmamem_alloc() may not get a boundary smaller than size, but
it's perfectly valid for bus_dmamap_create() to do so (a contigous
transfers will then split in multiple segment).
Fix _xen_bus_dmamem_alloc_range() and _bus_dmamem_alloc_range() to
allow a boundary limit smaller than size:
- compute appropriate boundary for uvm_pglistalloc(), wich doesn't
accept boundary < size
- also take care of boundary when deciding to start a new segment.
While there, remove useless boundary argument to _xen_alloc_contig().
Fix the boundary-related issue of PR port-amd64/42980
|
| 1.11.8.2 |
| 29-Mar-2010 |
snj | Pull up following revision(s) (requested by jym in ticket #1334):
sys/arch/xen/x86/xen_bus_dma.c: revision 1.20
Although Xen's documentation states that the address_bits field is not used
by XENMEM_decrease_reservation, it is checked by the hypervisor. In certain
circumstances (stack leak), the field could have an improper value, leading
to a fail of the hypercall.
Set it to 0 ("no addressing restriction") to avoid that.
Patch tested by Sam Fourman and haad@.
This should fix the rare "failed allocating DMA memory" encountered
under NetBSD dom0.
|
| 1.11.8.1 |
| 30-Jan-2010 |
snj | Pull up following revision(s) (requested by bouyer in ticket #1271):
sys/arch/xen/x86/xen_bus_dma.c: revision 1.16
sys/arch/xen/xen/xengnt.c: revision 1.17 via patch
sys/arch/xen/xen/xennetback_xenbus.c: revision 1.33
fix address overflow with 32bit PAE.
Reported and tested by Mark Davies on port-xen@.
|
| 1.11.6.2 |
| 03-Mar-2009 |
skrll | Sync with HEAD.
|
| 1.11.6.1 |
| 19-Jan-2009 |
skrll | Sync with HEAD.
|
| 1.11.4.1 |
| 13-Dec-2008 |
haad | Update haad-dm branch to haad-dm-base2.
|
| 1.14.2.6 |
| 27-Aug-2011 |
jym | Sync with HEAD. Most notably: uvm/pmap work done by rmind@, and MP Xen
work of cherry@.
No regression observed on suspend/restore.
|
| 1.14.2.5 |
| 10-Jan-2011 |
jym | Sync with HEAD
|
| 1.14.2.4 |
| 24-Oct-2010 |
jym | Sync with HEAD
|
| 1.14.2.3 |
| 01-Nov-2009 |
jym | Sync with HEAD.
|
| 1.14.2.2 |
| 31-May-2009 |
jym | Modifications for the Xen suspend/migrate/resume branch:
- introduce xenbus_device_{suspend,resume}() functions. These are routines
used to suspend/resume MI parts of the Xenbus device interfaces, like updating
frontend/backend devices' paths found in XenStore.
- introduce HYPERVISOR_sysctl(), an hypercall used only by Xentools to obtain
information from hypervisor (listing VMs, printing console, etc.). I use it
to query xenconsole from ddb(), as a last resort in case of a panic() in
dom0 (xm being not available). Currently unused in the branch; could be, if
requested.
- disable the rwlock(9) used to protect code that could use transient MFNs.
It could trigger nasty context switches in place it should not to.
- fix some bugs in the xennet/xbd suspend/resume pmf(9) handlers.
- following XenSource's design, talk_to_otherend() is now called
watch_otherend(), and free_otherend_details() is used by Xenbus device
suspend/resume routines.
- some slight modifications in pmap regarding APDP. Introduce an inline
function (pmap_unmap_apdp_pde()) that clears APDP entry for the current pmap.
- similarly, implement pmap_unmap_all_apdp_pdes() that iterates through all
pmaps and tears down APDP, as Xen does not handle them properly.
TODO/XXX:
- pmap_unmap_apdp_pde() does not handle APDP shadow entry of PAE. It will,
once I figure out how PAE uses it.
- revisit the pmap locking issue regarding transient MFNs. As NetBSD does not
use kernel preemption and MP for Xen, this could be skipped momentarily. See
http://mail-index.netbsd.org/port-xen/2009/04/27/msg004903.html for details.
- fix a bug regarding grant tables which could technically DoS a dom0 if
ridiculously high consumer/producer indexes are passed down in the ring during
a resume.
All in all, once the grant table index issue and APDP PAE are fixed, next step
is to torture test this branch.
Tested under i386 PAE and non-PAE, Xen3 dom0 and domU. amd64 is only compile
tested.
|
| 1.14.2.1 |
| 09-Feb-2009 |
jym | Initial code for xen save/restore/migrate facilities.
- split the attach code of frontends in two half: one that is only needed
during autoconf(9) attach/detach phases, and one used at each save/restore
of device state (between suspend and resume).
Applies to hypervisor, xencons, xenbus, xbd, and xennet.
- add a rwlock(9) ("ptom_lock") to protect the different parts in the kernel
that manipulate MFNs (which could change between a suspend and a resume,
without the kernel noticing it). Parts that require MFNs acquire a reader lock,
while suspend code will acquire a writer lock to ensure that no-other parts
in kernel still use MFNs.
- integrate the suspend code with sysmon.
- various things in pmap(9), and clock.
TODO:
- factorize code a bit more inside frontends drivers.
- remove all alternative recursive (APDP_PDE) mappings found in PD/PT during
suspend, as Xen does not support them.
- abstract the ptom_lock locking, it is only required when kernel preemption
is enabled, or on MP systems.
Current code works mostly. You may experience difficulties in some corner
cases (dom0 warnings about xennet interface errors, and Xen tools failing to
validate NetBSD's alternative pmaps).
|
| 1.16.2.1 |
| 30-Apr-2010 |
uebayasi | Sync with HEAD.
|
| 1.20.2.2 |
| 05-Mar-2011 |
rmind | sync with head
|
| 1.20.2.1 |
| 30-May-2010 |
rmind | sync with head
|
| 1.22.6.2 |
| 20-Sep-2011 |
cherry | Remove the "xpq lock", since we have per-cpu mmu queues now. This may need further testing. Also add some preliminary locking around queue-ops in the network backend driver
|
| 1.22.6.1 |
| 03-Jun-2011 |
cherry | Initial import of xen MP sources, with kernel and userspace tests.
- this is a source priview.
- boots to single user.
- spurious interrupt and pmap related panics are normal
|
| 1.23.2.1 |
| 30-Oct-2012 |
yamt | sync with head
|
| 1.26.38.2 |
| 06-Sep-2018 |
pgoyette | Sync with HEAD
Resolve a couple of conflicts (result of the uimin/uimax changes)
|
| 1.26.38.1 |
| 25-Jun-2018 |
pgoyette | Sync with HEAD
|
| 1.27.2.2 |
| 13-Apr-2020 |
martin | Mostly merge changes from HEAD upto 20200411
|
| 1.27.2.1 |
| 10-Jun-2019 |
christos | Sync with HEAD
|
| 1.28.10.2 |
| 20-Apr-2020 |
bouyer | We need xenbus_bus_dma_tag for PVHVM too, but without phys->machine translation
|
| 1.28.10.1 |
| 20-Apr-2020 |
bouyer | Sync with HEAD
|
