Home
last modified time | relevance | path

Searched hist:"6699 c22c1cb0f8a355ecb9d030c6990e48f8d7db" (Results 1 – 3 of 3) sorted by relevance

/freebsd/sys/dev/xen/bus/
H A Dintr-internal.hdiff 6699c22c1cb0f8a355ecb9d030c6990e48f8d7db Fri May 14 06:36:02 CEST 2021 Elliott Mitchell <ehem+freebsd@m5p.com> xen/intr: move interrupt allocation/release to architecture

Simply moving the interrupt allocation and release functions into files
which belong to the architecture. Since x86 interrupt handling is quite
distinct from other architectures, this is a crucial necessary step.

Identifying the border between x86 and architecture-independent is
actually quite tricky. Similarly, getting the prototypes for the
border right is also quite tricky.

Inspired by the work of Julien Grall <julien@xen.org>,
2015-10-20 09:14:56, but heavily adjusted.

Reviewed by: royger
Differential Revision: https://reviews.freebsd.org/D30936
/freebsd/sys/x86/include/xen/
H A Darch-intr.hdiff 6699c22c1cb0f8a355ecb9d030c6990e48f8d7db Fri May 14 06:36:02 CEST 2021 Elliott Mitchell <ehem+freebsd@m5p.com> xen/intr: move interrupt allocation/release to architecture

Simply moving the interrupt allocation and release functions into files
which belong to the architecture. Since x86 interrupt handling is quite
distinct from other architectures, this is a crucial necessary step.

Identifying the border between x86 and architecture-independent is
actually quite tricky. Similarly, getting the prototypes for the
border right is also quite tricky.

Inspired by the work of Julien Grall <julien@xen.org>,
2015-10-20 09:14:56, but heavily adjusted.

Reviewed by: royger
Differential Revision: https://reviews.freebsd.org/D30936
/freebsd/sys/x86/xen/
H A Dxen_arch_intr.cdiff 6699c22c1cb0f8a355ecb9d030c6990e48f8d7db Fri May 14 06:36:02 CEST 2021 Elliott Mitchell <ehem+freebsd@m5p.com> xen/intr: move interrupt allocation/release to architecture

Simply moving the interrupt allocation and release functions into files
which belong to the architecture. Since x86 interrupt handling is quite
distinct from other architectures, this is a crucial necessary step.

Identifying the border between x86 and architecture-independent is
actually quite tricky. Similarly, getting the prototypes for the
border right is also quite tricky.

Inspired by the work of Julien Grall <julien@xen.org>,
2015-10-20 09:14:56, but heavily adjusted.

Reviewed by: royger
Differential Revision: https://reviews.freebsd.org/D30936