>>> Wei Liu 06/28/17 4:18 PM >>>
>@@ -577,7 +577,7 @@ static void plt_overflow(void *unused)
>}
>if ( i != 0 )
>{
>-static bool_t warned_once;
>+static bool warned_once;
>if ( !test_and_set_bool(warned_once) )
Again, please also add the missing newline here
On 06/28/2017 06:31 PM, Vitaly Kuznetsov wrote:
Konrad Rzeszutek Wilk writes:
On Mon, Jun 26, 2017 at 06:39:30PM +0200, Vitaly Kuznetsov wrote:
CONFIG_BOOTPARAM_HOTPLUG_CPU0 allows to offline CPU0 but Xen HVM guests
BUG() in xen_teardown_timer(). Remove the BUG_ON(), this is probably a
leftov
>>> Andrew Cooper 06/28/17 4:17 PM >>>
>FEATURE_CONTROL is already read with LOCK bit set (so is unmodifiable), and
>all VMX MSRs are read-only. Also, fix the MSR_IA32_VMX_TRUE_ENTRY_CTLS bound
>to be MSR_IA32_VMX_VMFUNC, rather than having the intervening MSRs falling
>into the default case.
>
>
On 17-06-29 00:24:50, Jan Beulich wrote:
> >>> Yi Sun 06/29/17 7:12 AM >>>
> >On 17-06-28 05:43:58, Jan Beulich wrote:
> >> >>> Yi Sun 06/28/17 11:10 AM >>>
> >> >On 17-06-28 01:14:59, Jan Beulich wrote:
> >> >> >>> Yi Sun 06/14/17 3:25 AM >>>
> >> >> > @@ -537,7 +556,16 @@ int psr_get_val(struc
On Thu, Jun 08, 2017 at 02:08:54PM +0200, Dario Faggioli wrote:
> As cap is already present in Credit1, as a parameter, all
> the wiring is there already for it to be percolate down
s/be //
> to csched2_dom_cntl() too.
Alan
___
Xen-devel mailing list
Hi Oleksandr,
On Fri, Jun 23, 2017 at 09:09:55AM +0300, Oleksandr Andrushchenko wrote:
> + switch (event->mtouch.event_type) {
> + case XENKBD_MT_EV_DOWN:
> + input_mt_report_slot_state(dev, MT_TOOL_FINGER,
> +
flight 71614 distros-debian-wheezy real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71614/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
build-arm64 2 hosts-allocate broken never pass
build-arm64-pvops
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 28 June 2017 19:37
> To: xen-de...@lists.xenproject.org; qemu-de...@nongnu.org
> Cc: sstabell...@kernel.org; peter.mayd...@linaro.org; Anthony Perard
> ; kra...@redhat.com; Paul Durrant
>
> Subject: [PA
On Thu, Jun 29, 2017 at 12:19:39AM -0600, Jan Beulich wrote:
> >>> Roger Pau Monne 06/28/17 5:37 PM >>>
> >On Mon, May 29, 2017 at 07:29:29AM -0600, Jan Beulich wrote:
> >> >>> On 27.04.17 at 16:35, wrote:
> >> > +switch ( offset )
> >> > +{
> >> > +case PCI_MSIX_ENTRY_LOWER_ADDR_OFFS
On 29/06/17 08:39, Alan Robinson wrote:
> On Thu, Jun 08, 2017 at 02:08:54PM +0200, Dario Faggioli wrote:
>> As cap is already present in Credit1, as a parameter, all
>> the wiring is there already for it to be percolate down
>
> s/be //
or "to be percolated down"
-G
__
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 28 June 2017 19:20
> To: Peter Maydell
> Cc: Stefano Stabellini ; QEMU Developers de...@nongnu.org>; Anthony Perard ; Gerd
> Hoffmann ; Paul Durrant ;
> xen-de...@lists.xenproject.org
> Subject: Re: Ge
flight 67 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/67/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-1 59 leak-check/check fail REGR. vs. 111074
test-xtf-amd64-amd64-4
Hi Wei,
On 28 June 2017 at 22:47, Wei Liu wrote:
> On Thu, Jun 22, 2017 at 01:08:50PM +0530, Bhupinder Thakur wrote:
> [...]
>> static struct termios stdin_old_attr;
>> @@ -343,6 +344,7 @@ int main(int argc, char **argv)
>> char *end;
>> console_type type = CONSOLE_INVAL;
>> bo
On Wed, 2017-06-28 at 20:05 +0100, George Dunlap wrote:
> On Wed, Jun 28, 2017 at 3:56 PM, Dario Faggioli
> wrote:
> >
> > In the case you describe, at 2T, with budget -C, the first round of
> > the
> > loop will make the budget 0, and set the next replenishment to 3T.
> > As
> > you say, since b
On Thu, Jun 29, 2017 at 03:03:45PM +0530, Bhupinder Thakur wrote:
> Hi Wei,
>
> On 28 June 2017 at 22:47, Wei Liu wrote:
> > On Thu, Jun 22, 2017 at 01:08:50PM +0530, Bhupinder Thakur wrote:
> > [...]
> >> static struct termios stdin_old_attr;
> >> @@ -343,6 +344,7 @@ int main(int argc, char **a
flight 48 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/48/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs.
110515
test-amd64-a
On Wed, 2017-06-28 at 16:19 +0100, George Dunlap wrote:
> On Thu, Jun 8, 2017 at 1:08 PM, Dario Faggioli
> wrote:
> >
> > +/*
> > + * We are disabling the cap for this domain, which may
> > have vCPUs
> > + * waiting for a replenishment, and we need to unpark
>
On Wed, 2017-06-28 at 19:43 +0100, George Dunlap wrote:
> On Thu, Jun 8, 2017 at 1:09 PM, Dario Faggioli
> wrote:
> > Note that a cap is considered valid only if
> > it is within the [1, nr_vcpus]% interval.
>
> Oh, I see you added the check here.
>
Yeah...
> Still, I think we should add a chec
On Thu, Jun 29, 2017 at 12:53:21AM -0600, Jan Beulich wrote:
> >>> Andrew Cooper 06/28/17 4:30 PM >>>
> >On 28/06/17 15:18, Wei Liu wrote:
> >> --- a/xen/arch/x86/irq.c
> >> +++ b/xen/arch/x86/irq.c
> >> @@ -29,7 +29,7 @@
> >> static void parse_irq_vector_map_param(char *s);
> >>
> >> /* opt_n
From: Chao Gao
According to SDM 10.11.1, only [19:12] bits of MSI address are
Destination ID, change the mask to avoid ambiguity for VT-d spec
has used the bit 4 to indicate a remappable interrupt request.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
include/hw/i386/apic-msidef.h | 2
This patchset is to deal with MSI interrupt remapping request when guest
updates MSI registers.
Chao Gao (3):
i386/msi: Correct mask of destination ID in MSI address
xen-pt: bind/unbind interrupt remapping format MSI
msi: Handle remappable format interrupt request
configure
From: Chao Gao
If a vIOMMU is exposed to guest, guest will configure the msi to remapping
format. The original code isn't suitable to the new format. A new pair
bind/unbind interfaces are added for this usage. This patch recognizes
this case and uses new interfaces to bind/unbind msi.
Signed-off
From: Chao Gao
According to VT-d spec Interrupt Remapping and Interrupt Posting ->
Interrupt Remapping -> Interrupt Request Formats On Intel 64
Platforms, fields of MSI data register have changed. This patch
avoids wrongly regarding a remappable format interrupt request as
an interrupt binded wit
Change since RFC v2:
1) Move vvtd.c to drivers/passthrough/vtd directroy.
2) Make vIOMMU always built in on x86
3) Add new boot cmd "viommu" to enable viommu function
4) Fix some code stype issues.
Change since RFC v1:
1) Add Xen virtual IOMMU doc docs/misc/viom
This patch is to add get_irq_info callback for platform implementation
to convert irq remapping request to irq info (E,G vector, dest, dest_mode
and so on).
Signed-off-by: Lan Tianyu
---
xen/common/viommu.c | 16
xen/include/asm-x86/viommu.h | 8
xen/include/x
This patch is to add Xen virtual IOMMU doc to introduce motivation,
framework, vIOMMU hypercall and xl configuration.
Signed-off-by: Lan Tianyu
---
docs/misc/viommu.txt | 129 +++
1 file changed, 129 insertions(+)
create mode 100644 docs/misc/viom
This patch is to introduct an abstract layer for arch vIOMMU implementation
to deal with requests from dom0. Arch vIOMMU code needs to provide callback
to perform create, destroy and query capabilities operation.
Signed-off-by: Lan Tianyu
---
xen/arch/x86/setup.c| 1 +
xen/common/Kconf
From: Chao Gao
The BIOS reports the remapping hardware units in a platform to system software
through the DMA Remapping Reporting (DMAR) ACPI table.
To build DMAR table during domain construction, two fields are added to struct
acpi_config. One is dmar_flag which indicates whether interrupt rema
From: Chao Gao
a field, viommu_info, is added to struct libxl_domain_build_info. Several
attributes can be specified by guest configuration file for the DMAR table
building and vIOMMU creation.
In domain creation process, a new logic is added to build ACPI DMAR table in
tool stack according VM c
From: Chao Gao
This patch adds create/destroy/query function for the emulated VTD
and adapts it to the common VIOMMU abstraction.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
xen/drivers/passthrough/vtd/Makefile | 7 +-
xen/drivers/passthrough/vtd/iommu.h | 99 +--
This patch is to introduce create, destroy and query capabilities
command for vIOMMU. vIOMMU layer will deal with requests and call
arch vIOMMU ops.
Signed-off-by: Lan Tianyu
---
xen/common/domctl.c | 3 +++
xen/common/viommu.c | 43 +++
x
This patch is to add irq request callback for platform implementation
to deal with irq remapping request.
Signed-off-by: Lan Tianyu
---
xen/common/viommu.c | 15 +
xen/include/asm-x86/viommu.h | 73
xen/include/xen/viommu.h | 9 +
From: Chao Gao
This patch is to add XEN_DOMCTL_viommu_op hypercall. This hypercall
comprise three sub-command:
- query capabilities of one specific type vIOMMU emulated by Xen
- create vIOMMU in Xen hypervisor with viommu type, register range,
capability
- destroy vIOMMU specified by viommu_i
From: Chao Gao
When irq remapping is enabled, IOAPIC Redirection Entry may be in remapping
format. If that, generate an irq_remapping_request and call the common
VIOMMU abstraction's callback to handle this interrupt request. Device
model is responsible for checking the request's validity.
Signe
From: Chao Gao
In two situations, hypervisor delivers a msi to a hvm guest. One is
when qemu sends a request to hypervisor through XEN_DMOP_inject_msi.
The other is when a physical interrupt arrives and it has been bound
to a guest msi.
For the former, the msi is routed to common vIOMMU layer if
From: Chao Gao
Software writes this field to enable/disable interrupt reampping. This patch
emulate IRES field of GCMD.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
xen/drivers/passthrough/vtd/iommu.h | 3 ++-
xen/drivers/passthrough/vtd/vvtd.c | 27 +++
2 f
From: Chao Gao
This patch adds VVTD MMIO handler to deal with MMIO access.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
xen/drivers/passthrough/vtd/vvtd.c | 114 +
1 file changed, 114 insertions(+)
diff --git a/xen/drivers/passthrough/vtd/vvtd.c
From: Chao Gao
Previously, interrupt attributes can be extracted from msi message or
IOAPIC RTE. However, with interrupt remapping enabled, the attributes
are enclosed in the associated IRTE. This callback is for cases in
which the caller wants to acquire interrupt attributes.
Signed-off-by: Cha
From: Chao Gao
If guest is configured to have a vIOMMU, create it during domain construction.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
tools/libxl/libxl_arch.h | 5 +
tools/libxl/libxl_arm.c| 7 +++
tools/libxl/libxl_create.c | 6 ++
tools/libxl/libxl_x86.c
From: Chao Gao
Interrupt translation faults are non-recoverable fault. When faults
are triggered, it needs to populate fault info to Fault Recording
Registers and inject vIOMMU msi interrupt to notify guest IOMMU driver
to deal with faults.
This patch emulates hardware's handling interrupt trans
From: Chao Gao
No functional change. It is a preparation for introducing new fields in
hvm_gmsi_info to manage remapping format msi bound to a physical msi.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
xen/arch/x86/hvm/vmsi.c | 4 ++--
xen/drivers/passthrough/io.c | 32
From: Chao Gao
Software writes to QIE fields of GCMD to enable or disable queued
invalidations. This patch emulates QIE fields of GCMD.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
xen/drivers/passthrough/vtd/iommu.h | 3 ++-
xen/drivers/passthrough/vtd/vvtd.c | 22
From: Chao Gao
Software sets this field to set/update the interrupt remapping table pointer
used by hardware. The interrupt remapping table pointer is specified through
the Interrupt Remapping Table Address (IRTA_REG) register.
This patch emulates this operation and adds some new fields in VVTD
From: Chao Gao
When a remapping interrupt request arrives, remapping hardware computes the
interrupt_index per the algorithm described in VTD spec
"Interrupt Remapping Table", interprets the IRTE and generates a remapped
interrupt request.
This patch introduces viommu_handle_irq_request() to emu
From: Chao Gao
When IOAPIC RTE is in remapping format, it doesn't contain the vector of
interrupt. This patch adds vioapic_pin_vector() to get vector from pin
for both remapping format and legacy format and uses this function other
than accessing IOAPIC RTE directly.
Signed-off-by: Chao Gao
Sig
From: Chao Gao
Add dmar table structure according Chapter 8 "BIOS Considerations" of
VTd spec Rev. 2.4.
VTd
spec:http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/vt-directed-io-spec.pdf
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
tools/libacpi/acp
From: Chao Gao
Wrap some useful status in a new structure hvm_hw_vvtd, following
the customs of vlapic, vioapic and etc. Provide two save-restore
pairs to save/restore registers and non-register status.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
xen/drivers/passthrough/vtd/vvtd.c
From: Chao Gao
Introduce a new binding relationship and provide a new interface to
manage the new relationship.
Signed-off-by: Chao Gao
Signed-off-by: Lan Tianyu
---
tools/libxc/include/xenctrl.h | 17 ++
tools/libxc/xc_domain.c | 53 +
xen/drivers/passthrough/io.c
From: Chao Gao
Queued Invalidation Interface is an expanded invalidation interface with
extended capabilities. Hardware implementations report support for queued
invalidation interface through the Extended Capability Register. The queued
invalidation interface uses an Invalidation Queue (IQ), whi
On Fri, Jun 23, 2017 at 03:42:20AM -0400, Bruno Alvisio wrote:
> This patch is the first attempt on adding live migration of instances with
> local
> storage to Xen. This patch just handles very restricted case of fully
> virtualized HVMs. The code uses the "drive-mirror" capability provided by
>
On 27 June 2017 at 23:04, Stefano Stabellini wrote:
> The following changes since commit 577caa2672ccde7352fda3ef17e44993de862f0e:
>
> Merge remote-tracking branch
> 'remotes/edgar/tags/edgar/mmio-exec-v2.for-upstream' into staging (2017-06-27
> 16:56:55 +0100)
>
> are available in the git rep
flight 72 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/72/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 8cf19dc7a5305007bd33934838c67a7b1640f633
baseline version:
ovmf 1fb805b1eb5b6039cb123
In the null scheduler, we don't need either hard or soft affinity during online
scheduling operations. In fact, the vCPUs are statically assigned to the
pCPUs, and hence there's no scope for checking or enforcing any affinity.
We, however, use hard-affinity for 'placement', i.e., for deciding to
Whether or not there's pending tasklet work to do, it's
something we know from the tasklet_work_scheduled parameter.
Deal with that as soon as possible, like all other schedulers
do.
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
---
xen/common/sched_null.c |9 +
1 file change
The null scheduler does not really use hard-affinity for
scheduling, it uses it for 'placement', i.e., for deciding
to what pCPU to statically assign a vCPU.
Let's use soft-affinity in the same way, of course with the
difference that, if there's no free pCPU within the vCPU's
soft-affinity, we go
In fact, we want to be able to use them from any scheduler.
While there, make the moved code use 'v' for struct_vcpu*
variable, like it should be done everywhere.
No functional change intended.
Signed-off-by: Dario Faggioli
Signed-off-by: Justin T. Weaver
Reviewed-by: George Dunlap
---
Cc: An
In line with what is there in all the other schedulers.
Signed-off-by: Dario Faggioli
---
George Dunlap
---
xen/common/sched_null.c| 94 +++-
xen/include/public/trace.h |1
2 files changed, 92 insertions(+), 3 deletions(-)
diff --git a/xen/com
In both xentrace and xenalyze.
Signed-off-by: Dario Faggioli
---
George Dunlap
---
tools/xentrace/formats|7 +
tools/xentrace/xenalyze.c | 65 +
2 files changed, 72 insertions(+)
diff --git a/tools/xentrace/formats b/tools/xentrace/form
On Mon, Jun 26, 2017 at 05:16:22PM +0800, Haozhong Zhang wrote:
> If LMCE is supported by host and ' mca_caps = [ "lmce" ] ' is present
> in xl config, the LMCE capability will be exposed in guest MSR_IA32_MCG_CAP.
> By default, LMCE is not exposed to guest so as to keep the backwards migration
> c
Reference: https://xenproject.atlassian.net/browse/XEN-90
If you create a Xen patch for livepatch that adds additional files to the
build (adds the files and patches the Makefile to include them), the
livepatch tools (from https://github.com/rosslagerwall/livepatch-build-tools)
do not properly han
On 29/06/17 09:54, osstest service owner wrote:
> flight 67 xtf real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/67/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-xtf-amd64-amd64-1 59 leak-check/ch
> Anthony Perard did a great job providing patches which add a partial
> Q35
> support. I tried extending his patches to include missing features for
> Q35 in
> hvmloader, libacpi and QEMU and so far the Xen+Q35 experience is quite
> positive
Hi Alexey,
I saw Anthony's patch, but your extension
Thanks Wei. Currently it is started after the memory is streamed from
source to destination (for migration) and the booting functions are
completed.I was going to ask to the list if there is a specific reason the
QEMU process needs to be started at that point.
Also, if the start point of the QEMU
On Thu, Jun 29, 2017 at 09:33:07AM -0400, Bruno Alvisio wrote:
> Thanks Wei. Currently it is started after the memory is streamed from
> source to destination (for migration) and the booting functions are
> completed.I was going to ask to the list if there is a specific reason the
> QEMU process ne
flight 55 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/55/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-examine 4 host-install broken REGR. vs. 110441
build-armhf-pvops
flight 87 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87/
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
test-amd64-amd64-libvirt 13 mig
flight 80 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/80/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-1 59 leak-check/check fail REGR. vs. 111074
test-xtf-amd64-amd64-4
Hi,
On 06/29/2017 07:47 AM, Jan Beulich wrote:
Ross Lagerwall 06/28/17 6:14 PM >>>
--- a/xen/common/Kconfig
+++ b/xen/common/Kconfig
@@ -226,7 +226,7 @@ config CRYPTO
>bool
>
>config LIVEPATCH
- bool "Live patching support (TECH PREVIEW)"
+ bool "Live patching support
On Thu, Jun 29, 2017 at 02:56:55PM +0100, Wei Liu wrote:
> On Thu, Jun 29, 2017 at 09:33:07AM -0400, Bruno Alvisio wrote:
> > Thanks Wei. Currently it is started after the memory is streamed from
> > source to destination (for migration) and the booting functions are
> > completed.I was going to as
This run is configured for baseline tests only.
flight 71615 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71615/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-insta
Hi Julien,
My thoughts are that while it is not essential to recover from AER and DPC
initially, it is critical to at least take the slot offline and notify drivers
so they quiesce.
Without this basic handling, it is possible to create backups in some hardware
that result in CPU hangs for loads
On 2017-06-20 12:56:34 +0100, Wei Liu wrote:
> On Wed, Jun 07, 2017 at 02:24:32PM -0500, Venu Busireddy wrote:
> >
> > Hi,
> >
> > I am working on creating a patch to aid in containing the unrecoverable
> > AER errors generated by PCI devices assigned to guests in passthrough
> > mode.
> >
> > T
On Thu, Jun 29, 2017 at 11:21:53AM +0800, Chao Gao wrote:
> The problem is for a VF of RC integrated PF (e.g. PF's BDF is 00:02.0),
> we would wrongly use 00:00.0 to search VT-d unit.
>
> From SRIOV spec REV 1.0 section 3.7.3, it says:
> "ARI is not applicable to Root Complex integrated Endpoints;
>>> Julien Grall 06/29/17 4:31 PM >>>
>On 06/29/2017 07:47 AM, Jan Beulich wrote:
> Ross Lagerwall 06/28/17 6:14 PM >>>
>>> --- a/xen/common/Kconfig
>>> +++ b/xen/common/Kconfig
>>> @@ -226,7 +226,7 @@ config CRYPTO
>> >bool
>> >
>> >config LIVEPATCH
>>> - bool "Live patching suppo
On Thu, Jun 29, 2017 at 03:34:37PM +0100, Roger Pau Monné wrote:
> On Thu, Jun 29, 2017 at 02:56:55PM +0100, Wei Liu wrote:
> > On Thu, Jun 29, 2017 at 09:33:07AM -0400, Bruno Alvisio wrote:
> > > Thanks Wei. Currently it is started after the memory is streamed from
> > > source to destination (for
Hi,
On 06/27/2017 10:47 AM, Julien Grall wrote:
On 27/06/2017 10:46, Tim Deegan wrote:
At 10:33 +0100 on 27 Jun (1498559600), Julien Grall wrote:
The current implementation of {G,M}FN_INVALID cannot be used to
initialize global variable because the initializer element is not a
constant.
Due
On 29/06/17 17:30, Julien Grall wrote:
> Hi,
>
> On 06/27/2017 10:47 AM, Julien Grall wrote:
>>
>>
>> On 27/06/2017 10:46, Tim Deegan wrote:
>>> At 10:33 +0100 on 27 Jun (1498559600), Julien Grall wrote:
The current implementation of {G,M}FN_INVALID cannot be used to
initialize global var
flight 62 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs.
31
Regressi
On Tue, Jun 27, 2017 at 01:03:20PM +0300, Oleksandr Grytsov wrote:
> From: Oleksandr Grytsov
>
> Add libxl__device_add functio.
function
> Almost all devices have similar libxl__device__add function.
> This generic function implements same functionality but
> using the device handling frame
On Tue, Jun 27, 2017 at 01:03:19PM +0300, Oleksandr Grytsov wrote:
> From: Oleksandr Grytsov
>
> Add libxl__device_list, libxl__device_list_free.
> Device list is created from libxl xen store entries.
> In order to fill libxl device structure from xen store,
> the device handling framework extend
On Tue, Jun 27, 2017 at 01:03:27PM +0300, Oleksandr Grytsov wrote:
> From: Oleksandr Grytsov
>
> Signed-off-by: Oleksandr Grytsov
> ---
> docs/man/xl.cfg.pod.5.in | 54
>
> docs/man/xl.pod.1.in | 42 +
> 2
On Tue, Jun 27, 2017 at 01:03:17PM +0300, Oleksandr Grytsov wrote:
> From: Oleksandr Grytsov
>
> Add libxl_device_vdispl and libxl_vdisplinfo to libxl_types.idl
> Add VDISPL to libxl__device_kind enumerator
>
> Signed-off-by: Oleksandr Grytsov
> ---
> tools/libxl/libxl_types.idl | 38
Can you push this series to a git tree? It would be easier for me to
check your changes to the device framework. The device specific handlers
mostly look OK to me.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Hi all, (proposers CC'ed)
I added several new design sessions today: people on the CC list may want to
propose different time-slots
*
https://xendeveloperanddesignsummit2017.sched.com/event/AjEI/design-session-the-missing-toolstack-side-of-pvh-domu
*
https://xendeveloperanddesignsummit2017.sch
On Tue, Jun 27, 2017 at 12:14:55PM -0500, Venu Busireddy wrote:
> libxc: Add wrappers for new commands
Extraneous line here.
>
> Add wrappers for the newly introduced commands "pci-assignable-hide",
> "pci-assignable-unhide", and "pci-assignable-list-hidden".
>
> Signed-off-by: Venu Busireddy
>>> Yi Sun 06/14/17 3:25 AM >>>
> @@ -592,7 +615,14 @@ int psr_get_val(struct domain *d, unsigned int socket,
> /* Set value functions */
> static unsigned int get_cos_num(const struct psr_socket_info *info)
> {
> -return 0;
> +unsigned int num = 0, i;
> +
> +/* Get all features tot
>>> Yi Sun 06/14/17 3:25 AM >>>
> static int find_cos(const uint32_t val[], unsigned int array_len,
> enum psr_feat_type feat_type,
> const struct psr_socket_info *info)
> {
> +unsigned int cos, cos_max;
> +const unsigned int *ref = info->cos_ref
>>> Yi Sun 06/14/17 3:25 AM >>>
> --- a/xen/arch/x86/psr.c
> +++ b/xen/arch/x86/psr.c
> @@ -845,12 +845,97 @@ static int find_cos(const uint32_t val[], unsigned int
> array_len,
> return -ENOENT;
> }
>
> +static bool fits_cos_max(const uint32_t val[],
> + uint32_t
>>> Yi Sun 06/14/17 3:25 AM >>>
> +struct cos_write_info
> +{
> +unsigned int cos;
> +struct feat_node *feature;
> +uint32_t *val;
const?
> static int write_psr_msrs(unsigned int socket, unsigned int cos,
>uint32_t val[], unsigned int array_len,
>
Hi, Dmitry!
First of all thank you for both the comments and the patch
On 06/29/2017 11:17 AM, Dmitry Torokhov wrote:
Hi Oleksandr,
On Fri, Jun 23, 2017 at 09:09:55AM +0300, Oleksandr Andrushchenko wrote:
+ switch (event->mtouch.event_type) {
+ case
Hello all,
Thank you all for the call.
As was agreed, I'll to provide some details on our use cases. I want
to tell you about four cases: one is OP-TEE related, while other three
shows various aspects of virtualized coprocesssors workflow.
1. OP-TEE use case: DRM playback (secure data path).
Us
On June 29, 2017 11:40:30 AM PDT, Oleksandr Andrushchenko
wrote:
>Hi, Dmitry!
>
>First of all thank you for both the comments and the patch
>
>On 06/29/2017 11:17 AM, Dmitry Torokhov wrote:
>> Hi Oleksandr,
>>
>> On Fri, Jun 23, 2017 at 09:09:55AM +0300, Oleksandr Andrushchenko
>wrote:
>>> +
flight 89 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/89/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 03a5572bed61a5e0af83d634962c869f89730d75
baseline version:
ovmf 8cf19dc7a5305007bd339
Hi,
> I saw Anthony's patch, but your extension patch seems still in
> development. Do you have plan to upstream it? I'm also interested in
> this basically I want full PCI-e passthru capability (Current Xen does
> support passthru a PCI-e device but guest can't see configuration offset
> 256-4095
On Fri, 30 Jun 2017, Alexey G wrote:
> Hi,
>
> > I saw Anthony's patch, but your extension patch seems still in
> > development. Do you have plan to upstream it? I'm also interested in
> > this basically I want full PCI-e passthru capability (Current Xen does
> > support passthru a PCI-e device bu
On Thu, 2017-06-29 at 22:04 +0300, Volodymyr Babchuk wrote:
> Hello all,
>
Hello,
> 1. OP-TEE use case: DRM playback (secure data path).
>
> User wants to play a DRM-protected media file. Rights holders don't
> want to give user any means to get DRM-free copy of that media file.
> If you ever he
flight 68 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/68/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs.
110465
test-amd64-
This run is configured for baseline tests only.
flight 71616 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71616/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-i386-libvirt5 libvirt-buildfai
Hello Dario,
On 30 June 2017 at 00:26, Dario Faggioli wrote:
> On Thu, 2017-06-29 at 22:04 +0300, Volodymyr Babchuk wrote:
>> Hello all,
>>
> Hello,
>
>> 1. OP-TEE use case: DRM playback (secure data path).
>>
>> User wants to play a DRM-protected media file. Rights holders don't
>> want to give
flight 93 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-1 59 leak-check/check fail REGR. vs. 111074
test-xtf-amd64-amd64-3
1 - 100 of 124 matches
Mail list logo
