Hi Stefano,
On 2017/3/18 1:21, Stefano Stabellini wrote:
> On Fri, 17 Mar 2017, Wei Chen wrote:
>> Hi Stefano,
>> On 2017/3/17 7:30, Stefano Stabellini wrote:
>>> On Mon, 13 Mar 2017, Wei Chen wrote:
In the later patches of this series, we want to use the alternative
patching framework t
Hi Konrad,
On 2017/3/17 22:34, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 16, 2017 at 05:53:38PM +0800, Wei Chen wrote:
>> This patch is based on the implementation of ARM64, it introduces
>> alternative runtime patching to ARM32. This allows to patch assembly
>> instruction at runtime to either f
flight 106777 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106777/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-cubietruck 11 guest-start fail REGR. vs. 59254
test-armhf-armhf-li
flight 106779 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106779/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 032862642d7184f7ab335b1c38b43d86c79349f5
baseline version:
ovmf 135ae8c873bb18600b847
On 03/17/2017 06:54 PM, Wei Liu wrote:
On Fri, Mar 17, 2017 at 04:42:30PM +0800, Zhang Chen wrote:
After related patch merged by Xen, qemu side patch got
some comments to change the API in qemu community.
So we update Xen side codes.
Qemu patchs:
https://lists.nongnu.org/archive/html/qemu-dev
On 2017年03月17日 22:48, Paolo Bonzini wrote:
>
>
> On 17/03/2017 12:29, Lan Tianyu wrote:
>> This patchset is to add Xen vIOMMU device model and handle
>> irq remapping stuffs. Xen vIOMMU emulation is in the Xen hypervisor
>> and the new device module in Qemu works as hypercall wrappers to
>> creat
On March 16, 2017 11:32 PM, Jan Beulich wrote:
On 16.03.17 at 15:21, wrote:
>> On March 16, 2017 10:06 PM, Jan Beulich wrote:
>> On 16.03.17 at 14:55, wrote:
I try to pass-through a device with 8G large bar, such as nvidia
M60(note1, pci-e info as below). It takes about '__15 s
flight 106776 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106776/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 3 host-install(3) broken in
106768 pass in 106776
test-amd64-amd64-x
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Subject: [Qemu-devel] [RFC QEMU PATCH v2 00/10] Implement vNVDIMM for Xen HVM
guest
Message-id: 20170320001249.25521-1-haozhong.zh...@intel.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script wil
xen-ndctl is a tool for users in Dom0 to setup the host pmem with Xen
hypervisor. It's used to specify the storage, which is either the
regular RAM or a pmem range, to manage the specified pmem.
Signed-off-by: Haozhong Zhang
---
Cc: Ian Jackson
Cc: Wei Liu
---
.gitignore | 1 +
t
Xen relies on QEMU to build guest ACPI for NVDIMM. However, no fw_cfg
is created when QEMU is used as Xen device model, so QEMU should avoid
using fw_cfg on Xen.
Signed-off-by: Haozhong Zhang
---
Cc: "Michael S. Tsirkin"
Cc: Igor Mammedov
Cc: Xiao Guangrong
---
hw/acpi/aml-build.c | 9 ++-
Add CONFIG_PMEM to enable NVDIMM persistent memory support. By
default, it's N.
Signed-off-by: Haozhong Zhang
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
---
xen/common/Kconfig | 9 +++
The current QEMU implementation allocates guest physical address for
vNVDIMM in the hotplug memory region, which was not created when QEMU
is used as Xen device model. Reuse existing code in i386/pc.c to
create the hotplug memory region for HVM domain on Xen, so that we can
reuse other parts of NVD
libacpi needs to access information placed in XenStore in order to
load ACPI built by the device model.
Signed-off-by: Haozhong Zhang
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Ian Jackson
Cc: Wei Liu
Changes in v2:
* Extract the common part of the existing xenstore_read() and the
new xen
We can map host pmem devices or files on pmem devices to guests. This
patch adds support to map pmem devices. The implementation relies on
the Linux pmem driver (CONFIG_ACPI_NFIT, CONFIG_LIBNVDIMM, CONFIG_BLK_DEV_PMEM),
so it functions only when libxl is compiled for Linux right now.
Signed-off-by
If QEMU is running as Xen device model and Xen needs ACPI (e.g. NFIT)
from QEMU, initiate building DM ACPI.
Signed-off-by: Haozhong Zhang
---
Cc: "Michael S. Tsirkin"
Cc: Paolo Bonzini
Cc: Richard Henderson
Cc: Eduardo Habkost
Cc: Stefano Stabellini
Cc: Anthony Perard
Cc: xen-de...@lists.xe
If xen_enabled(), memory_region_get_ram_ptr() always returns NULL and
nvdimm_realize() cannot get the correct pointer to the label area. This
commit disables the label support for Xen accelerator to workaround
this issue.
Signed-off-by: Haozhong Zhang
---
Cc: "Michael S. Tsirkin"
Cc: Igor Mammed
Some virtual devices (e.g. NVDIMM) require complex ACPI tables and
definition blocks (in AML), which a device model (e.g. QEMU) has
already been able to construct. Instead of introducing the similar
implementation to Xen, we would like to reuse the device model to
provide those ACPI stuffs.
This c
The AML builder added later requires this information to implement a
memory allocator that can allocate contiguous memory across multiple
calls to mem_ops.alloc().
Signed-off-by: Haozhong Zhang
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Ian Jackson
Cc: Wei Liu
Changes in v2:
* Only expose th
Xen hypervisor is not aware which portions of pmem can be used to
store the frame table and M2P table of pmem. Instead, it provides
users or admins in Dom0 with a sysctl XEN_SYSCTL_nvdimm_pmem_setup to
specify the location.
XEN_SYSCTL_nvdimm_pmem_setup receives four arguments: data_smfn,
data_emfn
XENMEM_populate_pmemmap is used by toolstack to map the specified host
pmem pages to the specified guest physical address. Only pmem pages
that have been setup via XEN_SYSCTL_nvdimm_pmem_setup can be mapped
via XENMEM_populate_pmem_map. Because XEN_SYSCTL_nvdimm_pmem_setup only
works on x86, XENMEM
Some virtual devices (e.g. NVDIMM) use the host memory backend to map
its backend resources to the guest. When those devices are used on Xen,
the mapping has to be managed out of QEMU. In order to reuse other parts
of the implementation of those devices, we introduce a host memory
backend for Xen (
ACPI tables built by the device model, whose signatures do not
conflict with tables built by Xen (except SSDT), are loaded after ACPI
tables built by Xen.
ACPI namespace devices built by the device model, whose names do not
conflict with devices built by Xen, are assembled and placed in SSDTs
afte
The address of ACPI blobs passed from device model is provided via
XenStore as the physical address. libacpi needs this callback to
access them.
Signed-off-by: Haozhong Zhang
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Ian Jackson
Cc: Wei Liu
---
tools/firmware/hvmloader/util.c | 6 ++
to
Probe the address ranges of pmem regions via ACPI NFIT and report them
to Xen hypervisor.
Signed-off-by: Haozhong Zhang
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/acpi/boot.c | 4 ++
xen/common/Makefile | 1 +
xen/common/pmem.c | 106 +
This is the QEMU patch of v2 RFC patch series to enable vNVDIMM
support for Xen HVM guest. v1 can be found at
https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg01678.html.
The corresponding Xen patch series is sent in another thread
"[RFC XEN PATCH v2 00/15] Add vNVDIMM support to HVM domai
Signed-off-by: Haozhong Zhang
---
Cc: Stefano Stabellini
Cc: Anthony Perard
Cc: xen-de...@lists.xenproject.org
---
include/hw/xen/xen.h | 18
xen-hvm-stub.c | 6 +++
xen-hvm.c| 113 +++
3 files changed, 137 insertions
Probe the base address and the length of guest ACPI buffer reserved
for copying ACPI from QEMU.
Signed-off-by: Haozhong Zhang
---
Cc: Stefano Stabellini
Cc: Anthony Perard
Cc: xen-de...@lists.xenproject.org
---
xen-hvm.c | 66 +++
1 f
Xen is not aware which portions of pmem can be used to store its
frametable and M2P table. Instead, it will rely on users or system
admins in Dom0 to specify the location. For the regular RAM, no
functional change is introduced.
Signed-off-by: Haozhong Zhang
---
Cc: Jan Beulich
Cc: Andrew Cooper
For xl configs
vnvdimms = [ '/path/to/pmem0', '/path/to/pmem1', ... ]
the following qemu options are built
-machine ,nvdimm
-m ,slots=$NR_SLOTS,maxmem=$MEM_SIZE
-object memory-backend-xen,id=mem1,size=$PMEM0_SIZE,mem-path=/path/to/pmem0
-device nvdimm,id=nvdimm1,memdev=mem1
-object mem
It is used by libacpi to generate SSDTs from ACPI namespace devices
built by the device model.
Signed-off-by: Haozhong Zhang
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Ian Jackson
Cc: Wei Liu
Cc: ross.philip...@ainfosec.com
Changes in v2:
* Add code comment for what is built by each function
Build and copy NVDIMM namespace devices to guest when QEMU is used as
Xen device model. Only the body of each AML device is built and copied.
Xen hvmloader will complete other parts of namespace devices and put
in SSDT.
Signed-off-by: Haozhong Zhang
---
Cc: "Michael S. Tsirkin"
Cc: Igor Mammedov
Add an optional argument 'devtype' to 'query-memory-devices', which
is either 'dimm' or 'nvdimm'. If 'devtype' is missed or 'dimm', all
memory devices will be listed. If 'devtype' is 'nvdimm', only nvdimm
devices will be listed.
Signed-off-by: Haozhong Zhang
---
Cc: "Dr. David Alan Gilbert"
Cc:
Get the backend device, the guest SPA and the size of each vNVDIMM
device via QMP commands "query-memory-device devtype=nvdimm" and
"qom-get", and pass them to libxl to map each backend device to guest.
Signed-off-by: Haozhong Zhang
---
Cc: Ian Jackson
Cc: Wei Liu
Changes in v2:
* Fail the do
Xen relies on QEMU to build the guest NFIT.
Signed-off-by: Haozhong Zhang
---
Cc: "Michael S. Tsirkin"
Cc: Igor Mammedov
Cc: Xiao Guangrong
---
hw/acpi/nvdimm.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c
index bb45452e70..2509561729 100644
-
This is v2 RFC patch series to add vNVDIMM support to HVM domains.
v1 can be found at
https://lists.xenproject.org/archives/html/xen-devel/2016-10/msg00424.html.
No label and no _DSM except function 0 "query implemented functions"
is supported by this version, but they will be added by future pat
flight 106774 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106774/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-libvirt 3 host-install(3) broken pass in 106767
test-amd64-i386-xl-raw3
flight 106772 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106772/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 3 host-install(3) broken REGR.
vs. 59254
test-armhf-
flight 106770 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106770/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 3 host-install(3) broken
pass in 106765
test-amd64-i386-l
This test is similar to cirros-minios-stubdom-hvm test, differing by
explicitly exposing the xen netfront and blockfront drivers
Signed-off-by: Géza Gémes
---
tests/cirros-minios-stubdom-pvhvm | 30 ++
tests/series | 1 +
2 files changed, 31 inse
The existing cirros tests are enabled, with the following
exceptions:
cirros-minios-stubdom-hvm and cirros-minios-stubdom-pvhvm are
skipped as raisin does not install the stubdom
Signed-off-by: Géza Gémes
---
defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/defconfi
This test is similar to cirros-qemu-hvm test, differing by
explicitly exposing the xen netfront and blockfront drivers
Signed-off-by: Géza Gémes
---
tests/cirros-qemu-pvhvm | 29 +
tests/series| 1 +
2 files changed, 30 insertions(+)
create mode 100644 t
Change lopartsetup in order to handle partitions, which have the
boot flag enabled.
Signed-off-by: Géza Gémes
---
scripts/lopartsetup | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/scripts/lopartsetup b/scripts/lopartsetup
index bf33a28..04ce3cc 100755
--- a/scripts/lop
Change deb package build in order to symlink the files installed
to site-packages to dist-packages to have them inluded in the
default PYTHONPATH
Signed-off-by: Géza Gémes
---
scripts/mkdeb | 9 +
1 file changed, 9 insertions(+)
diff --git a/scripts/mkdeb b/scripts/mkdeb
index 3796300..
This test is the cirros equivalent of the bussybox-pv test
Signed-off-by: Géza Gémes
---
tests/cirros-separate-kernel-pv | 28
tests/series| 1 +
2 files changed, 29 insertions(+)
create mode 100644 tests/cirros-separate-kernel-pv
diff --git a/
This test verifies booting the cirros image using pygrub
Signed-off-by: Géza Gémes
---
tests/cirros-pygrub-pv | 27 +++
tests/series | 1 +
2 files changed, 28 insertions(+)
create mode 100644 tests/cirros-pygrub-pv
diff --git a/tests/cirros-pygrub-pv b/tests
This test verifies booting the cirros image using pvgrub2
Signed-off-by: Géza Gémes
---
tests/cirros-pvgrub2-pv | 27 +++
tests/series| 1 +
2 files changed, 28 insertions(+)
create mode 100644 tests/cirros-pvgrub2-pv
diff --git a/tests/cirros-pvgrub2-pv b/
First patch adds a symlink from python2.7/site-packages/*
to python2.7/dist-packages/ at debian package build, this fixes
pygrub imports.
The rest of the patches are the cirros tests rebased to current master
and the python fix, plus a trivial fix for the pygrub test. in this
new patchset pygrub t
This test is the cirros equivalent of the bussybox-hvm test
Signed-off-by: Géza Gémes
---
tests/cirros-qemu-hvm | 28
tests/series | 1 +
2 files changed, 29 insertions(+)
create mode 100644 tests/cirros-qemu-hvm
diff --git a/tests/cirros-qemu-hvm b/tests
This test verifies a cirros based hvm domain using a minios based
stubdom as its device model
Signed-off-by: Géza Gémes
---
tests/cirros-minios-stubdom-hvm | 29 +
tests/series| 1 +
2 files changed, 30 insertions(+)
create mode 100644 tests/cirr
Add support for using cirros images in raisin tests
Signed-off-by: Géza Gémes
---
configs/config-cirros | 44 ++
defconfig | 2 +
lib/common-tests.sh | 102 ++
3 files changed, 148 insertions(+)
create mode 100
Hi Paul,
On 03/17/2017 10:30 AM, Paul Durrant wrote:
This patch adds a command-line option (-xen-domid-restrict) which will
use the new libxendevicemodel API to restrict devicemodel operations to
the specified domid.
This patch also adds a tracepoint to allow successful enabling of the
restrict
On 03/17/2017 08:16 AM, Greg Kurz wrote:
On Thu, 16 Mar 2017 13:01:52 -0700
Stefano Stabellini wrote:
Use the new type in virtio-9p-device.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Aneesh Kumar K.V
CC: Greg Kurz
---
Reviewed-by: Greg Kurz
flight 106768 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106768/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 104301
Tests which are faili
which surprisingly (or maybe not) looks like
XEN_SYSCTL_TMEM_OP_SET_POOLS.
This hypercall came about, as explained in docs/misc/tmem-internals.html:
When tmem was first proposed to the linux kernel mailing list
(LKML), there was concern expressed about security of shared ephemeral
pools. The ini
Hey!
Please see the attached patches. I had hoped that I would have the
initial migrationv2 patches ready but other things preempted me .
This patchset moves two sub-ops (TMEM_RESTORE_NEW, TMEM_AUTH)
from the guest accessible one to the system admin controlled.
It made no sense to have them ther
The hypervisor code (tmemc_shared_pool_auth) since the inception
would consider auth values of:
0 - to disable authentication!
1 - to enable authentication for the given UUID.
The docs have it the other way around, so lets fix it.
Signed-off-by: Konrad Rzeszutek Wilk
---
Cc: Ian Jackson
Cc:
Having an off by default option allowing guests to join
_any_ shared pool is not very secure.
Lets eliminate tmem_shared_auth bootup option (which
was disabled by default) and have the code force this by default.
Signed-off-by: Konrad Rzeszutek Wilk
---
docs/misc/tmem-internals.html | 6 +
This used to be done under TMEM_RESTORE_NEW which was an hypercall
accessible by the guest. However there are couple of reasons
not to do it:
- No checking of domid on TMEM_RESTORE_NEW which meant that
any guest could create TMEM pools for other guests.
- The guest can already create pools usi
A simple
xl tmem-shared-auth -u --000A--0001 -A 0 0
resulted in uuid_low = 1 (correct) and uuid_high = 0 (umm?).
The issue was that for hex values above 'A' (or 'a') we forgot
to add 10.
Signed-off-by: Konrad Rzeszutek Wilk
---
Cc: Ian Jackson
Cc: Wei Liu
---
tools/li
flight 106767 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106767/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-pair 15 debian-install/dst_host fail REGR. vs. 106747
Regressions which
flight 106766 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106766/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 3 host-install(3) broken REGR.
vs. 59254
test-armhf-
flight 106769 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106769/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-xsm 3 host-install(3)broken REGR. vs. 106755
Re
flight 106771 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106771/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
coverity-amd646 coverity-upload fail REGR. vs. 106549
version t
flight 106765 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106765/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail in 106758 pass
in 106765
test-armhf-armhf-xl-rtd
65 matches
Mail list logo
