Reported-by: Wei Liu
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
---
xen/arch/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/Kconfig b/xen/arch/x86/Kconfig
index c405c4bf4f..f64fc56739 100644
--- a/xen/arch/x86
Add dummy replacements for some functions used outside of the vpci
code, and also a guard in vmsi.c to prevent vpci arch specific helpers
from being compiled if the option is not selected.
Reported-by: Wei Liu
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
--
Allow the path to be set from a configure command line option.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
Cc: Olaf Hering
Cc: Jan Beulich
---
config/Paths.mk.in | 1 +
m4/paths.m4| 9 +
2 files changed, 10 insertions(+)
diff --git a/config/Paths.mk.in b/c
Allow the path to be set from a configure command line option.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
Cc: Olaf Hering
Cc: Jan Beulich
---
Changes since v1:
- Fix the path so it's PREFRIX/lib/... instead of PREFIX/usr/lib/...
---
config/Paths.mk.in | 1 +
m4/paths.m4
The start_info size calculated in bootlate_hvm is wrong. It should use
HVMLOADER_MODULE_MAX_COUNT instead of dom->num_modules and it doesn't
take into account the size of the modules command line.
This is not a problem so far because the actually used amount of
memory doesn't cross a page boundary
This will lead to writing a wrong module command line physical memory
address if no command line is actually provided.
This hasn't caused problems so far because hvmloader is the only
consumer of the modules command line, and it's unconditionally set
in that case.
Signed-off-by: Roger Pau Monné
lld (the llvm linker) has some issues with Xen linker script. It
doesn't understand '||' in assert expressions:
ld-melf_x86_64_fbsd -T xen.lds -N prelink.o --build-id=sha1 \
/root/src/xen/xen/common/symbols-dummy.o -o /root/src/xen/xen/.xen-syms.0
ld: error: xen.lds:260: malformed number:
Signed-off-by: Roger Pau Monné
---
ts-build-prep-freebsd | 6 ++
ts-freebsd-build | 5 -
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/ts-build-prep-freebsd b/ts-build-prep-freebsd
index 1d78a3e1..3999ed79 100755
--- a/ts-build-prep-freebsd
+++ b/ts-build-prep-freebs
And use it for the build-amd64-freebsd-again job, which should test
the new FreeBSD build produced by build-amd64-freebsd and a host
install error should be treated as a failure in order to trigger the
bisection.
Signed-off-by: Roger Pau Monné
---
make-freebsd-flight | 3 ++-
sg-run-job
FreeBSD package manager uses /usr/local/ as the default install path,
but that's not part of the compiler search path, so add it using the
APPEND_{LIB/INCLUDES} variables.
Signed-off-by: Roger Pau Monné
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Julien Grall
clang is not capable of building the x86 emulator test harness, so
disconnect it from the clang build until it can be fixed.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
---
tools/tests/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/tests/Makefile b/tool
SeaBIOS requires gcc and GNU ld in order to build, so allow setting
SEABIOSCC and SEABIOSLD by the caller when building in order to pass
the path to the compiler and linker that should be used when building
SeaBIOS.
Note that the LD32BIT-y variable was used by FreeBSD builds and is no
longer neede
ENODATA is not part of the standard set of errno values, so use
ENOENT instead. This fixes the build on FreeBSD.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
---
tools/tests/xenstore/xs-test.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
Hello,
This series contains some minor FreeBSD build fixes and improvements
required in order to add a Xen build on FreeBSD to osstest.
Thanks, Roger.
Roger Pau Monne (4):
firmware/seabios: fix build on systems with non GNU toolchains
tests: disable x86 emulator test harness when using
Signed-off-by: Roger Pau Monné
---
make-freebsd-flight | 31 ---
1 file changed, 31 deletions(-)
diff --git a/make-freebsd-flight b/make-freebsd-flight
index 66d4b816..1a2b359c 100755
--- a/make-freebsd-flight
+++ b/make-freebsd-flight
@@ -36,37 +36,6 @@ job_create_bu
The default make on FreeBSD is the BSD make, and Xen requires the GNU
make in order to build. Set the make command based on the OS for the
Xen build.
Signed-off-by: Roger Pau Monné
---
ts-xen-build | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/ts-xen-build b/ts-
://lists.xenproject.org/archives/html/xen-devel/2018-07/msg00048.html
Thanks, Roger.
Roger Pau Monne (3):
osstest: remove duplicate set_freebsd_runvars
osstest: set the make command to use for xen-build
osstest: add FreeBSD Xen build job
make-freebsd-flight | 48
To both the FreeBSD and the xen-unstable flights.
This is the runvar difference of a xen-unstable flight:
+build-amd64-freebsd all_host_os freebsd
+build-amd64-xsm-freebsd all_host_os freebsd
+build-amd64-freebsd arch amd64
+build-amd64-xsm-freebsd arch a
There's no support yet in osstest to install FreeBSD from UEFI, so for
the time being limit the FreeBSD jobs to boxes booting with legacy
BIOS.
Signed-off-by: Roger Pau Monné
---
Note that this patch depends on Ian Jackson's resource allocation
series.
---
make-freebsd-flight | 4 ++--
1 file ch
From: Ian Jackson
So that the contents of the runvar can be expanded. There are
currently two ways to do this:
- Using += will append to the end of the runvar.
- Using ,= will append to the end of the runvar using ',' as the
separator.
Note that if the runvar is empty {,|+}= just sets the
The default make on FreeBSD is the BSD make, and Xen requires the GNU
make in order to build. Set the make command based on the OS for the
Xen build.
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- Use gmake for all BSDs.
---
ts-xen-build | 11 ++-
1 file changed, 6 insertions(+)
added to the FreeBSD flight and also to the Xen
flights.
The patches can also be found at:
git://xenbits.xen.org/people/royger/osstest.git freebsd_improvement
Thanks, Roger.
Ian Jackson (1):
osstest: allow appending to existing runvars
Roger Pau Monne (5):
osstest: remove duplicate
Into a helper.
Signed-off-by: Roger Pau Monné
---
make-freebsd-flight | 24 +---
mfi-common | 14 ++
2 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/make-freebsd-flight b/make-freebsd-flight
index 1a2b359c..6c530ebe 100755
--- a/make-free
The set_freebsd_runvars helper in mfi-common is a superset of the
original function present in make-freebsd-flight, and will attempt to
fetch the last anointed FreeBSD build as a last resort option if no
FreeBSD build is signaled from the FreeBSD env vars. There's no reason
to have this duplication
To both the FreeBSD and the xen-unstable flights.
This is the runvar difference of a xen-unstable flight:
+build-amd64-xen-freebsd all_host_os freebsd
+build-amd64-xen-xsm-freebsd all_host_os freebsd
+build-amd64-xen-freebsd all_hostflagsPropEq:Firmware:bios:bios
+build-amd6
There's no support yet in osstest to install FreeBSD from UEFI, so for
the time being limit the FreeBSD jobs to boxes booting with legacy
BIOS.
The hostflags are not set for examine jobs, in order to avoid them
from only running on BIOS boxes.
Signed-off-by: Roger Pau Monné
---
Note that this pa
Avoid having error messages with the same text. No functional change.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/hvm/dom0_build.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/hvm/dom0_build.c b/xen/arch/x86/hvm/dom0
lld (the llvm linker) has some issues with Xen linker script. It
doesn't understand '||' in assert expressions:
ld-melf_x86_64_fbsd -T xen.lds -N prelink.o --build-id=sha1 \
/root/src/xen/xen/common/symbols-dummy.o -o /root/src/xen/xen/.xen-syms.0
ld: error: xen.lds:260: malformed number:
Hello,
The following 3 patches allow building the hypervisor with lld 6.0.0.
The only difference between v2 is the split into multiple patches.
Thanks, Roger.
Roger Pau Monne (3):
xen/x86: replace '||' usage in the linker script
xen/compiler: introduce a define for weak symbols
And replace the open-coded versions already in tree. No functional
change.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Daniel Kiper
---
xen/include/xen/compiler.h | 2 ++
xen/include/xen/livepatch_payload.h | 4 ++--
2 files changed, 4 insertions(+), 2 de
This allows removing the DEFINED conditional in the linker script, and
fixes compilation with lld:
ld-melf_x86_64_fbsd -T xen.lds -N prelink.o --build-id=sha1 \
/root/src/xen/xen/common/symbols-dummy.o -o /root/src/xen/xen/.xen-syms.0
ld: error: xen.lds:233: symbol not found: efi
Signed-
With '|'. The result is the same, and the later works with lld. Fixes
the following error when building Xen with lld:
ld-melf_x86_64_fbsd -T xen.lds -N prelink.o --build-id=sha1 \
/root/src/xen/xen/common/symbols-dummy.o -o /root/src/xen/xen/.xen-syms.0
ld: error: xen.lds:260: malformed n
In the x86 test harness and the fuzzer, and instead create a link in
the tools/include directory that can be used by all the tools.
No functional change.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Ian Jackson
Cc: Wei Liu
---
tools/fuzz/x86_instruction_emulator/
There's no support yet in osstest to install FreeBSD from UEFI, so for
the time being limit the FreeBSD jobs to boxes booting with legacy
BIOS.
The hostflags are not set for examine jobs, in order to avoid them
from only running on BIOS boxes.
Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
To both the FreeBSD and the xen-unstable flights.
This is the runvar difference of a xen-unstable flight:
+build-amd64-xen-freebsd all_host_os freebsd
+build-amd64-xen-xsm-freebsd all_host_os freebsd
+build-amd64-xen-freebsd all_hostflagsPropEq:Firmware:bios:bios
+build-amd6
added to the FreeBSD flight and also to the Xen
flights.
The patches can also be found at:
git://xenbits.xen.org/people/royger/osstest.git freebsd_improvement_v2
Thanks, Roger.
Ian Jackson (1):
osstest: allow appending to existing runvars
Roger Pau Monne (5):
osstest: remove duplicate
The default make on FreeBSD is the BSD make, and Xen requires the GNU
make in order to build. Set the make command based on the OS for the
Xen build.
Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
---
Changes since v1:
- Use gmake for all BSDs.
---
ts-xen-build | 11 ++-
1 file c
From: Ian Jackson
So that the contents of the runvar can be expanded. There are
currently two ways to do this:
- Using += will append to the end of the runvar.
- Using ,= will append to the end of the runvar using ',' as the
separator.
Note that if the runvar is empty {,|+}= just sets the
The set_freebsd_runvars helper in mfi-common is a superset of the
original function present in make-freebsd-flight, and will attempt to
fetch the last anointed FreeBSD build as a last resort option if no
FreeBSD build is signaled from the FreeBSD env vars. There's no reason
to have this duplication
Into a helper. A diff of the runvars of flights generated with and
without the patch show no differences.
No functional change.
Signed-off-by: Roger Pau Monné
---
make-freebsd-flight | 24 +---
mfi-common | 14 ++
2 files changed, 19 insertions(+), 19 de
In the x86 test harness and the fuzzer, and instead create a link in
the tools/include directory that can be used by all the tools.
No functional change.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Ian Jackson
Cc: Wei Liu
---
Changes since v1:
- Don't remove the
So that it can be used by other components apart from the efi specific
code.
This is required so that the conditional used to define the efi symbol
in the linker script can be removed and instead the definition of the
efi symbol can be guarded using the preprocessor.
The motivation behind this ch
multiboot2 capable ELF binary linker PE support was also
required.
Thanks, Roger.
Roger Pau Monne (2):
x86/efi: move the logic to detect PE build support
x86/efi: split compiler vs linker support
.gitignore| 1 -
xen/arch/x86/Makefile | 12 ++--
xen/arch/x86/efi
So that an ELF binary with support for EFI services will be built when
the compiler supports the MS ABI, regardless of the linker support for
PE.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Daniel Kiper
---
Changes since v1:
- New in this version.
---
xen/arch/x8
So that it can be used by other components apart from the efi specific
code. By moving the detection code creating a dummy efi/disabled file
can be avoided.
This is required so that the conditional used to define the efi symbol
in the linker script can be removed and instead the definition of the
Tear down functions are not mandatory. Note that this patch just
implements the framework, but doesn't implement any tear down function
yet.
The list of vpci init and teardown functions is also moved outside of
the init section. This is in preparation for SR-IOV support, which
requires the ability
To be queued in vpci_vcpu. This will be required for SR-IOV support,
which uses a single control register bit to toggle memory decoding for
all the virtual functions.
No functional change expected.
Signed-off-by: Roger Pau Monné
Reviewed-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc:
This is required in order to allow run-time removal of MSI-X regions.
No functional change.
Signed-off-by: Roger Pau Monné
Reviewed-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Julien Grall
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Ti
This allows waiting a specified number of cycles on the vcpu. Once the
wait has finished a callback is executed.
Note that this is still not used, but introduced here in order to
simplify the complexity of the patches that actually make use of it.
Signed-off-by: Roger Pau Monné
---
Cc: Andrew Co
preparatory changes in order to support SR-IOV.
Patch 11 actually adds support for the capability.
The series can also be found at:
git://xenbits.xen.org/people/royger/xen.git sriov.v2
The series has been tested with a Linux PVH Dom0 and an Intel I350 nic.
Thanks, Roger.
Roger Pau Monne (11):
vpci
To the outside of the vpci struct. This way the lock can be used to
check whether vpci is present, and removal can be performed while
holding the lock, in order to make sure there are no accesses to the
contents of the vpci struct. Previously removal could race with
vpci_read for example, since the
So that interrupts are properly freed.
Signed-off-by: Roger Pau Monné
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Julien Grall
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
---
Changes since v1:
- Free the msi struct in the t
This new helper will merge two rangesets.
Signed-off-by: Roger Pau Monné
Acked-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Julien Grall
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
---
xen/common/rangeset.c
So that interrupts are properly freed.
Signed-off-by: Roger Pau Monné
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Julien Grall
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
---
Changes since v1:
- Shuffle order of the teardow
In order to unmap the BARs
Signed-off-by: Roger Pau Monné
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Julien Grall
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
---
Changes since v1:
- Add comment regarding the fact that memo
So that a PCI device that supports SR-IOV (PF) can enable the capability
and use the virtual functions.
This code is expected to only be used by privileged domains,
unprivileged domains should not get access to the SR-IOV capability.
The current code detects enabling of the virtual functions feat
So that pci_{add/remove}_device work correctly with vpci. Note that
this requires moving vpci_add_handlers out of the init section.
Signed-off-by: Roger Pau Monné
Reviewed-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Julien Grall
Cc: Konrad Rzeszut
In order to test HPET level trigger interrupts.
Note that the test doesn't check that the interrupt is injected
correctly, only that the status bits are properly set an acknowledged
when using HPET with level triggered interrupts.
Signed-off-by: Roger Pau Monné
---
Cc: Andrew Cooper
---
arch/x
Level trigger interrupts will be asserted regardless of whether the
interrupt is masked, and thus the callback will also be executed.
Add a new 'level' parameter to create_periodic_time in order to create
level triggered timers. None of the current users of vpt are switched
to use level triggered
(mainly the level
triggered interrupts) to xtf.
The Xen series can be found at:
git://xenbits.xen.org/people/royger/xen.git vhpet.v4
Thanks, Roger.
Roger Pau Monne (2):
vpt: add support for level interrupts
vhpet: add support for level triggered interrupts
xen/arch/x86/hvm/hpet.c | 54
Level triggered interrupts are not an optional feature of HPET, and
must be implemented in order to comply with the HPET specification.
Implement them by adding a callback to the timer which sets the
interrupt bit in the general interrupt status register. Further
interrupts (in case of periodic mo
This is currently a non-functional change, since no new jobs are
added, and the existing ones should stay unchanged. Runvars of a
xen-unstable flight are exactly the same.
The purpose of the helper is to allow adding different Xen build jobs,
with likely different runvars in the future.
Signed-of
Into a helper. A diff of the runvars of flights generated with and
without the patch show no differences.
No functional change.
Signed-off-by: Roger Pau Monné
---
make-freebsd-flight | 24 +---
mfi-common | 14 ++
2 files changed, 19 insertions(+), 19 de
From: Ian Jackson
In particular
OSSTEST_CONFIG=standalone-config-example eatmydata bash -x
./standalone-generate-dump-flight-runvars
should not require ~/osstest-repos to exist.
Signed-off-by: Ian Jackson
---
cri-getconfig | 2 +-
cri-lock-repos | 4 +++-
2 files changed, 4 insertions(+),
print { }
osstest: allow appending to existing runvars
Roger Pau Monne (6):
osstest: remove duplicate set_freebsd_runvars
osstest: abstract code to create a FreeBSD build job
osstest: limit FreeBSD jobs to hardware booting in BIOS mode
osstest: set the make command to use for xen-build
The default make on FreeBSD is the BSD make, and Xen requires the GNU
make in order to build. Set the make command based on the OS for the
Xen build.
Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
---
Changes since v1:
- Use gmake for all BSDs.
---
ts-xen-build | 11 ++-
1 file c
There's no support yet in osstest to install FreeBSD from UEFI, so for
the time being limit the FreeBSD jobs to boxes booting with legacy
BIOS.
The hostflags are not set for examine jobs, in order to avoid them
from only running on BIOS boxes.
The runvar difference with this patch applied is:
+f
From: Ian Jackson
So that the contents of the runvar can be expanded. There are
currently two ways to do this:
- Using += will append to the end of the runvar.
- Using ,= will append to the end of the runvar using ',' as the
separator.
Note that if the runvar is empty {,|+}= just sets the
The set_freebsd_runvars helper in mfi-common is a superset of the
original function present in make-freebsd-flight, and will attempt to
fetch the last anointed FreeBSD build as a last resort option if no
FreeBSD build is signaled from the FreeBSD env vars. There's no reason
to have this duplication
From: Ian Jackson
With newer bash, this causes
local envvar="FREEBSD_${arch^^}_BUILDJOB"
if [ -n "${!envvar}" ]; then
to (properly) report a syntax error.
As Roger says, it is better to print a dummy host for each
architecture, so do that.
Reported-by: Roger Pau Monné
Signed-off-by
To both the FreeBSD and the xen-unstable flights.
This is the runvar difference of all flights:
+freebsd-master build-amd64-xen-freebsd all_host_osfreebsd
+freebsd-master build-amd64-xen-freebsd all_hostflags
PropEq:Firmware:bios:bios
+freebsd-master build-amd64-xen-freebsd
multiboot2 capable ELF binary linker PE support was also
required.
The series can be found at:
git://xenbits.xen.org/people/royger/xen.git efi.v3
Thanks, Roger.
Roger Pau Monne (2):
x86/efi: move the logic to detect PE build support
x86/efi: split compiler vs linker support
.gitignore
So that an ELF binary with support for EFI services will be built when
the compiler supports the MS ABI, regardless of the linker support for
PE.
Signed-off-by: Roger Pau Monné
Reviewed-by: Jan Beulich
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Daniel Kiper
---
Changes since v1:
- New in this
So that it can be used by other components apart from the efi specific
code. By moving the detection code creating a dummy efi/disabled file
can be avoided.
This is required so that the conditional used to define the efi symbol
in the linker script can be removed and instead the definition of the
Remove local definition of MIN and instead include the kernel.h header
for the hypervisor build. Fixes the following error on the tools build:
In file included from xc_dom_decompress_unsafe_lzma.c:8:0:
../../xen/common/unlzma.c:33:0: error: "MIN" redefined [-Werror]
#define MIN(a, b) (((a) < (b))
The regexp used with find in order to list the man pages doesn't work
with FreeBSD find, so use a wildcard instead. No functional change.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
---
docs/Makefile | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a
The iommu initialization will also create MMIO mappings in the Dom0
p2m, so the paging memory pool needs to be allocated or else iommu
initialization will fail.
Move the call to init the iommu after the Dom0 p2m has been setup in
order to solve this.
Note that issues caused by this wrong ordering
Several people have reported hardware issues (malfunctioning USB
controllers) due to iommu page faults. Those faults are caused by
missing RMRR (VTd) or IRVS (AMD-Vi) entries in the ACPI tables. Those
can be worked around on VTd hardware by manually adding RMRR entries
on the command line, this is
In order to place all the map conditions in a single if ... else
conditional.
No functional change.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
---
xen/drivers/passthrough/x86/iommu.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/xen/drive
Introduce a new iommu=inclusive generic option that supersedes
iommu_inclusive_mapping. This should be a non-functional change on
Intel hardware, while AMD hardware will gain the same functionality of
mapping almost everything below the 4GB boundary.
Note that is a noop for ARM hardware.
Signed-o
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
---
xen/drivers/passthrough/iommu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/drivers/passthrough/iommu.c b/xen/drivers/passthrough/iommu.c
index 2c44fabf99..70d218f910 100644
--- a/xen/drivers/passthrough/iommu.c
+
emory map.
The series can be found at:
git://xenbits.xen.org/people/royger/xen.git iommu_inclusive_v1
Thanks, Roger.
Roger Pau Monne (4):
iommu: remove unneeded return from iommu_hwdom_init
iommu: generalize iommu_inclusive_mapping
x86/iommu: reorder conditions used in the inclusive iommu map
To select the iommu configuration used by Dom0. This option supersedes
iommu=dom0-strict|dom0-passthrough.
No functional change.
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- New in this version.
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Julien Gra
Remove the handling for different page sizes now that ia64 is gone.
No functional change.
Reported by: Jan Beulich
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- New in this version.
---
Cc: Kevin Tian
---
xen/drivers/passthrough/vtd/x86/vtd.c | 17 -
1 file changed,
Several people have reported hardware issues (malfunctioning USB
controllers) due to iommu page faults on Intel hardware. Those faults
are caused by missing RMRR (VTd) entries in the ACPI tables. Those can
be worked around on VTd hardware by manually adding RMRR entries on
the command line, this is
dware. It's
also available to AMD hardware, although it's disabled by default in
that case.
The series can be found at:
git://xenbits.xen.org/people/royger/xen.git iommu_inclusive_v2
Thanks, Roger.
Roger Pau Monne (5):
iommu/vtd: cleanup vtd_set_hwdom_mapping after ia64 removal
i
So it's done before the iommu is initialized. This is required in
order to be able to fetch the MMCFG regions from the domain struct.
No functional change.
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- New in this version.
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/hvm/d
Introduce a new dom0-iommu=inclusive generic option that supersedes
iommu_inclusive_mapping. The prevcious behaviour is preserved and the
option should only be enabled by default on Intel hardware.
No functional change intended.
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- Use dom0-io
The path to the python binary can be different from /usr/bin/python
depending on the distro/OS.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
Cc: Christian Lindig
Cc: David Scott
---
tools/include/xen-foreign/mkchecker.py | 2 +-
tools/include/xen-foreign/mkheader.py|
Several people have reported hardware issues (malfunctioning USB
controllers) due to iommu page faults on Intel hardware. Those faults
are caused by missing RMRR (VTd) entries in the ACPI tables. Those can
be worked around on VTd hardware by manually adding RMRR entries on
the command line, this is
dware. It's
also available to AMD hardware, although it's disabled by default in
that case.
The series can be found at:
git://xenbits.xen.org/people/royger/xen.git iommu_inclusive_v3
Thanks, Roger.
Roger Pau Monne (4):
iommu: introduce dom0-iommu option
iommu: make iommu_incl
Introduce a new dom0-iommu=inclusive generic option that supersedes
iommu_inclusive_mapping. The previous behaviour is preserved and the
option should only be enabled by default on Intel hardware.
No functional change intended.
Signed-off-by: Roger Pau Monné
---
Changes since v2:
- Fix typo in
To select the iommu configuration used by Dom0. This option supersedes
iommu=dom0-strict|dom0-passthrough.
No functional change.
Signed-off-by: Roger Pau Monné
Reviewed-by: Paul Durrant
---
Changes since v2:
- Change the style and text used in the xen command line document.
- Don't allow none
So it's done before the iommu is initialized. This is required in
order to be able to fetch the MMCFG regions from the domain struct.
No functional change.
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- New in this version.
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/hvm/d
To select the iommu configuration used by Dom0. This option supersedes
iommu=dom0-strict|dom0-passthrough.
No functional change.
Signed-off-by: Roger Pau Monné
Reviewed-by: Paul Durrant
---
Changes since v2:
- Change the style and text used in the xen command line document.
- Don't allow none
So it's done before the iommu is initialized. This is required in
order to be able to fetch the MMCFG regions from the domain struct.
No functional change.
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- New in this version.
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/hvm/d
Introduce a new dom0-iommu=inclusive generic option that supersedes
iommu_inclusive_mapping. The previous behaviour is preserved and the
option should only be enabled by default on Intel hardware.
No functional change intended.
Signed-off-by: Roger Pau Monné
Reviewed-by: Paul Durrant
---
Change
dware. It's
also available to AMD hardware, although it's disabled by default in
that case.
The series can be found at:
git://xenbits.xen.org/people/royger/xen.git iommu_inclusive_v4
Thanks.
Roger Pau Monne (4):
iommu: introduce dom0-iommu option
iommu: make iommu_inclusive_mapping
Several people have reported hardware issues (malfunctioning USB
controllers) due to iommu page faults on Intel hardware. Those faults
are caused by missing RMRR (VTd) entries in the ACPI tables. Those can
be worked around on VTd hardware by manually adding RMRR entries on
the command line, this is
The current balloon code tries to calculate a delta factor for the
balloon target when running in HVM mode in order to account for memory
used by the firmware.
This workaround for memory accounting doesn't work properly on a PVH
Dom0, that has a static-max value different from the target value eve
401 - 500 of 2554 matches
Mail list logo
