> -Original Message-
> From: Tian, Kevin [mailto:kevin.t...@intel.com]
> Sent: 06 August 2018 04:19
> To: Roger Pau Monne ; Paul Durrant
>
> Cc: Jan Beulich ; Stefano Stabellini
> ; Wei Liu ; George Dunlap
> ; Andrew Cooper
> ; Ian Jackson ; Tim
> (Xen.org) ; Julien Grall ; Suravee
> Suthi
flight 125759 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125759/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 6 kernel-build fail REGR. vs. 125758
Tests which did not succee
This run is configured for baseline tests only.
flight 75049 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75049/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 75047
test
On Mon, Aug 06, 2018 at 08:51:55AM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: Tian, Kevin [mailto:kevin.t...@intel.com]
> > Sent: 06 August 2018 04:19
> > To: Roger Pau Monne ; Paul Durrant
> >
> > Cc: Jan Beulich ; Stefano Stabellini
> > ; Wei Liu ; George Dunlap
> > ; An
On Sat, Aug 04, 2018 at 08:25:18PM +0200, Marek Marczykowski-Górecki wrote:
> Hi,
>
> libxl__domain_build calls libxl__build_hvm for both
> LIBXL_DOMAIN_TYPE_HVM and LIBXL_DOMAIN_TYPE_PVH, but libxl__build_hvm
> uses fields from b_info->u.hvm, which looks like invalid thing to do.
> Should those f
On Sat, Aug 04, 2018 at 07:08:59PM -0500, Gustavo A. R. Silva wrote:
> Return statements in functions returning bool should use true or false
> instead of an integer value.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A. R. Silva
Acked-by: Roger Pau Monné
flight 75048 distros-debian-sid real [real]
http://osstest.xensource.com/osstest/logs/75048/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-armhf-sid-netboot-pygrub 10 debian-di-install fail like 75026
test-amd64-amd64-i386-sid-netboot-pygru
Gcc 8.1 has a bug that causes kdd fail to build. Rewrite the code to
work around that bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86827
Signed-off-by: Tim Deegan
Signed-off-by: Wei Liu
Tested-by: Wei Liu
---
tools/debugger/kdd/kdd.c | 9 -
1 file changed, 4 insertions(+), 5 del
flight 125761 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125761/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 6 kernel-build fail REGR. vs. 125758
Tests which did not succee
On Fri, Aug 03, 2018 at 04:33:31PM +0100, Anthony PERARD wrote:
> On Thu, Aug 02, 2018 at 12:25:53PM +0200, Roger Pau Monné wrote:
> > On Fri, Jul 27, 2018 at 03:05:59PM +0100, Anthony PERARD wrote:
> > > +/* workaround strstr limitation */
> > > +ev->rx_buf[ev->buf_used] = '\0';
> >
> > W
On Fri, Aug 03, 2018 at 06:25:00PM +0100, Anthony PERARD wrote:
> On Thu, Aug 02, 2018 at 01:17:37PM +0200, Roger Pau Monné wrote:
> > On Fri, Jul 27, 2018 at 03:06:04PM +0100, Anthony PERARD wrote:
> > > diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl
> > > index 4a385801ba.
Persistent grants are allocated until a threshold per ring is being
reached. Those grants won't be freed until the ring is being destroyed
meaning there will be resources kept busy which might no longer be
used.
Instead of freeing only persistent grants until the threshold is
reached add a timesta
Add a periodic cleanup function to remove old persistent grants which
are no longer in use on the backend side. This avoids starvation in
case there are lots of persistent grants for a device which no longer
is involved in I/O business.
Signed-off-by: Juergen Gross
---
drivers/block/xen-blkfront
flight 125762 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125762/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-freebsd 7 freebsd-buildfail REGR. vs. 125317
Tests which did
Persistent grants are used in the Xen's blkfront/blkback drivers to
avoid mapping/unmapping of I/O buffers in the backend for each I/O.
While this speeds up processing quite a bit there are problems related
to persistent grants in some configurations: domains with multiple
block devices making use
pers_gnts_lock isn't being used anywhere. Remove it.
Signed-off-by: Juergen Gross
---
drivers/block/xen-blkback/common.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/block/xen-blkback/common.h
b/drivers/block/xen-blkback/common.h
index 26710602d463..4b7747159c38 100644
--- a/drive
On 06/08/18 13:34, Juergen Gross wrote:
> Remove some macros not used anywhere.
Meh, ignore that one, please. Doesn't belong to this series.
Juergen
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinf
Remove some macros not used anywhere.
Signed-off-by: Juergen Gross
---
drivers/block/xen-blkfront.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
index b5cedccb5d7d..94300dbe358b 100644
--- a/drivers/block/xen-blkfront.c
+++ b
On Mon, Aug 06, 2018 at 11:16:49AM +0200, Roger Pau Monné wrote:
> On Sat, Aug 04, 2018 at 08:25:18PM +0200, Marek Marczykowski-Górecki wrote:
> > Hi,
> >
> > libxl__domain_build calls libxl__build_hvm for both
> > LIBXL_DOMAIN_TYPE_HVM and LIBXL_DOMAIN_TYPE_PVH, but libxl__build_hvm
> > uses fiel
In case we don't want pv block devices we should not test parameters
for sanity and eventually print out error messages. So test precluding
conditions before checking parameters.
Signed-off-by: Juergen Gross
---
drivers/block/xen-blkfront.c | 18 +-
1 file changed, 9 insertions(+
On 05/08/18 02:50, Gustavo A. R. Silva wrote:
> Return statements in functions returning bool should use true or false
> instead of an integer value.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A. R. Silva
Reviewed-by: Juergen Gross
Juergen
___
On 08/06/2018 06:42 AM, Juergen Gross wrote:
> On 05/08/18 02:50, Gustavo A. R. Silva wrote:
>> Return statements in functions returning bool should use true or false
>> instead of an integer value.
>>
>> This code was detected with the help of Coccinelle.
>>
>> Signed-off-by: Gustavo A. R. Silva
This patch allows grant table frames to be mapped using the
XENMEM_acquire_resource memory op.
NOTE: This patch expands the on-stack mfn_list array in acquire_resource()
but it is still small enough to remain on-stack.
Signed-off-by: Paul Durrant
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc:
A previous patch added support for priv-mapping guest resources directly
(rather than having to foreign-map, which requires P2M modification for
HVM guests).
This patch makes use of the new API to seed the guest grant table unless
the underlying infrastructure (i.e. privcmd) doesn't support it, in
These patches are the patches from my original resource mapping series
that did not make it into 4.11.
Paul Durrant (2):
common: add a new mappable resource type: XENMEM_resource_grant_table
tools/libxenctrl: use new xenforeignmemory API to seed grant table
tools/libxc/include/xc_dom.h
On Mon, Aug 06, 2018 at 01:25:22PM +0200, Roger Pau Monné wrote:
> On Fri, Aug 03, 2018 at 06:25:00PM +0100, Anthony PERARD wrote:
> > On Thu, Aug 02, 2018 at 01:17:37PM +0200, Roger Pau Monné wrote:
> > > On Fri, Jul 27, 2018 at 03:06:04PM +0100, Anthony PERARD wrote:
> > > > diff --git a/tools/li
On 8/4/18 6:08 PM, Gustavo A. R. Silva wrote:
> Return statements in functions returning bool should use true or false
> instead of an integer value.
>
> This code was detected with the help of Coccinelle.
Applied, thanks.
--
Jens Axboe
___
Xen-deve
flight 125544 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125544/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs. 125183
Tests which are fail
flight 125749 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125749/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken
build-arm64-xsm
flight 125742 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125742/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 broken
build-arm64-pvops
flight 125745 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125745/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 broken
build-arm64-xsm
flight 125751 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125751/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-pvops
On Fri, Aug 03, 2018 at 05:24:52PM +0200, Roger Pau Monné wrote:
> On Fri, Aug 03, 2018 at 03:32:09PM +0100, Anthony PERARD wrote:
> > On Thu, Aug 02, 2018 at 11:56:11AM +0200, Roger Pau Monné wrote:
> > > On Fri, Jul 27, 2018 at 03:05:56PM +0100, Anthony PERARD wrote:
> > > > +/* The -1 is
On Mon, Aug 06, 2018 at 02:14:51PM +0100, Anthony PERARD wrote:
> On Mon, Aug 06, 2018 at 01:25:22PM +0200, Roger Pau Monné wrote:
> > On Fri, Aug 03, 2018 at 06:25:00PM +0100, Anthony PERARD wrote:
> > > On Thu, Aug 02, 2018 at 01:17:37PM +0200, Roger Pau Monné wrote:
> > > > On Fri, Jul 27, 2018
flight 125747 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125747/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64
flight 125743 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125743/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-pvops
flight 125744 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125744/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
Regressions wh
flight 125536 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125536/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 broken in 125509
test-amd64-amd64-xl-qemuu-debian
flight 125763 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125763/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf d3bc33731f5b039bf3df76e50cbb1f60ce697e9b
baseline version:
ovmf cd3a42640acdb4f5ac14a
On Thu, Aug 02, 2018 at 01:34:52PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:07PM +0100, Anthony PERARD wrote:
> > This function can be use by user libxl__spawn_* when they setup a
>^ used and remove user
I meant user of libxl__spawn, so I'll s/user/user
On Mon, Aug 06, 2018 at 01:33:59PM +0200, Juergen Gross wrote:
> Persistent grants are allocated until a threshold per ring is being
> reached. Those grants won't be freed until the ring is being destroyed
> meaning there will be resources kept busy which might no longer be
> used.
>
> Instead of
On Mon, Aug 06, 2018 at 01:34:01PM +0200, Juergen Gross wrote:
> Add a periodic cleanup function to remove old persistent grants which
> are no longer in use on the backend side. This avoids starvation in
> case there are lots of persistent grants for a device which no longer
> is involved in I/O b
On Thu, Aug 2, 2018 at 1:13 PM, Ulrich Windl
wrote:
> Hi!
>
> WHen using "xm list test12 -l" that seems to be in pvgrub state, I get this
> error:
Unfortunately Xen 4.4 is long out of security support, and xm/xend was
deprecated even in Xen 4.4. Have you tried using its replacement, xl?
-Geor
On Mon, Aug 06, 2018 at 01:34:02PM +0200, Juergen Gross wrote:
> In case we don't want pv block devices we should not test parameters
> for sanity and eventually print out error messages. So test precluding
> conditions before checking parameters.
>
> Signed-off-by: Juergen Gross
Reviewed-by: Ro
On Mon, Aug 06, 2018 at 01:34:03PM +0200, Juergen Gross wrote:
> pers_gnts_lock isn't being used anywhere. Remove it.
That was likely a leftover from when the list of persistent grants was
shared between rings.
> Signed-off-by: Juergen Gross
Reviewed-by: Roger Pau Monné
Thanks, Roger.
__
On Thu, Aug 02, 2018 at 05:08:15PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:10PM +0100, Anthony PERARD wrote:
> > This will be used in a later patch.
> >
> > Signed-off-by: Anthony PERARD
> > ---
> > tools/libxl/libxl_internal.h | 7 +++
> > tools/libxl/libxl_qmp.c
On Thu, Aug 02, 2018 at 05:38:41PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:12PM +0100, Anthony PERARD wrote:
> > +
> > +if (qmp_ev_qemu_check_version(ev, 2, 11, 0))
> > +qmp_parameters_add_bool(gc, &args, "live", dsps->live);
> > +QMP_PARAMETERS_SPRINTF(&args,
On Thu, Aug 02, 2018 at 05:50:52PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:13PM +0100, Anthony PERARD wrote:
> Can you provide a comment explaining how is this supposed to work? The
> current code is already quite convoluted IMO (maybe because I'm not
> familiar with it), so I
This run is configured for baseline tests only.
flight 75050 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75050/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 75049
test
On Thu, Aug 02, 2018 at 01:26:35PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:05PM +0100, Anthony PERARD wrote:
> > Signed-off-by: Anthony PERARD
> > ---
> > tools/libxl/libxl_qmp.c | 36 ++--
> > 1 file changed, 30 insertions(+), 6 deletions(-)
flight 125772 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125772/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
Regressions wh
From: Oleksandr Tyshchenko
Signed-off-by: Oleksandr Tyshchenko
CC: Stefano Stabellini
CC: Julien Grall
---
xen/drivers/char/scif-uart.c| 4
xen/include/asm-arm/scif-uart.h | 11 ---
2 files changed, 15 deletions(-)
diff --git a/xen/drivers/char/scif-uart.c b/xen/drivers/cha
From: Oleksandr Tyshchenko
Hi, all.
The purpose of this patch series is to add required support to be able to run
Xen on
Renesas Stout board [1] which uses SCIFA compatible UART as a console interface.
Actually Xen already has support for SCIF compatible UARTs which are used on
Renesas Lager
From: Oleksandr Tyshchenko
Extend existing driver to be able to handle SCIFA interface as well.
SCIF and SCIFA have lot in common, though SCIFA has different
offsets and bits for some registers.
Use compatible string to recognize what interface is present
on a target board.
Signed-off-by: Oleks
From: Oleksandr Tyshchenko
Add support for Renesas "Stout" development board based on
R-Car H2 SoC which has SCIFA compatible UART.
Actually existing SCIF UART support (debug-scif.inc) and
newly added SCIFA UART support (debug-scifa.inc) differ only
in registers offsets.
Signed-off-by: Oleksand
From: Oleksandr Tyshchenko
Renesas "Stout" development board (with different expansion boards)
is also based on R-Car Gen2 SoC. So extend compat array with
board's compatible strings.
Signed-off-by: Oleksandr Tyshchenko
CC: Stefano Stabellini
CC: Julien Grall
---
xen/arch/arm/platforms/rcar2
flight 125753 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125753/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken
build-arm64-xsm
On Thu, Aug 02, 2018 at 01:09:06AM -0600, Jan Beulich wrote:
> >>> On 02.08.18 at 00:20, wrote:
> > On Tue, Jul 31, 2018 at 05:25:27AM -0600, Jan Beulich wrote:
> >> Code structure wise this looks to undo a fair part of what patch
> >> 1 has done. It would be nice to limit code churn.
> >
> > Pat
I just got the following patch from a colleague. It's a backport of
the XSA 274 kernel patch to 4.9.x kernels. The kernel patch given in
the XSA would not apply cleanly. Would someone mind reviewing it? It
would be much appreciated.
commit b3681dd548d06deb2e1573890829dff4b15abf46 upstream.
Th
x86 maintainers, this needs your ack please.
-boris
On 07/24/2018 08:45 AM, M. Vefa Bicakci wrote:
> Commit d94a155c59c9 ("x86/cpu: Prevent cpuinfo_x86::x86_phys_bits
> adjustment corruption") has moved the query and calculation of the
> x86_virt_bits and x86_phys_bits fields of the cpuinfo_x86
On Mon, 6 Aug 2018, Boris Ostrovsky wrote:
> x86 maintainers, this needs your ack please.
Reviewed-by: Thomas Gleixner
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 08/06/2018 04:16 PM, Thomas Gleixner wrote:
> On Mon, 6 Aug 2018, Boris Ostrovsky wrote:
>
>> x86 maintainers, this needs your ack please.
> Reviewed-by: Thomas Gleixner
>
Thanks.
Applied to for-linus-4.19
___
Xen-devel mailing list
Xen-devel@list
On 08/06/2018 07:42 AM, Juergen Gross wrote:
> On 05/08/18 02:50, Gustavo A. R. Silva wrote:
>> Return statements in functions returning bool should use true or false
>> instead of an integer value.
>>
>> This code was detected with the help of Coccinelle.
>>
>> Signed-off-by: Gustavo A. R. Silva
flight 125774 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125774/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
Regressions wh
flight 125776 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125776/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
Regressions wh
This allows using arguments with spaces, like -append.
Stubdomain side of this require "xenstore-client: Add option for raw
in-/output" commit.
Signed-off-by: Marek Marczykowski-Górecki
Reviewed-by: Jason Andryuk
---
tools/libxl/libxl_dm.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-
When qemu is running in stubdomain, any attempt to initialize vnc/sdl
there will crash it (on failed attempt to load a keymap from a file). If
vfb is present, all those cases are skipped. But since
b053f0c4c9e533f3d97837cf897eb920b8355ed3 "libxl: do not start dom0 qemu
for stubdomain when not neede
Since multiple consoles support was added to xenconsoled, use it for
stubdomain. This makes it possible to have HVM without qemu in dom0 at
al. As long as no other feature requiring qemu in dom0 is used, like VNC
or qdisk.
Signed-off-by: Marek Marczykowski-Górecki
---
tools/libxl/libxl_dm.c | 7
Add support for standard xenbus initialization protocol using 'state'
xenstore entry. It will be necessary for secondary consoles.
For consoles supporting it, read 'state' entry on the frontend and
proceed accordingly - either init console or close it. When closing,
make sure all the in-transit dat
From: Eric Shelton
This enum gives the ability to select between a MiniOS-based QEMU
traditional stub domain and a Linux-based QEMU upstream stub domain. To
use the Linux-based stubdomain, the following two lines should be
included in the appropriate xl.cfg file:
device_model_version="qemu-xen"
From: Eric Shelton
This will build a Linux-based stubdomain with QEMU upstream.
Signed-off-by: Eric Shelton
Simon:
* use initramfs instead of disk with rootfs
* don't initialize qmp (unused in Qubes)
* Make libxl_domain_need_memory consistent with actual stubdoma build
code (bugfix relev
Not only for the primary one (/local/domain//console path).
Signed-off-by: Marek Marczykowski-Górecki
---
tools/console/daemon/io.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tools/console/daemon/io.c b/tools/console/daemon/io.c
index 8dac279..4d4e223 100644
Before this commit 'use_gnttab' means xenconsoled should first try
special GNTTAB_RESERVED_CONSOLE entry, and only then fallback to
ring-ref xenstore entry (being gfn of actual ring).
In case of secondary consoles, ring-ref entry contains grant table
reference (not gfn of it), which makes the old m
Handle 'output' xenstore entry, as qemu does. Right now support only few
simple options:
- "pty" (unchanged)
- "file:path" (overwrite file)
- "pipe:path" (read-write file/pipe)
- "null"
Also, when ever read() returns 0, stop reading from that source, instead
of spinning in a loop.
For now, in
From: Simon Gaiser
There is no QMP socket access, re-use the same mechanism as for MiniOS
based stubdom.
Signed-off-by: Marek Marczykowski-Górecki
---
tools/libxl/libxl_pci.c | 22 ++
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/tools/libxl/libxl_pci.c b/t
General idea is to allow freely set device_model_version and
device_model_stubdomain_override and choose the right options based on this
choice.
Also, allow to specific path to stubdomain kernel/ramdisk, for greater
flexibility.
Right now when qemu-xen in stubdomain is selected, it is assumed it'
Rely on a wrapper script in stubdomain to attach FD 3/4 of qemu to
relevant consoles.
Signed-off-by: Marek Marczykowski-Górecki
Reviewed-by: Jason Andryuk
---
tools/libxl/libxl_dm.c | 23 +++
tools/libxl/libxl_dom_suspend.c | 10 --
2 files changed, 19 inser
Add support for talking with qemu in stubdomain via QMP connected to a
console. Since a console doesn't have out of band connect/disconnect
signaling, use (new) qmp_reset command at every connect, to force
renegotiation.
This commit doesn't deal with multiple users accessing the same console.
For
Signed-off-by: Marek Marczykowski-Górecki
Reviewed-by: Jason Andryuk
---
docs/man/xl.cfg.pod.5.in | 23 +++
tools/xl/xl_parse.c | 7 +++
2 files changed, 26 insertions(+), 4 deletions(-)
diff --git a/docs/man/xl.cfg.pod.5.in b/docs/man/xl.cfg.pod.5.in
index b727181
Based on previous few commits, this adds basic support for multiple
consoles in xenconsoled. A static number of them - up to 3 (+ one
primary).
Signed-off-by: Marek Marczykowski-Górecki
---
I know this is awful, but everything else I can think of (real support
for multiple consoles, dynamically a
The forced vkb device is meant for better performance of qemu access
(at least according to ebbd2561b4cefb299f0f68a88b2788504223de18 "libxl:
Add a vkbd frontend/backend pair for HVM guests"), which isn't used if
there is no configured channel to actually access that keyboard.
One can still add vkb
From: Eric Shelton
This patch creates an appropriate command line for the QEMU instance
running in a Linux-based stubdomain.
NOTE: a number of items are not currently implemented for Linux-based
stubdomains, such as:
- save/restore
- QMP socket
- graphics output (e.g., VNC)
Signed-off-by: Eric
Signed-off-by: Marek Marczykowski-Górecki
---
tools/console/daemon/io.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/tools/console/daemon/io.c b/tools/console/daemon/io.c
index c2c37dc..ea07442 100644
--- a/tools/console/daemon/io.c
+++ b/tools/console/dae
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Saturday, August 4, 2018 1:22 AM
>
> ...meaning 'bus frame number' i.e. a frame number mapped in the IOMMU
> rather than the MMU.
>
> This patch is a largely cosmetic change that substitutes the terms 'gfn'
> and 'gaddr' for 'bfn' and
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Saturday, August 4, 2018 1:22 AM
>
> This patch modifies the declaration of the entry points to the IOMMU
> sub-system to use bfn_t and mfn_t in place of unsigned long. A subsequent
> patch will similarly modify the methods in the iommu
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Saturday, August 4, 2018 1:22 AM
>
> This patch modifies the methods in struct iommu_ops to use type-safe BFN
> and MFN. This follows on from the prior patch that modified the functions
> exported in xen/iommu.h.
>
> Signed-off-by: Pau
flight 125777 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125777/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-armhf 6 xen
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Saturday, August 4, 2018 1:22 AM
>
> Turn iommu_map/unmap_page() into straightforward wrappers that check
> the
iommu_iotlb_flush is also changed.
> existence of the relevant iommu_op and call through to it. This makes them
> usable b
> From: Paul Durrant
> Sent: Saturday, August 4, 2018 1:22 AM
>
> This patch introduces the boilerplate for a new hypercall to allow a
> domain to control IOMMU mappings for its own pages.
> Whilst there is duplication of code between the native and compat entry
> points which appears ripe for som
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Saturday, August 4, 2018 1:22 AM
>
> Ranges that should be considered reserved in the IOMMU are not
> necessarily
> limited to RMRRs. If iommu_inclusive_mapping is set then any frame
> number
> falling within an E820 reserved region sho
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Saturday, August 4, 2018 1:22 AM
>
> This patch adds a new method to the VT-d IOMMU implementation to find
> the
> MFN currently mapped by the specified BFN along with a wrapper function
> in
> generic IOMMU code to call the implementat
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Saturday, August 4, 2018 1:22 AM
>
> The name 'iommu_use_hap_pt' suggests that that P2M table is in use as
> the
> domain's IOMMU pagetable which, prior to this patch, is not strictly true
> since the macro did not test whether the doma
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Saturday, August 4, 2018 1:22 AM
>
> The name 'need_iommu' is a little confusing as it suggests a domain needs
> to use the IOMMU but something might not be set up yet, when in fact it
> doesn't become true until IOMMU mappings for the
flight 125768 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125768/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken
build-arm64-xsm
> From: Paul Durrant
> Sent: Saturday, August 4, 2018 1:22 AM
>
> This patch adds an iommu_op which checks whether it is possible or
> safe for a domain to modify its own IOMMU mappings and, if so, creates
> a rangeset to track modifications.
Have to say that there might be a concept mismatch bet
flight 125778 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125778/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
Regressions wh
On 06/08/18 18:16, Roger Pau Monné wrote:
> On Mon, Aug 06, 2018 at 01:34:01PM +0200, Juergen Gross wrote:
>> Add a periodic cleanup function to remove old persistent grants which
>> are no longer in use on the backend side. This avoids starvation in
>> case there are lots of persistent grants for
On 06/08/18 17:58, Roger Pau Monné wrote:
> On Mon, Aug 06, 2018 at 01:33:59PM +0200, Juergen Gross wrote:
>> Persistent grants are allocated until a threshold per ring is being
>> reached. Those grants won't be freed until the ring is being destroyed
>> meaning there will be resources kept busy wh
>>> George Dunlap schrieb am 06.08.2018 um 18:16 in
>>> Nachricht
:
> On Thu, Aug 2, 2018 at 1:13 PM, Ulrich Windl
> wrote:
>> Hi!
>>
>> WHen using "xm list test12 -l" that seems to be in pvgrub state, I get this
> error:
>
> Unfortunately Xen 4.4 is long out of security support, and xm/xend w
99 matches
Mail list logo
