flight 66414 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66414/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-winxpsp3 6 xen-boot fail REGR. vs. 59254
test-amd64-i386-freeb
From: Yang Hongyang
Add a new structure remus state, and move concrete layer's private
member to remus state.
it is pure refactoring and no functional changes.
Init interval in libxl__remus_setup(). It is safe to move this initialisation,
because this value is only used for remus, and remus will
From: Yang Hongyang
we call (init|cleanup)_subkind_nic and (init|cleanup)_subkind_drbd_disk
directly in checkpoint device. Move them to libxl_remus.c, Call them before
calling libxl__checkpoint_devices_setup() or after calling
libxl__checkpoint_devices_teardown().
it is pure refactoring and no fu
From: Yang Hongyang
After previous refactoring, we are now able to move all remus code
into a separate file libxl_remus.c.
Export following functions for internal use:
- Remus callbacks
* libxl__remus_domain_suspend_callback
* libxl__remus_domain_resume_callback
* libxl__remus_domain_save_
From: Yang Hongyang
The error code ERROR_REMUS_XXX was introduced in Xen 4.5, and
changed to ERROR_CHECKPOINT_XXX after previous renaming.
The patch fix the backword compatibility.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
---
tools/libxl/libxl.h | 13 +
1 file chan
From: Yang Hongyang
Checkpoint device is an abstract layer to do checkpoint.
COLO can also use it to do checkpoint. But there are
still some codes in checkpoint device which touch remus.
This patch and the following 2 will seperate remus from
checkpoint device layer.
We use remus ops directly i
From: Yang Hongyang
This patch is auto generated by the following commands:
1. git mv tools/libxl/libxl_remus_device.c
tools/libxl/libxl_checkpoint_device.c
2. perl -pi -e 's/libxl_remus_device/libxl_checkpoint_device/g'
tools/libxl/Makefile
3. perl -pi -e 's/\blibxl__remus_devices/libxl__ch
From: Yang Hongyang
This is purely code motion.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
CC: Ian Jackson
CC: Wei Liu
Acked-by: Ian Campbell
---
tools/libxl/Makefile | 2 +-
tools/libxl/libxl_dom.c | 605 -
tools/libxl/l
From: Yang Hongyang
This is just tidying up after the previous automatic renaming.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
Acked-by: Ian Campbell
---
tools/libxl/libxl_checkpoint_device.c | 21 +++--
tools/libxl/libxl_internal.h | 19 +++-
From: Yang Hongyang
Secondary vm is running in colo mode, we need to send
secondary vm's dirty page information to master at checkpoint,
so we have to enable qemu logdirty on secondary.
libxl__domain_suspend_common_switch_qemu_logdirty() is to enable
qemu logdirty. But it uses domain_save_state,
From: Yang Hongyang
introduce enum type libxl_checkpointed_stream in IDL.
rename the last argument of migrate_receive from "remus" to
"checkpointed" since the semantics of this parameter has
changed.
NOTE:
libxl_domain_restore_params isn't changed here,
checkpointed_stream is still an int.
Si
This patchset is Prerequisite for COLO feature. Refer to:
http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
v4->v5:
- Rebased to the latest xen
- Addressed comments from last round
v3->v4:
- Rebased to the latest migration v2 branch
- Addressed comments from last round
v2->v3:
- Me
In COLO mode, both VMs are running, and are considered in sync if the
visible network traffic is identical. After some time, they fall out of
sync.
At this point, the two VMs have definitely diverged. Lets call the
primary dirty bitmap set A, while the secondary dirty bitmap set B.
Sets A and B
From: Yang Hongyang
init stream {read/write} state checkpoint_callback in Remus setup callback.
There's no functional change, it's just refactoring so that we can move
all remus code into one file.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
CC: Andrew Cooper
CC: Ian Campbell
CC
From: Yang Hongyang
Pass checkpointed_stream from libxl to libxc.
It won't affact legacy migration because legacy migration
won't use this param.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
CC: Andrew Cooper
---
tools/libxc/include
From: Yang Hongyang
Currently struct libxl__domain_suspend_state contains 2 type of states,
one is save state, another is suspend state. This patch separates those
two out.
The motivation of this is that COLO will need to do suspend/resume
continuously, we need a more common suspend state.
After
From: Yang Hongyang
In colo mode, slave needs to send data to master, but the io_fd
only can be written in master, and only can be read in slave.
Save recv_fd in domain_suspend_state, and send_fd in
domain_create_state.
Extend libxl_domain_create_restore API, add a send_fd param to
it.
Add LIBXL_
From: Yang Hongyang
We need to enable logdirty on secondary, so we export logdirty_init
for internal use. Rename it to libxl__logdirty_init.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
Acked-by: Ian Campbell
---
tools/libxl/libxl_dom_save.c | 4 ++--
tools/libxl/libxl_internal.h
Befor this patch:
1. suspend
a. PVHVM and PV: we use the same way to suspend the guest (send the suspend
request to the guest). If the guest doesn't support evtchn, the xenstore
variant will be used, suspending the guest via XenBus control node.
b. pure HVM: we call xc_domain_shutdown(..., SH
From: Yang Hongyang
In normal migration, the qemu state was passed to qemu as a parameter.
With COLO, Secondary vm is running. So we will do the following steps
at every checkpoint:
1. suspend both primary vm and secondary vm
2. sync the state
3. resume both primary vm and secondary vm
Primary wi
flight 66415 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66415/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 15 guest-start/debian.repeatfail like 65748
test-amd64-i386-xl-qemut-stub
This run is configured for baseline tests only.
flight 38525 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38525/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 2
Hi,
I tried to setup xen serial console with this guide,
http://wiki.xen.org/wiki/Xen_Serial_Console
I am using RS232 -USB cable for this purpose.
I am on Ubuntu 15.10 (4.2.0-19-generic).
xl info http://paste2.org/F2UgY5yz
My output is garbled.
http://paste2.org/tZveaAGU
I will appreciate any
Thanks a lot and looking forward to that.
> Date: Wed, 16 Dec 2015 09:42:47 -0500
> Subject: Re: [Xen-devel] how to enable kdb for xen
> From: ufimts...@gmail.com
> To: konrad.w...@oracle.com
> CC: quizy_jo...@outlook.com; xen-devel@lists.xen.org;
> elena.ufimts...@oracle.com; t...@xen.org
>
> O
Sorry for the late reply, there is something wrong in network which makes the
email not delivered successfully.The inject method is by using
xc_map_foreign_range to map the address of the nested xen and memcpy the trap
to the specific location. If there is a problem, it should be the
xc_map_
flight 66413 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66413/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-raw 5 xen-install fail REGR. vs. 65654
Regressions which are reg
3.13.11-ckt32 -stable review patch. If anyone has any objections, please let
me know.
--
From: Andrew Cooper
commit 581b7f158fe0383b492acd1ce3fb4e99d4e57808 upstream.
There appears to be no formal statement of what pv_irq_ops.save_fl() is
supposed to return precisely. Native
This is a note to let you know that I have just added a patch titled
x86/cpu: Fix SMAP check in PVOPS environments
to the linux-3.13.y-queue branch of the 3.13.y-ckt extended stable tree
which can be found at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.13.y-queue
This
flight 66410 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66410/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 63732
test-amd64-amd64-xl-qe
On 12/16/15, Ian Campbell wrote:
> On Wed, 2015-12-16 at 01:01 +0330, Alireza Vaezi wrote:
>> I'm using Xen 4.4.2 and I need to be able to change or set my preferred
>> (available) ssl cipher suit like RC4-SHA, or DES-CBC-SHA , etc. to be
>> further used in relocation/migration of domU via ssl.
>>
Ian Campbell, on Wed 16 Dec 2015 12:31:08 +, wrote:
> ... rather than in the libxc rule.
>
> This puts all the header dependencies in one place and will allow us
> to avoid races when more libraries which need these headers are
> introduced. I observed issues with the xen-foreign/tmp.size file
flight 66412 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66412/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-pvops 5 kernel-build fail REGR. vs. 60684
build-i386
Signed-off-by: Andrew Cooper
---
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
CC: David Scott
CC: Rob Hoes
---
tools/libxc/include/xenctrl.h | 2 ++
tools/libxc/xc_misc.c | 14 ++
tools/ocaml/libs/xc/xenctrl.ml | 2 ++
tools/ocaml/libs/xc/xenctrl.mli
* Use the boot-generated pv and hvm featureset to clamp the visible features,
rather than picking and choosing at individual features. This subsumes most
of the feature availability checks.
* More use of compiler-visible &'s and |'s, rather than clear,set bit.
* Remove logic which hides PSE36
For HVM guests, there are two different featuresets, depending on whether hap
or shadow mode is used.
HVM Shadow guests are strictly more capable than PV guests, and HVM HAP are
strictly more capable than HVM Shadow; this is represented in the way the HVM
shadow and HAP masks are expressed.
Signe
This allows PV domains with different featuresets to observe different values
from a native cpuid instruction, on supporting hardware.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
---
xen/arch/x86/domctl.c | 68 +++
1 file changed, 68 insertio
Before c/s 44e24f8567 "x86: don't call generic_identify() redundantly", the
commandline-provided masks would take effect in Xen's view of the features.
As the masks got applied after the query for features, the redundant call to
generic_identify() would clobber the wrong feature information with t
APIC and XSAVE have dependent features, which also need disabling if Xen
chooses to disable a feature.
Use setup_clear_cpu_cap() rather than clear_bit(), as it takes care of
dependent features as well.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
---
xen/arch/x86/apic.c | 4 ++--
xe
This patch is best reviewed as its end result rather than as a diff, as it
rewrites almost all of the setup.
On the BSP, cpuid information is used to evaluate the potential available set
of masking MSRs, and they are unconditionally probed, filling in the
availability information and hardware defa
Later changes will add to this logic.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
---
xen/arch/x86/domctl.c | 64 ---
1 file changed, 35 insertions(+), 29 deletions(-)
diff --git a/xen/arch/x86/domctl.c b/xen/arch/x86/domctl.c
index bf62a88.
It is conceptually wrong to base a VM's featureset on the features visible to
the toolstack which happens to construct it.
Instead, the featureset used is either an explicit one passed by the
toolstack, or the default which Xen believes it can give to the guest.
Signed-off-by: Andrew Cooper
---
When clearing a cpu cap, clear all dependent features. This avoids having a
featureset with intermediate features disabled, but leaf features enabled.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
---
xen/arch/x86/cpu/common.c | 16
1 file changed, 16 insertions(+)
diff --
Future changes will make use of this to advertise availability of levelling
support, and to provide lazy context switching.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
---
xen/arch/x86/cpu/common.c| 3 +++
xen/include/asm-x86/cpufeature.h | 1 +
xen/include/asm-x86/processor.h |
And use them in preference to cpumask_defaults on context switch. HVM domains
must not be masked (to avoid interfering with cpuid calls within the guest),
so always lazily context switch to the host default.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
---
xen/arch/x86/cpu/amd.c | 4
This allows the toolstack to query what exactly Xen can control in a PV guest
issuing a native `cpuid` instruction.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Tim Deegan
CC: Ian Campbell
---
xen/arch/x86/cpu/common.c | 3 +++
xen/arch/x86/sysctl.c | 6 ++
xen/i
Some features depend on other features. Working out and maintaining the exact
dependency tree is complicated, so it is expressed in script form instead.
`gen-feature-deps.py` parses 'xen/include/public/arch-x86/featureset.h' (To
obtain some literal names conforming to the API), contains some sing
When generating a VM featureset, clearing individual features is problematic
if a feature has dependent features.
Instead of disabling individual features, collect all disabling together in
sanitise_featureset(), and perform deep dependency removal on the result, to
remove all impacted features.
This patch is best reviewed as its end result rather than as a diff, as it
rewrites almost all of the setup.
On the BSP, cpuid information is used to evaluate the potential available set
of masking MSRs, and they are unconditionally probed, filling in the
availability information and hardware defa
It is able to reports the current featuresets; both the static masks and
dynamic featuresets from Xen, or to decode an arbitrary featureset into
`/proc/cpuinfo` style strings.
Signed-off-by: Andrew Cooper
---
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
.gitignore
A single ctxt_switch_levelling() function pointer is provided
(defaulting to an empty nop), which is overridden in the appropriate
$VENDOR_init_levelling().
set_cpuid_faulting() is made private and included within
intel_ctxt_switch_levelling()
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
--
Calculate and expose the raw featureset to userspace. This is for
informational purposes; the difference between the raw and the host
featuresets are the features Xen has specifically chosen not to use.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Tim Deegan
CC: Ian Campbell
---
xen/
Later changes will cause the cpuid generation logic to seed their information
from a featureset. This patch adds the infrastructure to specify a
featureset, and will obtain the appropriate default from Xen if omitted.
Signed-off-by: Andrew Cooper
---
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Li
Use the new gen-feature-deps.py infrastructure to automatically generate
known_features[], rather than requiring people to patch two places to add a
new feature for hypervisor use.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
TODO: Probably move the introduction of gen-feature-deps.py earie
It is unsafe to generate the guests xstate leaves from host information, as it
prevents the differences between hosts from being hidden.
Signed-off-by: Andrew Cooper
---
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libxc/xc_cpuid_x86.c | 44 ++
Guest featuresets are seeded from the host featureset, and the host featureset
has calculated in the front of boot_cpu_data.x86_capability.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
---
xen/arch/x86/Makefile | 1 +
xen/arch/x86/cpuid.c| 23 +++
xen/arch
Presented here is v1 of my work to improve cpuid levelling for guests. This
series is very close to what is now present in XenServer trunk, and testing is
going well.
This series is available in git form at:
http://xenbits.xen.org/git-http/people/andrewcoop/xen.git levelling-v1
This entire ser
The PV featuremask is the collection of features a PV guest can safely use
(i.e. has support in Xen, or needs no hypervisor support).
The PV guest featureset is then the host featureset, clipped to the PV mask.
As part of this work, I introduced all the remaining bits in leaf 7 which can
be enabl
Signed-off-by: Andrew Cooper
---
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
CC: David Scott
CC: Rob Hoes
---
tools/libxc/include/xenctrl.h | 3 +++
tools/libxc/xc_misc.c | 27 +++
tools/ocaml/libs/xc/xenctrl.ml | 3 +++
tools/ocaml/libs/xc
If Xen doesn't know about a feature, it is unsafe for use and should be
deliberately hidden from Xen's capabilities.
This doesn't make a practical difference yet, but will make a difference
later when the guest featuresets are seeded from the host featureset.
Signed-off-by: Andrew Cooper
---
CC:
Awkwardly, some new feature bits mean "Feature $X no longer works".
Store these inverted in a featureset.
This permits safe zero-extending of a smaller featureset as part of a
comparison, and safe reasoning (subset?, superset?, compatible? etc.)
without specific knowldge of meaning of each bit.
S
New words are:
* 0x0007:0.ecx - New for Intel Skylake processors
* 0x8007.edx - Contains Invarient TSC
* 0x8008.ebx - Newly used for AMD Zen processors
In addition, replace a lot of open-coded Invarient TSC manipulation.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
---
xen/a
Rather than having a different local copy of some of the feature
definitions.
Modify the xc_cpuid_x86.c cpumask helpers to appropriate truncate the
new values, and add X86_FEATURE_TSC_ADJUST to the public API to allow
libxc to continue compiling.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
For the featureset to be a useful object, it needs a stable interpretation, a
property which is missing from the current hw_caps interface.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Tim Deegan
CC: Ian Campbell
---
xen/include/asm-x86/cpufeature.h | 175 +
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Tim Deegan
CC: Ian Campbell
---
xen/arch/x86/sysctl.c | 51 +
xen/include/public/sysctl.h | 20 ++
2 files changed, 71 insertions(+)
diff --git a/xen/arch/x86/sysctl.c b/xen/
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemuu-winxpsp3-vcpus1
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-tr
On 12/16/2015 04:04 AM, Jan Beulich wrote:
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -3116,6 +3116,21 @@ int hvm_hap_nested_page_fault(paddr_t gpa, unsigned long
gla,
goto out_put_gfn;
}
+if ( (p2mt == p2m_mmio_direct) && is_hardware_domain(currd) )
On 16/12/15 12:31, Ian Campbell wrote:
> libxengnttab will provide a stable API and ABI for accessing the
> grant table devices.
>
> The functions are moved into the xengnt{tab,shr} namespace to make a
> clean break from libxc and avoid ambiguity regarding which interfaces
> are stable.
>
> All in-
On Wed, 9 Dec 2015, Ian Campbell wrote:
> Currently only GICv2 support is implemented.
>
> Given the differing architectural state between the GICv2 and v3 I
> ended up with separate save records. I'm not sure if this is the best
> plan. I have also split the state into GICD (per domain) and GICC
flight 66434 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66434/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 13
On 01/12/15 11:53, George Dunlap wrote:
> save_domain was already constructing an error code; it just wasn't
> being used.
>
> Signed-off-by: George Dunlap
> ---
> CC: Ian Campbell
> CC: Ian Jackson
> CC: Wei Liu
> ---
> tools/libxl/xl_cmdimpl.c | 3 +--
> 1 file changed, 1 insertion(+), 2 de
flight 66400 linux-3.16 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66400/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 64969
test-amd64-i386-xl-qem
On Wed, 16 Dec 2015, Ian Campbell wrote:
> On Wed, 2015-12-16 at 15:53 +, Stefano Stabellini wrote:
> > On Wed, 9 Dec 2015, Ian Campbell wrote:
> > > Signed-off-by: Ian Campbell
> > > ---
> > > xen/arch/arm/vtimer.c | 72
> > > ++
> > > xen/inc
On 14/12/15 14:39, David Vrabel wrote:
> Holding the p2m lock while calling ept_sync_domain() is very expensive
> since it does a on_selected_cpus() call. IPIs on many socket machines
> can be very slows and on_selected_cpus() is serialized.
>
> Defer the invalidate until the p2m lock is released
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andrew Cooper
commit 581b7f158fe0383b492acd1ce3fb4e99d4e57808 upstream.
There appears to be no formal statement of what pv_irq_ops.save_fl() is
supposed to return precisely. Native
At 16:34 + on 16 Dec (1450283699), Andrew Cooper wrote:
> On 16/12/15 16:28, Tim Deegan wrote:
> > Hi,
> >
> > At 15:36 + on 16 Dec (1450280191), George Dunlap wrote:
> >> (hvm_fetch_from_guest_virt() seems to only set PFEC_insn_fetch if nx or
> >> smep are enabled in the guest. This seems
These are intended to allow user space processes (in particular QEMU)
to lock down all the handles at start of day and then drop the
privileges which would allow them to open any new unrestricted handles
(e.g. setuid or similar). This will reduce the privileges which taking
over such a process woul
At 16:50 + on 16 Dec (1450284615), George Dunlap wrote:
> On 16/12/15 16:28, Tim Deegan wrote:
> > Hi,
> >
> > At 15:36 + on 16 Dec (1450280191), George Dunlap wrote:
> >> (hvm_fetch_from_guest_virt() seems to only set PFEC_insn_fetch if nx or
> >> smep are enabled in the guest. This seem
On 16/12/15 16:53, George Dunlap wrote:
> On 08/12/15 17:15, Ian Campbell wrote:
>> On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
>>> Return proper error codes on failure so that scripts can tell whether
>>> the command completed properly or not.
>>>
>>> Also while we're at it, normalize
>>> On 16.12.15 at 17:10, wrote:
> The unconditional printks in the switch statement of the
> hvm_set_callback_via function results in Xen log spam in non debug
> versions of Xen.
Oh, now I see - that's because dprintk() is a no-op inline nowadays.
> --- a/xen/arch/x86/hvm/irq.c
> +++ b/xen/arch
>>> On 16.12.15 at 13:00, wrote:
> Use the Kconfig generated CONFIG_COMPAT defines in the code base.
>
> CC: Keir Fraser
> CC: Jan Beulich
> CC: Andrew Cooper
> Signed-off-by: Doug Goldstein
> ---
> config/x86_64.mk | 1 -
> xen/arch/x86/Kconfig | 1 +
> xen/common/Kconfig | 7 +++
On Wed, Dec 16, 2015 at 11:34:07AM -0500, Boris Ostrovsky wrote:
> The tables are almost identical and therefore there is little reason to
> keep both sets.
>
> PVH needs 3 extra hypercalls:
> * mmuext_op. MMUEXT_PIN_L_TABLE are required by control domain (dom0)
> when building guests.
> * platf
On 08/12/15 17:15, Ian Campbell wrote:
> On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
>> Return proper error codes on failure so that scripts can tell whether
>> the command completed properly or not.
>>
>> Also while we're at it, normalize init and dispose of
>> libxl_device_disk struct
On 16/12/15 16:28, Tim Deegan wrote:
> Hi,
>
> At 15:36 + on 16 Dec (1450280191), George Dunlap wrote:
>> (hvm_fetch_from_guest_virt() seems to only set PFEC_insn_fetch if nx or
>> smep are enabled in the guest. This seems inconsistent to me with the
>> treatment of PFEC_reserved_bit: it seem
On Wed, 2015-12-16 at 16:17 +, Julien Grall wrote:
> Hi,
>
> On 16/12/15 16:02, Ian Campbell wrote:
> > The PPI state is saved by the GIC. Perhaps we should save the actual
> > number
> > used by the guest here though.
>
> I think we have to save the actual number as we don't guarantee that t
On Wed, 2015-12-16 at 16:22 +, Stefano Stabellini wrote:
> On Wed, 9 Dec 2015, Ian Campbell wrote:
> > Signed-off-by: Ian Campbell
> > ---
> > tools/libxc/xc_resume.c | 18 ++
> > 1 file changed, 18 insertions(+)
> >
> > diff --git a/tools/libxc/xc_resume.c b/tools/libxc/xc_r
On 16/12/15 16:28, Tim Deegan wrote:
> Hi,
>
> At 15:36 + on 16 Dec (1450280191), George Dunlap wrote:
>> (hvm_fetch_from_guest_virt() seems to only set PFEC_insn_fetch if nx or
>> smep are enabled in the guest. This seems inconsistent to me with the
>> treatment of PFEC_reserved_bit: it seems
The tables are almost identical and therefore there is little reason to
keep both sets.
PVH needs 3 extra hypercalls:
* mmuext_op. MMUEXT_PIN_L_TABLE are required by control domain (dom0)
when building guests.
* platform_op. These are only available to privileged domains. We will
(eventually)
Hi,
At 15:36 + on 16 Dec (1450280191), George Dunlap wrote:
> (hvm_fetch_from_guest_virt() seems to only set PFEC_insn_fetch if nx or
> smep are enabled in the guest. This seems inconsistent to me with the
> treatment of PFEC_reserved_bit: it seems like
> hvm_fetch_from_guest_virt() should al
On Wed, 9 Dec 2015, Ian Campbell wrote:
> Signed-off-by: Ian Campbell
> ---
> tools/libxc/xc_resume.c | 18 ++
> 1 file changed, 18 insertions(+)
>
> diff --git a/tools/libxc/xc_resume.c b/tools/libxc/xc_resume.c
> index 87d4324..fa16c3e 100644
> --- a/tools/libxc/xc_resume.c
> +
Hi,
On 16/12/15 16:02, Ian Campbell wrote:
> The PPI state is saved by the GIC. Perhaps we should save the actual number
> used by the guest here though.
I think we have to save the actual number as we don't guarantee that the
interrupt (and memory layout BTW) for the guest won't change between 2
The unconditional printks in the switch statement of the
hvm_set_callback_via function results in Xen log spam in non debug
versions of Xen. The printks are for debug output only so conditionally
compile the entire switch statement on debug versions of Xen only.
---
xen/arch/x86/hvm/irq.c | 4 +++-
On 14/12/15 14:41, David Vrabel wrote:
> On 07/12/15 10:25, George Dunlap wrote:
>>
>> I took the past tense ("synced") to mean, "These CPUs have been
>> brought into sync (or are no longer out of sync)". So they start out
>> not-synced, so you initialize the bit to be clear; when an INVEPT is
>>
On Wed, 2015-12-16 at 15:53 +, Stefano Stabellini wrote:
> On Wed, 9 Dec 2015, Ian Campbell wrote:
> > Signed-off-by: Ian Campbell
> > ---
> > xen/arch/arm/vtimer.c | 72
> > ++
> > xen/include/public/arch-arm/hvm/save.h | 15 ++-
> > 2 fil
On Wed, 9 Dec 2015, Ian Campbell wrote:
> Signed-off-by: Ian Campbell
> ---
> xen/arch/arm/vtimer.c | 72
> ++
> xen/include/public/arch-arm/hvm/save.h | 15 ++-
> 2 files changed, 86 insertions(+), 1 deletion(-)
>
> diff --git a/xen/arch/arm
[Adding Tim, the previous mm maintainer]
On 11/12/15 09:16, Wu, Feng wrote:
>>> +{
>>> +void *xsave_addr;
>>> +unsigned int pkru = 0;
>>> +bool_t pkru_ad, pkru_wd;
>>> +
>>> +bool_t uf = !!(pfec & PFEC_user_mode);
>>> +bool_t wf = !!(pfec & PFEC_write_access);
>>> +bool_t f
On Wed, 2015-12-16 at 15:06 +, Ian Campbell wrote:
> -XENFIRMWAREDIR=`eval echo $libexecdir/$PACKAGE_TARNAME/boot`
> +dnl These variables will be substituted in various .in files
> +LIBEXEC_BIN=${LIBEXEC}/bin
> +AC_SUBST(LIBEXEC_BIN)
> +LIBEXEC_LIB=${LIBEXEC}/lib
> +AC_SUBST(LIBEXEC_LIB)
> +LIB
flight 38518 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38518/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-i386-daily-netboot-pvgrub 9 debian-di-install fail like 38464
test-amd64-i38
>>> On 28.11.15 at 22:45, wrote:
> ---
> v13:
> Changed to uint32_t arch_flags, since the emulation_flags is this.
I don't really understand this sentence, and I also don't understand
why you couldn't just use another XEN_X86_EMU_ flag, e.g.
XEN_X86_EMU_VMWARE_PORT (which would be the first one
Currently we hardcode various paths such as $libexec/xen/{bin,boot},
however some downstreams (notably Debian) would like instead to
install things into $libexec/xen-X.Y/{bin,boot} as part of allowing
multiple versions of the tools packages to be installed.
Since this currently involves patching c
On Wed, 2015-12-16 at 14:55 +, Stefano Stabellini wrote:
> On Wed, 9 Dec 2015, Ian Campbell wrote:
> > XXX TBD No support for arm64 (or even 32-bit guest on arm64).
> > XXX In particular the handling of save/restore of VFP state doesn't
> > XXX even compile for arm32. I need to investigate the
1 - 100 of 229 matches
Mail list logo
