Thanks Wang
I will keep eye on XenGT release for those code.
Regards,
Bharat
On Fri, Feb 24, 2017 at 7:55 AM, Wang, Hongbo wrote:
> Intel XenGT has another maillist " igv...@lists.01.org" to discuss Intel
> GPU
> virtualization questions, including XenGT and KVMGT. Feel free to
> subscribe.
>
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_command,
too.
Signed-off-by: Juergen Gross
Reviewed-by: Wei Liu
---
tools/x
Today xenstored supports logging only via a command line parameter.
This means that logging is either all the time off (default) or on.
To switch logging on the Xen host has to be rebooted as xenstored
isn't restartable.
This patch series changes this by using the XS_DEBUG wire command of
Xenstore
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 dump the report to the standard log file call:
xenstore-control memreport
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_count_strings() before returned a value > 1.
Signed-off-by: Juergen Gross
R
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 associated xenstore-control
program used to issue XS_CONTROL commands.
Si
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
---
tools/xenstore/xenstored_core.c | 35 ++-
1 file changed, 2 insertions(+), 33 del
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 off at runtime and to
specify a (new) logfile. This is done via the XS_C
Commit 20b75251d97 ("libxl/libxl_pci.c: used LOG*D functions") reverses the
logic to call xc_deassign_device(). It makes the device unusable.
Signed-off-by: Chao Gao
---
tools/libxl/libxl_pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/libxl/libxl_pci.c b/tools/li
On 23/02/17 12:06, Wei Liu wrote:
> 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.
>>
>> Su
flight 106018 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106018/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xend-qemut-winxpsp3 15 guest-localmigrate/x10 fail REGR. vs.
105835
test-armh
On 17-02-23 15:46:36, Meng Xu wrote:
> Hi Yi,
>
> I have some quick comment about this document. Some minor points are
> not very clear, IMHO.
>
Thanks for your mail!
> > +
> > + 2. `psr-mba-set [OPTIONS] domain-id throttling`:
> > +
> > + Set memory bandwidth throttling for domain.
> > +
>
flight 106015 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106015/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-xtf-amd64-amd64-4 3 host-install(3) broken in 105990 pass in 106015
test-armhf-armhf-xl-vhd
On 23 February 2017 at 17:18, Joe Perches wrote:
> On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote:
>> 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_w
flight 106014 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106014/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-amd64-pvgrub 3 host-install(3) broken REGR. vs. 1059
flight 106011 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106011/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-raw3 host-install(3) broken pass in 105989
test-amd64-amd64-pair
Intel XenGT has another maillist " igv...@lists.01.org" to discuss Intel GPU
virtualization questions, including XenGT and KVMGT. Feel free to subscribe.
Right now, we have two version GVT-g, "old architecture" vs "new
architecture for upstream"
Old architecture:
- The codes are maintained off-t
Cc'ed to the mailing list of Intel graphic virtualization
[Sorry for the spam. The last cc failed as I didn't subscribe to
igv...@lists.01.org]
On 02/23/17 12:36 +, Paul Durrant wrote:
> Hi,
>
> I’m not actually sure where the latest public release of the xengt code is.
> Perhaps someo
Cc'ed to the mailing list of Intel graphic virtualization
[Sorry for the spam. The last cc failed as I didn't subscribe to
igv...@lists.01.org]
On 01/18/17 18:51 +053
This run is configured for baseline tests only.
flight 68608 xen-4.6-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68608/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-520 xtf/test-hvm32-
Cc'ed to the mailing list of Intel graphic virtualization
On 02/23/17 12:36 +, Paul Durrant wrote:
> 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.or
Cc'ed to the mailing list of Intel graphic virtualization
On 01/18/17 18:51 +0530, bharat gohil wrote:
> Hello
>
> I am new to GPU and GPU virtualization and found that xen support intel GPU
> virtualization using XenGT.
> I want to know,
> 1) What are the critical GPU command pass from xen to Do
flight 106009 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106009/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 3 host-install(3) broken REGR. vs. 59254
test-amd64-i386-xl-
On 23/02/2017 22:54, osstest service owner wrote:
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: xen git://xenbits.xen.org/xen.git
> Bug introduced: 49de10f3c1718bb952f4b075d07f37eb9f605b2b
> Bug not present: 38b48605f3693e950bb4155ea8dac6614d796c2b
> Last fail repro
On Wed, 2017-02-22 at 01:46 -0700, Jan Beulich wrote:
> > > > On 22.02.17 at 01:02, wrote:
> > (XEN)
> > (XEN) Panic on CPU 14:
> > (XEN) Assertion 'd->cpupool != NULL' failed at
> > ...5948.build-amd64/xen/xen/include/xen/sched-if.h:200
> > (XEN) *
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-qemuu-nested-amd
testid xen-boot/l1
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xen
flight 106032 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106032/
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
Hi Yi,
I have some quick comment about this document. Some minor points are
not very clear, IMHO.
> +
> + 2. `psr-mba-set [OPTIONS] domain-id throttling`:
> +
> + Set memory bandwidth throttling for domain.
> +
> + Options:
> + '-s': Specify the socket to process, otherwise all socke
flight 105994 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105994/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-winxpsp3 6 xen-bootfail REGR. vs. 105933
test-amd64-i386-xl
On Thu, 23 Feb 2017, Oleksandr Andrushchenko wrote:
> Hi, Stefano!
>
> On 02/22/2017 07:10 PM, Stefano Stabellini wrote:
> > On Wed, 22 Feb 2017, Oleksandr Andrushchenko wrote:
> > > Hi, Stefano, Jan!
> > > 1. Stefano, are you still NOT considering adding
> > > functionality to avoid memory copyin
flight 106004 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106004/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 3 host-install(3) broken REGR. vs. 105963
test-amd64-amd64-xl-qemuu-
flight 106025 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106025/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-i386 3 host-install(3) broken REGR.
Hi Stefano,
On 14/02/17 19:11, Stefano Stabellini wrote:
On Tue, 14 Feb 2017, Julien Grall wrote:
10. Domains on which the monitor privileged call feature is enabled
(which is by default disabled for all domains) should not be able to
issue firmware calls via SMCs/HVCs so that such calls
flight 106006 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106006/
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. 105973
Re
On Thu, 2017-02-23 at 17:41 +, Emil Velikov wrote:
> On 23 February 2017 at 17:18, Joe Perches wrote:
> > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote:
> > > 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
> > > >
flight 105998 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105998/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 3 host-install/src_host(3) broken REGR. vs.
105855
test-amd64-i
On Thu, Feb 23, 2017 at 05:25:32PM +, Ian Jackson wrote:
> Wei Liu writes ("Re: [PATCH 0/2] tools: split xl into a separate directory"):
> > On Thu, Feb 23, 2017 at 04:59:34PM +, Wei Liu wrote:
> > > But I am now very confused how we encode this in our build system.
> > > Obviously there is
Wei Liu writes ("Re: [PATCH 0/2] tools: split xl into a separate directory"):
> On Thu, Feb 23, 2017 at 04:59:34PM +, Wei Liu wrote:
> > But I am now very confused how we encode this in our build system.
> > Obviously there is already such need. Say, all the tools under misc
> > would require l
On Thu, Feb 23, 2017 at 07:18:17PM +0200, Razvan Cojocaru wrote:
> On 02/23/2017 06:46 PM, Wei Liu wrote:
> > xc_hvm_inject_trap is moved to the new libdevicemodel. Request the
> > compat layer from libxenctrl for now to make it build again.
> >
> > Signed-off-by: Wei Liu
> > ---
> > Cc: Ian Jack
On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote:
> 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 ex
On 02/23/2017 06:46 PM, Wei Liu wrote:
> xc_hvm_inject_trap is moved to the new libdevicemodel. Request the
> compat layer from libxenctrl for now to make it build again.
>
> Signed-off-by: Wei Liu
> ---
> Cc: Ian Jackson
> Cc: Razvan Cojocaru
> Cc: Tamas K Lengyel
>
> This patch is urgent to
On Thu, Feb 23, 2017 at 11:03:55AM -0600, Venu Busireddy wrote:
> As some users have suggested, elaborate the usage of RMRR specification
> on the command line, and provide a usage example.
>
> Also, always treat the specified page numbers as hexadecimal values.
>
> Signed-off-by: Venu Busireddy
As some users have suggested, elaborate the usage of RMRR specification
on the command line, and provide a usage example.
Also, always treat the specified page numbers as hexadecimal values.
Signed-off-by: Venu Busireddy
---
Changes in v2:
- Provide a better usage example.
- Treat input
On Wed, Feb 22, 2017 at 01:52:02AM -0700, Jan Beulich wrote:
> >>> On 21.02.17 at 21:42, wrote:
> > --- a/docs/misc/xen-command-line.markdown
> > +++ b/docs/misc/xen-command-line.markdown
> > @@ -1406,6 +1406,15 @@ If segment of the first device is not specified,
> > segment zero will be used.
>
On Thu, Feb 23, 2017 at 04:59:34PM +, Wei Liu wrote:
> On Thu, Feb 23, 2017 at 04:29:46PM +, Ian Jackson wrote:
> > Wei Liu writes ("Re: [PATCH 0/2] tools: split xl into a separate
> > directory"):
> > > On Thu, Feb 23, 2017 at 03:54:02PM +, Ian Jackson wrote:
> > > > No, this is entir
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
> Wei Liu
> Sent: 23 February 2017 16:47
> To: Xen-devel
> Cc: Ian Jackson ; Tamas K Lengyel
> ; Wei Liu ; Razvan Cojocaru
>
> Subject: [Xen-devel] [PATCH] xen-access: request compat devicemodel A
Wei Liu writes ("[PATCH] xen-access: request compat devicemodel API"):
> xc_hvm_inject_trap is moved to the new libdevicemodel. Request the
> compat layer from libxenctrl for now to make it build again.
Acked-by: Ian Jackson
___
Xen-devel mailing list
On Thu, Feb 23, 2017 at 04:29:46PM +, Ian Jackson wrote:
> Wei Liu writes ("Re: [PATCH 0/2] tools: split xl into a separate directory"):
> > On Thu, Feb 23, 2017 at 03:54:02PM +, Ian Jackson wrote:
> > > No, this is entirely wrong. You will end up running make in
> > > tools/libxl twice si
Hi Edgar,
On 22/02/17 04:03, Edgar E. Iglesias wrote:
On Mon, Feb 13, 2017 at 03:35:19PM +, Julien Grall wrote:
On 02/02/17 15:33, Edgar E. Iglesias wrote:
On Wed, Feb 01, 2017 at 07:04:43PM +, Julien Grall wrote:
On 31/01/2017 19:06, Edgar E. Iglesias wrote:
On Tue, Jan 31, 2017 at
xc_hvm_inject_trap is moved to the new libdevicemodel. Request the
compat layer from libxenctrl for now to make it build again.
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
Cc: Razvan Cojocaru
Cc: Tamas K Lengyel
This patch is urgent to unblock staging build.
Another way of fixing this is to a
flight 106021 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106021/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3)broken REGR. vs.
On Thu, Feb 23, 2017 at 04:16:15PM +, Andrew Cooper wrote:
> On 23/02/17 16:09, Jan Beulich wrote:
> On 23.02.17 at 16:27, wrote:
> >> I also don't see much benefit from deviating from what HVM does, so I would
> >> just leave it as is.
> > Understood. The risk is that in a couple of year
Wei Liu writes ("Re: [PATCH 0/2] tools: split xl into a separate directory"):
> On Thu, Feb 23, 2017 at 03:54:02PM +, Ian Jackson wrote:
> > No, this is entirely wrong. You will end up running make in
> > tools/libxl twice simultaneously.
>
> Libacpi can be built in different directories by s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xen Security Advisory XSA-210
arm: memory corruption when freeing p2m pages
ISSUE DESCRIPTION
=
When freeing pages used for stage-2 page tables, the freeing routine
failed to remove these pages from a
On 23/02/17 16:09, Jan Beulich wrote:
On 23.02.17 at 16:27, wrote:
>> I also don't see much benefit from deviating from what HVM does, so I would
>> just leave it as is.
> Understood. The risk is that in a couple of years time understanding
> why it is the way it is and (whether that's necess
>>> On 23.02.17 at 17:01, wrote:
> On Thu, Feb 23, 2017 at 06:47:24AM -0700, Jan Beulich wrote:
>> >>> On 22.02.17 at 15:24, wrote:
>> > --- a/xen/common/libelf/libelf-loader.c
>> > +++ b/xen/common/libelf/libelf-loader.c
>> > @@ -146,6 +146,25 @@ void elf_set_verbose(struct elf_binary *elf)
>> >
>>> On 23.02.17 at 16:27, wrote:
> I also don't see much benefit from deviating from what HVM does, so I would
> just leave it as is.
Understood. The risk is that in a couple of years time understanding
why it is the way it is and (whether that's necessary) may take as
much effort as did the deci
On Thu, Feb 23, 2017 at 06:47:24AM -0700, Jan Beulich wrote:
> >>> 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_co
On Thu, Feb 23, 2017 at 03:54:02PM +, Ian Jackson wrote:
> Wei Liu writes ("Re: [PATCH 0/2] tools: split xl into a separate directory"):
> > Basically this needs to be folded into xl/Makefile:
> >
> > +# libxenlight should be built before building xl
> > +.PHONY: libxl
> > +libxl:
> > +
Wei Liu writes ("[PATCH] libs/devicemodel: initialise op_bufs in
xendevicemodel_xcall"):
> To avoid freeing uninitialised buffer when taking the first error exit
> path.
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://
Wei Liu writes ("Re: [PATCH 0/2] tools: split xl into a separate directory"):
> Basically this needs to be folded into xl/Makefile:
>
> +# libxenlight should be built before building xl
> +.PHONY: libxl
> +libxl:
> + $(MAKE) -C $(XEN_ROOT)/tools/libxl
> +$(XL_OBJS): libxl
OMG.
> This is in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xen Security Advisory CVE-2017-2620 / XSA-209
version 4
cirrus_bitblt_cputovideo does not check if memory region is safe
UPDATES IN VERSION 4
Include a prerequisite patch for qemu-ups
On Thu, Feb 23, 2017 at 06:39:53AM -0700, Jan Beulich wrote:
> >>> 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 fro
On Thu, Feb 23, 2017 at 11:55:15AM +, Xuquan (Quan Xu) wrote:
>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:
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/
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
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 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
>>> 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
> -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 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
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,
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.
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 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 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
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
>>> 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
>>> 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:
> 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:
> 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 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 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
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 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:
>>> [..]
>> + *
>> +
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 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/
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
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: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
>
>
>
> -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 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
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 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
>>> 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 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
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.
___
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
1 - 100 of 164 matches
Mail list logo