On 02/22/17 00:46 -0700, Jan Beulich wrote:
> >>> On 22.02.17 at 03:20, wrote:
> > On 02/22/17 09:28 +0800, Haozhong Zhang wrote:
> >> On 02/21/17 02:15 -0700, Jan Beulich wrote:
> >> > >>> On 21.02.17 at 03:11, wrote:
> > [..]
> >> > > + *
> >> > > + * Therefore, we clear the nested gue
>>> On 23.02.17 at 05:48, wrote:
> On 02/22/17 08:48 -0700, Jan Beulich wrote:
>> >>> On 17.02.17 at 07:39, wrote:
>> > --- a/xen/arch/x86/cpu/mcheck/mcaction.c
>> > +++ b/xen/arch/x86/cpu/mcheck/mcaction.c
>> > @@ -88,17 +88,19 @@ mc_memerr_dhandler(struct mca_binfo *binfo,
>> >
>>> On 23.02.17 at 06:14, wrote:
> On 02/22/17 08:59 -0700, Jan Beulich wrote:
>> >>> On 17.02.17 at 07:39, wrote:
>> > @@ -1552,6 +1553,21 @@ long do_mca(XEN_GUEST_HANDLE_PARAM(xen_mc_t)
>> > u_xen_mc)
>> > send_IPI_mask(cpumap, cmci_apic_vector);
>> > }
>> >
On 02/23/17 00:42 -0700, Jan Beulich wrote:
> >>> On 23.02.17 at 04:06, wrote:
> > On 02/22/17 06:53 -0700, Jan Beulich wrote:
> >> >>> On 17.02.17 at 07:39, wrote:
> >> > @@ -1709,6 +1724,7 @@ static void mce_softirq(void)
> >> > {
> >> > int cpu = smp_processor_id();
> >> > unsigned
2017-02-20 15:33, Joao Martins:
> On 02/17/2017 04:07 PM, Konrad Rzeszutek Wilk wrote:
> > On Thu, Feb 16, 2017 at 10:51:44PM +0100, Vincent JARDIN wrote:
> >> Le 16/02/2017 à 14:36, Konrad Rzeszutek Wilk a écrit :
> Is it time now to officially remove Dom0 support?
> >>> So we do have an prot
>From e101539e18625cb70dfaee58ae7e73aa5df7b8a9 Mon Sep 17 00:00:00 2001
From: Quan Xu
Date: Fri, 24 Feb 2017 08:43:16 +0800
Subject: [PATCH] x86/apicv: move posted_intr_vector handler to
pi_notification_interrupt
event_check_interrupt is likely used in pair with original delivery logic.
Now sinc
On 02/23/17 00:53 -0700, Jan Beulich wrote:
> >>> On 23.02.17 at 05:26, wrote:
> > On 02/22/17 08:36 -0700, Jan Beulich wrote:
> >> >>> On 17.02.17 at 07:39, wrote:
> >> All of this said - is this really a per-vCPU property, instead of a
> >> per-domain one?
> >
> > Per-vCPU. At least it can be
>>> On 23.02.17 at 09:54, wrote:
> On 02/23/17 00:53 -0700, Jan Beulich wrote:
>> >>> On 23.02.17 at 05:26, wrote:
>> > On 02/22/17 08:36 -0700, Jan Beulich wrote:
>> >> >>> On 17.02.17 at 07:39, wrote:
>> >> All of this said - is this really a per-vCPU property, instead of a
>> >> per-domain on
On 02/23/17 01:26 -0700, Jan Beulich wrote:
> >>> On 23.02.17 at 06:14, wrote:
> > On 02/22/17 08:59 -0700, Jan Beulich wrote:
> >> >>> On 17.02.17 at 07:39, wrote:
> >> > @@ -1552,6 +1553,21 @@ long do_mca(XEN_GUEST_HANDLE_PARAM(xen_mc_t)
> >> > u_xen_mc)
> >> > send_IPI_mask(c
On Wed, Feb 22, 2017 at 09:22:25AM -0800, Stefano Stabellini wrote:
> On Wed, 22 Feb 2017, Edgar E. Iglesias wrote:
> > On Tue, Feb 21, 2017 at 07:20:29PM +, Julien Grall wrote:
> > >
> > >
> > > On 21/02/2017 18:30, Stefano Stabellini wrote:
> > > >On Tue, 21 Feb 2017, Julien Grall wrote:
>
>>> On 23.02.17 at 10:14, wrote:
> On 02/23/17 01:26 -0700, Jan Beulich wrote:
>> >>> On 23.02.17 at 06:14, wrote:
>> > On 02/22/17 08:59 -0700, Jan Beulich wrote:
>> >> >>> On 17.02.17 at 07:39, wrote:
>> >> > @@ -1552,6 +1553,21 @@ long do_mca(XEN_GUEST_HANDLE_PARAM(xen_mc_t)
> u_xen_mc)
>> >
On Wed, Feb 22, 2017 at 09:29:47AM -0800, Stefano Stabellini wrote:
> Introduce new Xen command line parameter called "vwfi", which stands for
> virtual wfi. The default is "trap": Xen traps the guest wfi instruction
> and calls vcpu_block on the guest vcpu. The behavior can be changed
> setting vw
This run is configured for baseline tests only.
flight 68606 qemu-upstream-4.5-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68606/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd
Storing -1 into both fields was misleading consumers: We really should
have a manifest constant for "invalid vCPU" here, and the already
existing DOMID_INVALID should be used.
Also correct a bogus (dead code) check in mca_init_global(), at once
introducing a manifest constant for the early boot "i
On February 18, 2017 12:33 AM, Jan Beulich wrote:
On 17.02.17 at 09:49, wrote:
>> On Fri, Feb 17, 2017 at 09:37:45AM +, Xuquan (Quan Xu) wrote:
>>>From a589074281cc22a30ed75a5bccba60e83d2312a6 Mon Sep 17
>00:00:00 2001
>>>From: Quan Xu
>>>Date: Sat, 18 Feb 2017 09:27:37 +0800
>>>Subject:
Replace linear scan with vmx_find_msr(). This way the time complexity
of searching for required MSR reduces from linear to logarithmic.
Signed-off-by: Sergey Dyasli
Acked-by: Kevin Tian
Reviewed-by: Jan Beulich
---
v2 --> v3:
- no changes
xen/arch/x86/hvm/vmx/vmcs.c | 26
>>> On 23.02.17 at 09:50, wrote:
> event_check_interrupt is likely used in pair with original delivery logic.
> Now since delivery path is changed, we should move to
> pi_notification_interrupt
> always.
I don't think this is sufficient explanation. What change in the
delivery path are you talki
Modify vmx_add_msr() to use a variation of insertion sort algorithm:
find a place for the new entry and shift all subsequent elements before
insertion.
The new vmx_find_msr() exploits the fact that MSR list is now sorted
and reuses the existing code for binary search.
Signed-off-by: Sergey Dyasli
During VM entry, H/W will automatically load guest's MSRs from MSR-load
area in the same way as they would be written by WRMSR.
However, under the following conditions:
1. LBR (Last Branch Record) MSRs were placed in the MSR-load area
2. Address format of LBR includes TSX bits 61:62
3
The first 2 patches is a general optimization which is nice to have
prior to the 3rd patch which contains the real fix.
A similar bug was fixed in Linux's perf subsystem in Jun 2016:
commit 19fc9ddd61e059cc45464bdf6e8fa304bb94080f
("perf/x86/intel: Fix MSR_LAST_BRANCH_FROM_x bug when no T
flight 68607 distros-debian-wheezy real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68607/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
build-arm64 2 hosts-allocate broken never pass
build-arm64-pvops
For a HVM domain, if a vcpu is in the nested guest mode,
__copy_field_to_guest() and __copy_to_guest() used by
update_secondary_system_time() will copy data to L2 guest rather than
L1 guest.
This commit temporally clears the nested guest flag before all
__copy_field_to_guest() and __copy_to_guest(
For a HVM domain, if a vcpu is in the nested guest mode,
__raw_copy_to_guest() and __copy_to_guest() used by
update_runstate_area() will copy data to L2 guest rather than L1
guest.
Besides copying to the wrong address, this bug also causes crash in
the code path:
context_switch(prev, next)
The current implementation of nested VMX cannot work without HAP.
Signed-off-by: Haozhong Zhang
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/hvm/hvm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
index 6621d62..b8
On Tue, Feb 21, 2017 at 12:00:03PM +, Xen.org security team wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Xen Security Advisory CVE-2017-2620 / XSA-209
> version 3
>
>cirrus_bitblt_cputovideo does not check if memory region is safe
>>> On 22.02.17 at 19:20, wrote:
> flight 105966 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/105966/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-qemuu-nested-amd 13 xen-boot/l
>>> On 23.02.17 at 10:33, wrote:
> During VM entry, H/W will automatically load guest's MSRs from MSR-load
> area in the same way as they would be written by WRMSR.
>
> However, under the following conditions:
>
> 1. LBR (Last Branch Record) MSRs were placed in the MSR-load area
> 2. Add
>>> On 23.02.17 at 10:28, wrote:
> On February 18, 2017 12:33 AM, Jan Beulich wrote:
> On 17.02.17 at 09:49, wrote:
>>> On Fri, Feb 17, 2017 at 09:37:45AM +, Xuquan (Quan Xu) wrote:
From a589074281cc22a30ed75a5bccba60e83d2312a6 Mon Sep 17
>>00:00:00 2001
From: Quan Xu
Date: S
On 23/02/17 20:43, Roger Pau Monné wrote:
> On Tue, Feb 21, 2017 at 12:00:03PM +, Xen.org security team wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Xen Security Advisory CVE-2017-2620 / XSA-209
>> version 3
>>
>>cirrus_bitblt_cp
On 02/23/17 02:28 -0700, Jan Beulich wrote:
> Storing -1 into both fields was misleading consumers: We really should
> have a manifest constant for "invalid vCPU" here, and the already
> existing DOMID_INVALID should be used.
>
> Also correct a bogus (dead code) check in mca_init_global(), at once
>>> On 23.02.17 at 11:01, wrote:
> On 02/23/17 02:28 -0700, Jan Beulich wrote:
>> --- a/xen/arch/x86/cpu/mcheck/mcaction.c
>> +++ b/xen/arch/x86/cpu/mcheck/mcaction.c
>> @@ -100,7 +100,8 @@ mc_memerr_dhandler(struct mca_binfo *bin
>> goto vmce_failed;
>> }
>>
flight 105990 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105990/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-43 host-install(3)broken REGR. vs. 105847
test-armhf-armh
On Wed, Feb 22, 2017 at 04:35:20PM +, Olaf Hering wrote:
> Signed-off-by: Olaf Hering
Acked-by: Wei Liu
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
On Wed, Feb 22, 2017 at 04:28:45PM +0100, Juergen Gross wrote:
> As 0 is a valid file descriptor testing a descriptor to be valid
> should be done via >= 0 instead of > 0.
>
> Signed-off-by: Juergen Gross
> ---
Acked-by: Wei Liu
Ian, this should be backported.
> tools/xenstore/xenstored_core
In Python3 'int' and 'long' types are the same, there are no longer
separate PyInt_* functions. Provide convenient #defines to limit #if in
code.
Signed-off-by: Marek Marczykowski-Górecki
---
tools/python/xen/lowlevel/xc/xc.c | 51 ---
tools/python/xen/lowlev
In Python3, PyTypeObject looks slightly different, and also module
initialization is different. Instead of Py_InitModule, PyModule_Create
should be called on already defined PyModuleDef structure. And then
initialization function should return that module.
Additionally initialization function shou
Py_TYPE works on both Python2 and Python3, while internals of
PyObject_HEAD have changed.
Signed-off-by: Marek Marczykowski-Górecki
---
tools/python/xen/lowlevel/xc/xc.c | 2 +-
tools/python/xen/lowlevel/xs/xs.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/python/
Fields not named here will be zero-initialized anyway, but using this
way will be much easier to support both Python2 and Python3.
Signed-off-by: Marek Marczykowski-Górecki
---
tools/python/xen/lowlevel/xc/xc.c | 47 ---
tools/python/xen/lowlevel/xs/xs.c | 47
Signed-off-by: Marek Marczykowski-Górecki
---
tools/python/xen/lowlevel/xc/xc.c | 4
tools/python/xen/lowlevel/xs/xs.c | 4
2 files changed, 8 insertions(+)
diff --git a/tools/python/xen/lowlevel/xc/xc.c
b/tools/python/xen/lowlevel/xc/xc.c
index 39be1d5..7fbead5 100644
--- a/tools/pyt
tp_getattr method of type object is deprecated already in Python2 and
gone in Python3. Default implementation does the same as this custom one.
Signed-off-by: Marek Marczykowski-Górecki
---
tools/python/xen/lowlevel/xc/xc.c | 7 +--
tools/python/xen/lowlevel/xs/xs.c | 7 +--
2 files chan
In Python3 'long' type have been merged into 'int', '1L' syntax is no
longer valid. Assign 'int' type to a 'long' variable in python3, so
'long(1)' will give correct result in both python2 and python3.
Signed-off-by: Marek Marczykowski-Górecki
---
tools/python/xen/migration/libxc.py | 32 +++
This patch series add support for Python3 in tools/python. As most python
modules, it looks at $PYTHON variable to what python use, so to use this
PYTHON=python3 needs to be defined in a build environment. If both python2 and
python3 versions are needed, then python bindings needs to be built twice
In Python2 PyBytes is the same as PyString, but in Python3 PyString is
gone and 'str' is really PyUnicode in C-API.
When handling arbitrary data, use PyBytes - which is the right thing to
do in Python3, and pose no API change in Python2. When handling
xenstore paths and transaction ids, which have
On February 23, 2017 5:59 PM, Jan Beulich wrote:
On 23.02.17 at 10:28, wrote:
>> On February 18, 2017 12:33 AM, Jan Beulich wrote:
>> On 17.02.17 at 09:49, wrote:
On Fri, Feb 17, 2017 at 09:37:45AM +, Xuquan (Quan Xu) wrote:
>From a589074281cc22a30ed75a5bccba60e83d2312a6 Mon
>>> On 23.02.17 at 11:53, wrote:
> On February 23, 2017 5:59 PM, Jan Beulich wrote:
> On 23.02.17 at 10:28, wrote:
>>> On February 18, 2017 12:33 AM, Jan Beulich wrote:
>>> On 17.02.17 at 09:49, wrote:
> On Fri, Feb 17, 2017 at 09:37:45AM +, Xuquan (Quan Xu) wrote:
>>From a58
On Wed, Feb 22, 2017 at 04:28:46PM +0100, Juergen Gross wrote:
> In preparation to support other than pure debug functionality via the
> Xenstore XS_DEBUG wire command rename it to XS_CONTROL and make
> XS_DEBUG an alias of it.
>
> Add an alias xs_control_command for the associated xs_debug_comman
On Wed, Feb 22, 2017 at 04:28:51PM +0100, Juergen Gross wrote:
> As a memory report can now be triggered via XS_CONTROL support via
> command line and signal handler is no longer needed. Remove it.
>
> Signed-off-by: Juergen Gross
Acked-by: Wei Liu
_
On Wed, Feb 22, 2017 at 04:28:50PM +0100, Juergen Gross wrote:
> Add a XS_CONTROL command to xenstored for doing a talloc report to a
> file. Right now this is supported by specifying a command line option
> when starting xenstored and sending a signal to the daemon to trigger
> the report.
>
> To
On Wed, Feb 22, 2017 at 04:28:47PM +0100, Juergen Gross wrote:
> Move the XS_CONTROL handling of xenstored to a new source file
> xenstored_control.c.
>
> In order to avoid making get_string() in xenstored_core.c globally
> visible use strlen() instead, which is save in this context due to
> xs_co
On Wed, Feb 22, 2017 at 04:28:48PM +0100, Juergen Gross wrote:
> The Xenstore protocol supports the XS_CONTROL command for triggering
> various actions in the Xenstore daemon. Enhance that support by using
> a command table and adding a help function.
>
> Support multiple control commands in the a
On Wed, Feb 22, 2017 at 04:28:49PM +0100, Juergen Gross wrote:
> Today Xenstore supports logging only if specified at start of the
> Xenstore daemon. As it can't be disabled during runtime it is not
> recommended to start xenstored with logging enabled.
>
> Add support for switching logging on and
flight 105991 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105991/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt 13 saverestore-support-checkfail like 105936
test-amd64-i386-xl-qemuu
On Thu, Feb 23, 2017 at 11:48:20AM +0100, Marek Marczykowski-Górecki wrote:
> This patch series add support for Python3 in tools/python. As most python
> modules, it looks at $PYTHON variable to what python use, so to use this
> PYTHON=python3 needs to be defined in a build environment. If both pyt
On Thu, Feb 16, 2017 at 08:47:07AM +0100, Juergen Gross wrote:
> There have been reports that Fedora 25 uses /run instead of /var/run.
>
> Add a --with-rundir option ito configure to be able to specify that
> directory. Default is still /var/run.
>
> A re-run of autogen.sh is required.
>
> Signe
The base address, id and number of pins of the vIO APICs exposed to PVHv2 Dom0
is the same as the values found on bare metal.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/domain_build.c | 33 +++--
xen/arch/x86/hvm/vioapic.c | 5
And then remove hvm_vioapic (since it just contains a hvm_hw_ioapic struct
now). This is a preparatory change for introducing support for multiple vIO
APICs per domain.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/hvm/vioapic.c| 40 +
So that the function can be called from other files without adding prototypes
to each of them.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
xen/arch/x86/io_apic.c| 2 --
xen/include/asm-x86/io_apic.h | 3 +++
2 files changed, 3 insertions(+), 2 deletions(-)
Hello,
This patch series introduce support for having a variable number of entries in
vIO APICs, and also having a variable number of vIO APICs per domain. This
functionality is not used by unprivileged guests, that are still limited to a
single IO APIC with 49 entries.
The functionality introduc
Add support for multiple vIO APICs on the same domain, thus turning
d->arch.hvm_domain.vioapic into an array of vIO APIC control structures.
Note that this functionality is not exposed to unprivileged guests, and will
only be used by PVHv2 Dom0.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Altough it's still always set to VIOAPIC_NUM_PINS (48).
Add a new field to the hvm_hw_ioapic struct to contain the number of pins
(number of IO redirection table entries), and add the migration compatibility
code.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
Cc: Jan Beulich
On February 23, 2017 7:01 PM, Jan Beulich wrote:
On 23.02.17 at 11:53, wrote:
>> On February 23, 2017 5:59 PM, Jan Beulich wrote:
>> On 23.02.17 at 10:28, wrote:
On February 18, 2017 12:33 AM, Jan Beulich wrote:
On 17.02.17 at 09:49, wrote:
>>>diff --git a/xen/arch/x86
On 23/02/17 09:28, Jan Beulich wrote:
> Storing -1 into both fields was misleading consumers: We really should
> have a manifest constant for "invalid vCPU" here, and the already
> existing DOMID_INVALID should be used.
>
> Also correct a bogus (dead code) check in mca_init_global(), at once
> intr
CC: Paul Durrant
Signed-off-by: Ian Jackson
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index c8d56d1..7182fe8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -99,6 +99,7 @@ tools/libs/evtchn/headers.chk
tools/libs/gnttab/headers.chk
tools/libs/call/h
> -Original Message-
> From: Ian Jackson [mailto:ian.jack...@eu.citrix.com]
> Sent: 23 February 2017 12:10
> To: xen-de...@lists.xensource.com
> Cc: Ian Jackson ; Paul Durrant
> ; Ian Jackson
> Subject: [PATCH] tools/libxendevicemodel: Add headers.chk to .gitignore
>
> CC: Paul Durrant
>
flight 105992 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105992/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 15 guest-start/debian.repeat fail REGR. vs.
105835
Regressions
Wei Liu writes ("[PATCH 0/2] tools: split xl into a separate directory"):
> Xl has grown sufficiently large to warrnant its own directory. We also need
> clear separation between the client (xl) and library (libxl).
This is a fine idea.
Both patches,
Acked-by: Ian Jackson
Thanks,
Ian.
___
On 23/02/17 09:51, Jan Beulich wrote:
On 22.02.17 at 19:20, wrote:
>> flight 105966 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/105966/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> te
>>> On 23.02.17 at 13:02, wrote:
> On 23/02/17 09:28, Jan Beulich wrote:
>> --- a/xen/arch/x86/cpu/mcheck/mcaction.c
>> +++ b/xen/arch/x86/cpu/mcheck/mcaction.c
>> @@ -100,7 +100,8 @@ mc_memerr_dhandler(struct mca_binfo *bin
>> goto vmce_failed;
>> }
>>
>> -
>>> On 23.02.17 at 13:19, wrote:
> On 23/02/17 09:51, Jan Beulich wrote:
> On 22.02.17 at 19:20, wrote:
>>> flight 105966 xen-unstable real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/105966/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> in
Paul Durrant writes ("RE: [PATCH] tools/libxendevicemodel: Add headers.chk to
.gitignore"):
> Oops, yes, I missed that.
>
> Reviewed-by: Paul Durrant
Thanks.
I have put it all together and pushed the qemu-trad and xen.git parts
to the appropriate places. Please let me know if I have messed up
>>> On 23.02.17 at 12:55, wrote:
> On February 23, 2017 7:01 PM, Jan Beulich wrote:
> On 23.02.17 at 11:53, wrote:
>>> IOW,
>>> which vcpu does the 'current' refer to?
>>> which cpu does the ' smp_processor_id()' refer to?
>>
>>current: currently running vCPU
>
> in a SMP machine, are ther
> -Original Message-
> From: Ian Jackson [mailto:ian.jack...@eu.citrix.com]
> Sent: 23 February 2017 12:25
> To: Paul Durrant
> Cc: xen-de...@lists.xensource.com
> Subject: RE: [PATCH] tools/libxendevicemodel: Add headers.chk to .gitignore
>
> Paul Durrant writes ("RE: [PATCH] tools/libxe
On 23/02/17 12:21, Jan Beulich wrote:
On 23.02.17 at 13:02, wrote:
>> On 23/02/17 09:28, Jan Beulich wrote:
>>> --- a/xen/arch/x86/cpu/mcheck/mcaction.c
>>> +++ b/xen/arch/x86/cpu/mcheck/mcaction.c
>>> @@ -100,7 +100,8 @@ mc_memerr_dhandler(struct mca_binfo *bin
>>> goto
Thanks paul and anshul
Can you guys point out source code which is audit the GPU command?
Thanks
Bharat
On Mon, Feb 20, 2017 at 9:01 PM, Paul Durrant
wrote:
> No, that’s not correct. The GPU commands are whitelisted and only the
> commands that can be audited are handled.
>
>
>
> Paul
>
>
>
Hi,
I’m not actually sure where the latest public release of the xengt code is.
Perhaps someone from Intel can comment?
Otherwise, if you grab the source ISOs from xenserver.org you can look in the
SRPM for xengt. The xengt kernel module is responsible for auditing the
servicing the GPU co
On 23/02/17 12:24, Jan Beulich wrote:
On 23.02.17 at 13:19, wrote:
>> On 23/02/17 09:51, Jan Beulich wrote:
>> On 22.02.17 at 19:20, wrote:
flight 105966 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105966/
Regressions :-(
Tests
>>> On 23.02.17 at 13:38, wrote:
> On 23/02/17 12:24, Jan Beulich wrote:
> On 23.02.17 at 13:19, wrote:
>>> On 23/02/17 09:51, Jan Beulich wrote:
>>> On 22.02.17 at 19:20, wrote:
> flight 105966 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/105966/
flight 106016 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106016/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64 5 xen
On 23/02/17 08:00, Haozhong Zhang wrote:
> On 02/22/17 00:46 -0700, Jan Beulich wrote:
> On 22.02.17 at 03:20, wrote:
>>> On 02/22/17 09:28 +0800, Haozhong Zhang wrote:
On 02/21/17 02:15 -0700, Jan Beulich wrote:
On 21.02.17 at 03:11, wrote:
>>> [..]
>> + *
>> +
Hi,
Currently, xenconsoled supports only PV console. To support one
additional pl011 console, some of the data structures in struct domain
and certain functions such as buffer_append, ring_free_bytes, etc.
will have to be be scaled to support now two types of consoles.
Some changes are required i
On Thu, Feb 23, 2017 at 12:17:38PM +, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 0/2] tools: split xl into a separate directory"):
> > Xl has grown sufficiently large to warrnant its own directory. We also need
> > clear separation between the client (xl) and library (libxl).
>
> This is a f
On 02/23/2017 05:05 AM, Jan Beulich wrote:
On 23.02.17 at 11:01, wrote:
>> On 02/23/17 02:28 -0700, Jan Beulich wrote:
>>> --- a/xen/arch/x86/cpu/mcheck/mcaction.c
>>> +++ b/xen/arch/x86/cpu/mcheck/mcaction.c
>>> @@ -100,7 +100,8 @@ mc_memerr_dhandler(struct mca_binfo *bin
>>>
>>> On 22.02.17 at 15:24, wrote:
> Craft the Dom0 e820 memory map and populate it. Introduce a helper to remove
> memory pages that are shared between Xen and a domain, and use it in order to
> remove low 1MB RAM regions from dom_io in order to assign them to a PVHv2
> Dom0.
>
> On hardware lack
>>> On 22.02.17 at 15:24, wrote:
> This allows to also change the types of image_base and image_start in the Dom0
> builder from char * to void *.
>
> Signed-off-by: Roger Pau Monné
Reviewed-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@list
>>> On 22.02.17 at 15:24, wrote:
> Allow setting the destination vCPU for libelf, so that elf_load_image can take
> it into account when loading the kernel for Dom0. This is needed for PVHv2
> Dom0
> build, so that hvm_copy_to_guest_phys can be called with a Dom0 vCPU instead
> of
> current (tha
>>> On 22.02.17 at 15:24, wrote:
> Introduce a helper to parse the Dom0 kernel.
>
> A new helper is also introduced to libelf, that's used to store the
> destination
> vcpu of the domain. This parameter is needed when loading the kernel on a HVM
> domain (PVHv2), since hvm_copy_to_guest_phys req
Hi,
On 23/02/17 07:39, Jan Beulich wrote:
On 22.02.17 at 21:29, wrote:
Please don't top-post.
Appreciate the feedback. I want to use these defines for parsing out SMMUv3
components defined in ACPI. Since, I am picking these defines directly from
Linux, I did not want to make this a part of
This patch modifies the wrapper functions in xen_common.h to use the
new xendevicemodel interface if it is available along with compatibility
code to use the old libxenctrl interface if it is not.
Signed-off-by: Paul Durrant
---
Cc: Stefano Stabellini
Cc: Anthony Perard
---
include/hw/xen/xen_
My recent patches to Xen [1] introduced a new library to support
running device models for HVM guests.
This series ports QEMU onto the new library if it is available in the
build environment.
Paul Durrant (5):
xen: make use of xen_xc implicit in xen_common.h inlines
xen: rename xen_modified_me
This patch creates inline wrapper functions in xen_common.h for all open
coded calls to xc_hvm_XXX() functions outside of xen_common.h so that use
of xen_xc can be made implicit. This again is in preparation for the move
to using libxendevicemodel.
Signed-off-by: Paul Durrant
---
Cc: Stefano Stab
This patch adds code in configure to set CONFIG_XEN_CTRL_INTERFACE_VERSION
to a new value of 490 if libxendevicemodel is present in the build
environment.
Signed-off-by: Paul Durrant
---
Cc: Stefano Stabellini
Cc: Anthony Perard
---
configure | 19 +++
1 file changed, 19 insert
This patch is a purely cosmetic change that avoids a name collision in
a subsequent patch.
Signed-off-by: Paul Durrant
---
Cc: Paolo Bonzini
Cc: Stefano Stabellini
Cc: Anthony Perard
---
include/exec/ram_addr.h | 4 ++--
include/hw/xen/xen.h| 2 +-
xen-hvm-stub.c | 2 +-
xen-hvm.
Doing this will make the transition to using the new libxendevicemodel
interface less intrusive on the callers of these functions, since using
the new library will require a change of handle.
NOTE: The patch also moves the 'externs' for xen_xc and xen_fmem from
xen_backend.h to xen_common.h,
On Thu, Feb 23, 2017 at 01:20:25PM +, Wei Liu wrote:
> On Thu, Feb 23, 2017 at 12:17:38PM +, Ian Jackson wrote:
> > Wei Liu writes ("[PATCH 0/2] tools: split xl into a separate directory"):
> > > Xl has grown sufficiently large to warrnant its own directory. We also
> > > need
> > > clear
> -Original Message-
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: 23 February 2017 14:54
> To: xen-de...@lists.xenproject.org; qemu-de...@nongnu.org
> Cc: Paul Durrant
> Subject: [PATCH 0/5] xen: use new xendevicemodel library
>
> My recent patches to Xen [1] introduced a
>>> On 23.02.17 at 14:59, wrote:
> On 23/02/17 07:39, Jan Beulich wrote:
> On 22.02.17 at 21:29, wrote:
>>> Appreciate the feedback. I want to use these defines for parsing out SMMUv3
>>> components defined in ACPI. Since, I am picking these defines directly from
>>> Linux, I did not want to
On Thu, Feb 23, 2017 at 06:45:50PM +0530, Bhupinder Thakur wrote:
> Hi,
>
> Currently, xenconsoled supports only PV console. To support one
> additional pl011 console, some of the data structures in struct domain
> and certain functions such as buffer_append, ring_free_bytes, etc.
> will have to b
Hi Jan,
On 23/02/17 15:02, Jan Beulich wrote:
On 23.02.17 at 14:59, wrote:
On 23/02/17 07:39, Jan Beulich wrote:
On 22.02.17 at 21:29, wrote:
Appreciate the feedback. I want to use these defines for parsing out SMMUv3
components defined in ACPI. Since, I am picking these defines directly fr
On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches wrote:
> There are ~4300 uses of pr_warn and ~250 uses of the older
> pr_warning in the kernel source tree.
>
> Make the use of pr_warn consistent across all kernel files.
>
> This excludes all files in tools/ as there is a separate
> define pr_warning
To avoid freeing uninitialised buffer when taking the first error exit
path.
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
Cc: Paul Durrant
---
tools/libs/devicemodel/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/libs/devicemodel/core.c b/tools/libs/devicemodel/
1 - 100 of 164 matches
Mail list logo
