This run is configured for baseline tests only.
flight 75359 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75359/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm
Hi,
We want to passthrough the display to the guest OS.We are using Xen-4.8 and
Hikey960. Is it possible to do pass through of display?If yes please
provide reference.
--
This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the
flight 128407 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128407/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR.
vs. 125898
flight 128433 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128433/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf d20ae95a13e851d56c6618108b18c93526505ca2
baseline version:
ovmf
> -Daniel De Graaf wrote: -
> To: xen-devel@lists.xenproject.org, Nicolas Poirot
> From: Daniel De Graaf
> Date: 05/10/2018 18:33
> Cc: George Dunlap , Jan Beulich ,
> Daniel De Graaf
> Subject: [PATCH v2] flask: sort io{port,mem}con entries
>
> These entries are not always sorted by
> -Daniel De Graaf wrote: -
> To: xen-devel@lists.xenproject.org, Nicolas Poirot
> From: Daniel De Graaf
> Date: 10/05/2018 06:33PM
> Cc: George Dunlap , Jan Beulich ,
> Daniel De Graaf
> Subject: [PATCH v2] flask: sort io{port,mem}con entries
>
> These entries are not always sorted
On 11/09/2018 17:48, Amit Singh Tomar wrote:
> diff --git a/xen/arch/arm/arm64/head.S b/xen/arch/arm/arm64/head.S
> index d63734f..ef87b5c 100644
> --- a/xen/arch/arm/arm64/head.S
> +++ b/xen/arch/arm/arm64/head.S
> @@ -120,8 +127,8 @@ efi_head:
> add x13, x18, #0x16
> b
flight 128402 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128402/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 128367
Tests which did not
Today Ctrl-AAA is used to switch between Xen and Dom0. Extend the
mechanism to allow for switching between Xen, Dom0, and any of the
initial DomU created from Xen alongside Dom0 out of information provided
via device tree.
Rename xen_rx to console_rx to match the new behavior.
Clarify existing
domain_build.c is too large.
Move all the ACPI specific device tree generating functions from
domain_build.c to acpi/domain_build.c.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
- rename acpi_dt_build to domain_build.c
- add copyright header
- remove useless #include
- remove
Introduce functions to generate a basic domU device tree, similar to the
existing functions in tools/libxl/libxl_arm.c.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
- code style
- two separate functions for gicv2 and gicv3
- remove useless local variables
- fix typos
- do not use host
Similar to construct_dom0, construct_domU creates a barebone DomU guest.
The device tree node passed as argument is compatible "xen,domain", see
docs/misc/arm/device-tree/booting.txt.
Add const to kernel_probe dt_device_node parameter.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
-
Extend the existing device tree based multiboot protocol to include
information regarding multiple domains to boot.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
- memory is 64bit
Changes in v3:
- remove "xen,initial-domain" for now
- make vpl011 an empty property
- memory in KBs
Move generic initializations out of construct_dom0 so that they can be
reused.
Rename prepare_dtb to prepare_dtb_hwdom to avoid confusion.
No functional changes in this patch.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
- newline and style changes
Changes in v3:
- move setting type
also rename it to set_interrupt.
Signed-off-by: Stefano Stabellini
---
xen/arch/arm/domain_build.c | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index bf8aeca..760ebf8 100644
---
It will be #included by a file in a xen/arch/arm subdirectory.
Signed-off-by: Stefano Stabellini
---
xen/arch/arm/domain_build.c | 2 +-
xen/arch/arm/kernel.c| 3 +-
xen/arch/arm/kernel.h| 86
xen/include/asm-arm/kernel.h | 86
Add a new document to provide information on how to use dom0less related
features and their current limitations.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
- rename to .txt
- improve wording
Changes in v3:
- add patch
---
docs/misc/arm/dom0less.txt | 47
Introduce a union in struct vpl011 to contain the console ring members.
A later patch will add another member of the union for the case where
the backend is in Xen.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
- name union "backend"
Changes in v3:
- rename ring field to dom
Changes in
allocate_memory only deals with directly mapped memory. Rename it to
allocate_memory_11.
Signed-off-by: Stefano Stabellini
---
Changes in v3:
- add patch
---
xen/arch/arm/domain_build.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/xen/arch/arm/domain_build.c
Don't add duplicate boot modules (same kind and same start address),
they are freed later, we don't want to introduce double-free errors.
Introduce a domU flag in struct bootmodule and struct bootcmdline. Set
it for kernels and ramdisks of "xen,domain" nodes to avoid getting
confused in
Introduce a new array to store the cmdline of each boot module. It is
separate from struct bootmodules. Remove the cmdline field from struct
boot_module. This way, kernels and initrds with the same address in
memory can share struct bootmodule (important because we want them to be
free'd only
Find addresses, sizes on device tree from kernel_probe.
Find the cmdline from the bootcmdlines array.
Introduce a new boot_module_find_by_addr_and_kind function to match not
just on boot module kind, but also by address so that we can support
multiple domains.
Introduce a
Xen boot modules need to account not just for Dom0 but also for a few
potential DomUs, each of them coming with their own kernel and initrd.
Increase MAX_MODULES to 32 to allow for more DomUs.
Signed-off-by: Stefano Stabellini
Reviewed-by: Doug Goldstein
---
xen/include/asm-arm/setup.h | 2 +-
Make vpl011 being able to be used without a userspace component in Dom0.
In that case, output is printed to the Xen serial and input is received
from the Xen serial one character at a time.
Call domain_vpl011_init during construct_domU if vpl011 is enabled.
Introduce a new ring struct with only
Move the code to calculate in_fifo_level and out_fifo_level out of
vpl011_data_avail, to the caller.
This change will make it possible to reuse vpl011_data_avail with
different ring structures in a later patch.
Signed-off-by: Stefano Stabellini
Acked-by: Julien Grall
---
Changes in v3:
-
Introduce an allocate_memory function able to allocate memory for DomUs
and map it at the right guest addresses, according to the guest memory
map: GUEST_RAM0_BASE and GUEST_RAM1_BASE.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
- move earlier, add #if 0
- introduce
To avoid mixing the output of different domains on the console, buffer
the output chars and print line by line. Unless the domain has input
from the serial, in which case we want to print char by char for a
smooth user experience.
The size of SBSA_UART_OUT_BUF_SIZE is arbitrary, choose the same
Call a new function, "create_domUs", from setup_xen to start DomU VMs.
Introduce support for the "xen,domU" compatible node on device tree.
Create new DomU VMs based on the information found on device tree under
"xen,domU". Calls construct_domU for each domain.
Introduce a simple global variable
Introduce vpl011 support to guests started from Xen: it provides a
simple way to print output from a guest, as most guests come with a
pl011 driver. It is also able to provide a working console with
interrupt support.
The UART exposed to the guest is a SBSA compatible UART and not a PL011.
SBSA
No functional changes.
Signed-off-by: Stefano Stabellini
---
Changes in v3:
- no change in print messages
- do not remove BUG_ON
Changes in v2:
- new patch
---
xen/arch/arm/domain_build.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git
Introduce an is_console option to allow certain classes of domUs to use
the Xen console. Specifically, it will be used to give console access to
all domUs started from Xen from information on device tree.
Signed-off-by: Stefano Stabellini
Acked-by: Daniel De Graaf
CC: andrew.coop...@citrix.com
Hi all,
This is first step toward "dom0less" as discussed in the various
certifications related threads and discussions.
The goal of this series is to enable Xen to boot multiple domains in
parallel, in addition to dom0, out of information found on device tree.
The device tree based boot
On Fri, 5 Oct 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 10/04/2018 10:52 PM, Stefano Stabellini wrote:
> > On Wed, 1 Aug 2018, Jan Beulich wrote:
> > > > > > On 01.08.18 at 01:28, wrote:
> > > > Today Ctrl-AAA is used to switch between Xen and Dom0. Extend the
> > > > mechanism to allow for
On Fri, 5 Oct 2018, Julien Grall wrote:
> On 10/05/2018 10:25 AM, Julien Grall wrote:
> > On 10/04/2018 10:52 PM, Stefano Stabellini wrote:
> > > On Wed, 1 Aug 2018, Jan Beulich wrote:
> > > > > > > On 01.08.18 at 01:28, wrote:
> > > > > Today Ctrl-AAA is used to switch between Xen and Dom0.
flight 128426 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128426/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
Adding the implementation language as a suffix to a program name is
poor practice.
Signed-off-by: Ian Jackson
---
tools/xenmon/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/xenmon/Makefile b/tools/xenmon/Makefile
index e45c5b8c14..e1712304d0 100644
---
This command does the link, so it needs LDFLAGS.
Signed-off-by: Ian Jackson
---
tools/debugger/gdbsx/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/debugger/gdbsx/Makefile b/tools/debugger/gdbsx/Makefile
index 723a2743cc..8d7cd94a31 100644
---
From: Bastian Blank
libxenstat does not have a stable ABI. Set its version to the current
Xen release version.
Signed-off-by: Ian Jackson
---
tools/xenstat/libxenstat/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/xenstat/libxenstat/Makefile
`kdd' is an unfortunate namespace landgrab.
Signed-off-by: Ian Jackson
---
tools/debugger/kdd/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/debugger/kdd/Makefile b/tools/debugger/kdd/Makefile
index 5509eee68c..26116949d4 100644
---
This seems to have been simply omitted. Obviously this is needed when
building and not just when installing. Passing only when installing
is ineffective.
Signed-off-by: Ian Jackson
---
tools/pygrub/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Firstly, add a reference to the documentation for the kconfig system.
Secondly, warn the user about the XEN_CONFIG_EXPERT problem.
CC: Doug Goldstein
CC: Wei Liu
CC: Jan Beulich
CC: Andrew Cooper
Signed-off-by: Ian Jackson
---
INSTALL | 20
1 file changed, 20
Do not reset LDFLAGS to empty. Instead, append the fsimage-special
LDFLAGS.
Signed-off-by: Ian Jackson
---
tools/libfsimage/common/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/libfsimage/common/Makefile b/tools/libfsimage/common/Makefile
index
No functional change.
Signed-off-by: Ian Jackson
---
docs/man/xen-pv-channel.pod.7 | 1 -
1 file changed, 1 deletion(-)
diff --git a/docs/man/xen-pv-channel.pod.7 b/docs/man/xen-pv-channel.pod.7
index f9f0108488..07898f6dde 100644
--- a/docs/man/xen-pv-channel.pod.7
+++
A manpage `foo.7.pod' must start with
=head NAME
foo - some summary of what foo is or what this manpage is
because otherwise manpage catalogue systems cannot generate a proper
`whatis' entry.
Signed-off-by: Ian Jackson
---
docs/man/xen-pci-device-reservations.pod.7 | 4
Signed-off-by: Ian Jackson
---
tools/misc/xenlockprof.c | 2 +-
tools/misc/xenperf.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/misc/xenlockprof.c b/tools/misc/xenlockprof.c
index df23c82912..11f43a35e3 100644
--- a/tools/misc/xenlockprof.c
+++
Signed-off-by: Ian Jackson
---
docs/man/xenstore.pod.1 | 2 +-
docs/man/xl.pod.1.in| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/man/xenstore.pod.1 b/docs/man/xenstore.pod.1
index 74172891e2..dd8f80647d 100644
--- a/docs/man/xenstore.pod.1
+++
This allows the caller to provide some LDFLAGS to the Xen build
system.
Signed-off-by: Ian Jackson
---
tools/Rules.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/Rules.mk b/tools/Rules.mk
index 296b722372..68f2ed7ce1 100644
--- a/tools/Rules.mk
+++ b/tools/Rules.mk
@@ -9,6 +9,8
Signed-off-by: Ian Jackson
---
tools/libxl/libxl_internal.h | 2 +-
tools/python/xen/lowlevel/xc/xc.c | 2 +-
tools/xenstat/libxenstat/src/xenstat_qmp.c | 2 +-
xen/common/sched_rt.c | 2 +-
xen/drivers/acpi/apei/erst.c | 2 +-
Signed-off-by: Ian Jackson
---
tools/hotplug/Linux/block-drbd-probe | 2 +-
tools/libxc/xc_dom_elfloader.c | 2 +-
tools/libxl/libxl_dm.c | 2 +-
tools/libxl/libxl_event.h| 2 +-
tools/libxl/libxl_qmp.c | 2 +-
xen/include/xen/libfdt/libfdt.h | 2
Signed-off-by: Ian Jackson
---
tools/xl/xl_flask.c| 2 +-
xen/arch/arm/arm64/lib/memcmp.S| 2 +-
xen/arch/x86/hvm/hvm.c | 2 +-
xen/arch/x86/hvm/svm/intr.c| 2 +-
xen/drivers/passthrough/arm/smmu.c | 2 +-
xen/include/efi/efiprot.h | 2 +-
Signed-off-by: Ian Jackson
---
tools/python/xen/lowlevel/xc/xc.c | 2 +-
xen/drivers/passthrough/vtd/iommu.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/python/xen/lowlevel/xc/xc.c
b/tools/python/xen/lowlevel/xc/xc.c
index ebef92cd50..484b790c75 100644
---
Signed-off-by: Ian Jackson
---
tools/xentrace/xenalyze.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c
index 5ed0a12327..aa894673ad 100644
--- a/tools/xentrace/xenalyze.c
+++ b/tools/xentrace/xenalyze.c
@@
Bastian Blank (1):
tools/xenstat: Fix shared library version
Ian Jackson (17):
docs/man: Fix two typos detected by the Debian lintian tool
tools/xentrace/xenalyze: Fix typos detected by lintian
Various: Fix typos `unkown', `retreive' (detected by lintian)
Various: Fix typo `occured'
Signed-off-by: Ian Jackson
---
tools/python/xen/lowlevel/xc/xc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/python/xen/lowlevel/xc/xc.c
b/tools/python/xen/lowlevel/xc/xc.c
index b137d5a839..6f5b8a6fa8 100644
--- a/tools/python/xen/lowlevel/xc/xc.c
+++
When using shadow paging, EFER.NX is a Xen controlled bit, and is required by
the shadow pagefault handler to distinguish instruction fetches from data
accesses.
This can be observed by a guest which has NX and SMEP clear but SMAP active by
attempting to execute code on a user mapping. The first
When dm_restrict is enabled, ask QEMU to chroot into an empty directory.
* Create /var/run/qemu/root-domid (deleting the old one if it's there)
* Pass the -chroot option to QEMU
Rather than running `rm -rf` on the directory before creating it
(since there is no library function to do this),
Add a tool to check whether the various process-level deprivileging
operations have actually taken place on the process.
The tool takes a domname or domid, and returns success or failure.
Signed-off-by: George Dunlap
---
Changes since v2:
- Make grep for Uid line more strict
- Fix Gid grep,
QEMU running under Xen doesn't need mount or IPC functionality.
Create and enter separate namespaces for each of these before
executing QEMU, so that in the event that other restrictions fail, the
process won't be able to even name system mount points or exsting
non-file-based IPC descriptors to
Limit the ability of a potentially compromised QEMU to consume system
resources. Key limits:
- RLIMIT_FSIZE (file size): 256KiB
- RLIMIT_NPROC (after uid changes to a unique uid)
Probably unnecessary limits but why not:
- RLIMIT_CORE: 0
- RLIMIT_MSGQUEUE: 0
- RLIMIT_LOCKS: 0
-
docs/qemu-deprivilege.txt had some basic instructions for using
dm_restrict, but it was incomplete, misleading, and stale.
Update the docs in a number of ways.
First, separate user-facing documentation and technical description
into docs/features and docs/design, respectively.
In the feature
These entries are not always sorted by checkpolicy, so sort them during
policy load (as is already done for later ocontext additions).
Reported-by: Nicolas Poirot
Signed-off-by: Daniel De Graaf
---
xen/xsm/flask/ss/policydb.c | 35 +--
1 file changed, 29
> -Original Message-
> From: Wei Liu [mailto:wei.l...@citrix.com]
> Sent: 05 October 2018 17:04
> To: Paul Durrant
> Cc: xen-devel@lists.xenproject.org; Stefano Stabellini
> ; Jun Nakajima ; George
> Dunlap ; Andrew Cooper
> ; Jan Beulich ; Wei Liu
>
> Subject: Re: [Xen-devel] [PATCH v14
This patch has broken my PVH Dom0 setup.
[2.515159] igb :02:00.1: added PHC on eth1
[2.519539] igb :02:00.1: Intel(R) Gigabit Ethernet Network Connection
[2.526469] igb :02:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 0c:c4:7a:e7:b6:53
[2.533733] igb :02:00.1: eth1: PBA No:
flight 128422 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128422/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 05 October 2018 15:51
> To: Paul Durrant
> Cc: Brian Woods ; Suravee Suthikulpanit
> ; Julien Grall ;
> Andrew Cooper ; Wei Liu ;
> George Dunlap ; Ian Jackson
> ; Jun Nakajima ; Kevin
> Tian ; Stefano Stabellini
[resending]
On Fri, Oct 5, 2018 at 4:17 PM George Dunlap wrote:
>
> On Mon, Sep 24, 2018 at 9:35 AM Paul Durrant wrote:
> > > +{
> > > +.resource = -1
> >
> > Is -1 guaranteed not to clash with any defined resource type?
>
> Hmm... well at the moment /usr/include/bits/resource.h
>>> On 05.10.18 at 16:49, wrote:
> On 05/10/18 14:43, Jan Beulich wrote:
> On 05.10.18 at 14:39, wrote:
>>> On 03/10/18 19:38, Andrew Cooper wrote:
Makefile:136: recipe for target '/local/xen.git/xen/xen' failed
make[1]: *** [/local/xen.git/xen/xen] Error 2
Makefile:45: recipe
On the ARM side, lift the code to select the appropriate GIC version when
NATIVE is requested.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Wei Liu
CC: Stefano Stabellini
CC: Julien Grall
---
xen/arch/arm/domain.c | 44
Call it from the head of domain_create() (before doing any memory
allocations), which will apply the checks to dom0 as well as domU's.
For now, just subsume the XEN_DOMCTL_CDF_* check from XEN_DOMCTL_createdomain.
This means that the corner case of the toolstack providing bad configuration
will
The purpose of this is to move the auduting to be earlier than
arch_domain_create().
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Wei Liu
CC: Stefano Stabellini
CC: Julien Grall
The max_vcpus setting for GIC_V3 is somewhat confusing. The current GIC_V3
driver claims to support 4096
This reverts commit 703d9d5ec13a0f487e7415174ba54e0e3ca158db. The domain
creation logic has been adjusted to set up d->max_vcpus early enough to be
usable in vgic_v3_domain_init().
Signed-off-by: Andrew Cooper
---
CC: Stefano Stabellini
CC: Julien Grall
---
xen/arch/arm/vgic-v3.c | 29
With config->max_vcpus now being audited by the check_domain_config() path, we
can alloate d->vcpu[] before calling arch_domain_create().
Doing do allows for the removal of domain_max_vcpus(), which on the ARM side
removes vgic_max_vcpus() and the .max_vcpus field from vgic_ops.
Signed-off-by:
To fix an order-of-construction issue with gic-v3 on ARM, arrange for
d->max_vcpus to be auditied and set up prior to arch_domain_create()
This is RFC because all of the interesting changes are in ARM, and therefore
only compile tested by me at this point.
This can be found in git tree from
On 05/10/18 14:43, Jan Beulich wrote:
On 05.10.18 at 14:39, wrote:
>> On 03/10/18 19:38, Andrew Cooper wrote:
>>> Finally, this series doesn't link with the default Debian toolchain.
>>>
>>> andrewcoop@andrewcoop:/local/xen.git/xen$ ld --version
>>> GNU ld (GNU Binutils for Debian) 2.25
>>>
>>> On 04.10.18 at 12:45, wrote:
> The name 'need_iommu()' is a little confusing as it suggests a domain needs
> to use the IOMMU but something might not be set up yet, when in fact it
> represents a tri-state value (not a boolean as might be expected) where
> -1 means 'IOMMU mappings being set
flight 128388 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128388/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 16 guest-localmigrate/x10 fail
in 128363 pass in 128388
>>> On 05.10.18 at 15:39, wrote:
> On 05/10/18 14:28, Jan Beulich wrote:
>> 1: add FPU/SIMD register state test
>> 2: extend FPU exception tests
>>
>> Signed-off-by: Jan Beulich
>
> Thanks. However, I need to get the incremental test version logic
> working first, or OSSTest will block this on
>>> On 05.10.18 at 14:39, wrote:
> On 03/10/18 19:38, Andrew Cooper wrote:
>> Finally, this series doesn't link with the default Debian toolchain.
>>
>> andrewcoop@andrewcoop:/local/xen.git/xen$ ld --version
>> GNU ld (GNU Binutils for Debian) 2.25
>>
>> andrewcoop@andrewcoop:/local/xen.git/xen$
These parameters should have always been in the 'set once' category
but this has, so far, not been enforced.
Signed-off-by: Paul Durrant
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
---
xen/arch/x86/hvm/hvm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen/arch/x86/hvm/hvm.c
Paul Durrant (2):
x86/hvm: make sure HVM_PARAM_[BUF]IOREQ_PFN can only be set once
x86/hvm/ioreq: allow ioreq servers to use HVM_PARAM_[BUF]IOREQ_PFN
xen/arch/x86/hvm/hvm.c | 2 ++
xen/arch/x86/hvm/ioreq.c | 50 ++--
Since commit 2c257bd6 "x86/hvm: remove default ioreq server (again)" the
GFNs allocated by the toolstack and set in HVM_PARAM_IOREQ_PFN and
HVM_PARAM_BUFIOREQ_PFN have been unused. This patch allows them to be used
by (non-default) ioreq servers.
NOTE: This fixes a compatibility issue. A guest
On 05/10/18 14:28, Jan Beulich wrote:
> 1: add FPU/SIMD register state test
> 2: extend FPU exception tests
>
> Signed-off-by: Jan Beulich
Thanks. However, I need to get the incremental test version logic
working first, or OSSTest will block this on older versions of Xen, due
to (falsely)
flight 128413 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128413/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
freebsd 8f45b071b58d4a00be551ddcc52e78a06ed6fbc7
baseline version:
freebsd
Also test #MF and #XM handling.
Signed-off-by: Jan Beulich
---
v4: Re-base.
v3: New.
--- /dev/null
+++ b/arch/x86/include/arch/simd.h
@@ -0,0 +1,32 @@
+#ifndef XTF_X86_SIMD_H
+#define XTF_X86_SIMD_H
+
+#define X86_MXCSR_IE 0x0001
+#define X86_MXCSR_DE 0x0002
+#define
Add tests to verify that
- FPU insns leave correct (guest) values in FIP/FDP/FOP/FCS/FDS (at the
example for FSTPS),
- FPU insns writing memory don't update FPU register state when the
write faults (at the example of FISTPS),
- VCVTPS2PH doesn't update MXCSR if its write faults (VCVTPS2PH is
>>> On 05.10.18 at 14:18, wrote:
> On 05/10/18 12:31, Jan Beulich wrote:
>> A few pieces of the handling here are (no longer?) vendor specific, and
>> hence there's no point in replicating the code.
>
> EFER probably was vendor specific originally. The control registers
> really shouldn't have
1: add FPU/SIMD register state test
2: extend FPU exception tests
Signed-off-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Hi,
On 05/10/2018 12:06, Bharat Bhushan wrote:
Further update:
If I change Kconfig to enable this default
CONFIG_HAS_ITS is in tech preview. For having access to it, you need to
pass XEN_CONFIG_EXPERT on *all* the make command line.
Then DOM0 Linux Boots but MSIs are not still working,
On 10/5/18 7:31 AM, Jan Beulich wrote:
> A few pieces of the handling here are (no longer?) vendor specific, and
> hence there's no point in replicating the code. Make sure not otherwise
> pre-filled fields of struct hvm_hw_cpu instances are zero filled before
> calling the vendor "save" hook,
flight 128415 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128415/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
On 03/10/18 19:38, Andrew Cooper wrote:
> Finally, this series doesn't link with the default Debian toolchain.
>
> andrewcoop@andrewcoop:/local/xen.git/xen$ ld --version
> GNU ld (GNU Binutils for Debian) 2.25
>
> andrewcoop@andrewcoop:/local/xen.git/xen$ make -s build -j8
>
On 05/10/18 12:31, Jan Beulich wrote:
> A few pieces of the handling here are (no longer?) vendor specific, and
> hence there's no point in replicating the code.
EFER probably was vendor specific originally. The control registers
really shouldn't have been...
> Make sure not otherwise
>
>>> On 05.10.18 at 13:58, wrote:
> On 05/10/18 12:29, Jan Beulich wrote:
>> This is not used (and probably was never meant to be) by the tool stack.
>> Limiting it to the current domain in particular allows to eliminate a
>> bogus use of vCPU 0 in pagetable_dying().
>>
>> Remove the now
On 05/10/18 12:26, Jan Beulich wrote:
On 05.10.18 at 13:14, wrote:
>> On Fri, Oct 05, 2018 at 05:11:55AM -0600, Jan Beulich wrote:
>>> Older gcc, despite eliminating pci_clean_dpci_irqs() when !HVM, does
>>> not manage to also eliminate pci_clean_dpci_irq(). Cope with this.
>> Would be
On 10/5/18 2:31 PM, Jan Beulich wrote:
> A few pieces of the handling here are (no longer?) vendor specific, and
> hence there's no point in replicating the code. Make sure not otherwise
> pre-filled fields of struct hvm_hw_cpu instances are zero filled before
> calling the vendor "save" hook,
On 05/10/18 12:29, Jan Beulich wrote:
> This is not used (and probably was never meant to be) by the tool stack.
> Limiting it to the current domain in particular allows to eliminate a
> bogus use of vCPU 0 in pagetable_dying().
>
> Remove the now unnecessary domain/vCPU parameters from the
>>> On 05.10.18 at 13:43, wrote:
> On 05/10/18 12:25, Wei Liu wrote:
>> On Fri, Oct 05, 2018 at 05:22:29AM -0600, Jan Beulich wrote:
>> On 05.10.18 at 12:28, wrote:
On Fri, Oct 05, 2018 at 04:12:10AM -0600, Jan Beulich wrote:
> Now that CONFIG_HVM can (and should) be turned off for
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 05 October 2018 12:18
> To: George Dunlap ; Paul Durrant
>
> Cc: Andrew Cooper ; Ian Jackson
> ; Wei Liu ; Stefano
> Stabellini ; xen-devel de...@lists.xenproject.org>; Konrad Rzeszutek Wilk
> ; Tim (Xen.org)
>
On 05/10/18 12:25, Wei Liu wrote:
> On Fri, Oct 05, 2018 at 05:22:29AM -0600, Jan Beulich wrote:
> On 05.10.18 at 12:28, wrote:
>>> On Fri, Oct 05, 2018 at 04:12:10AM -0600, Jan Beulich wrote:
Now that CONFIG_HVM can (and should) be turned off for the shim, gcc 8.2
apparently is no
On Fri, Oct 05, 2018 at 05:35:13AM -0600, Jan Beulich wrote:
> >>> On 05.10.18 at 12:48, wrote:
> > Let me know what else is needed.
>
> The simple addition on top of what Andrew has said: A reliable
> repro ;-)
If I had managed to find one I would have debugged this myself. :-)
Wei.
>
> Jan
1 - 100 of 151 matches
Mail list logo
