This run is configured for baseline tests only.
flight 74490 xen-4.8-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74490/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64
flight 121953 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121953/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 121876
build-armhf
This run is configured for baseline tests only.
flight 74491 xen-4.9-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74491/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64
This run is configured for baseline tests only.
flight 74494 qemu-upstream-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74494/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64
This run is configured for baseline tests only.
flight 74489 xen-4.7-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74489/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64
Den 05.04.2018 kl. 10:02, skrev Juergen Gross:
The kernel is wrong here. You don't want to take the patches fixing the
issue. That's rather sad as PVH mode was meant to replace PV in the
future, which will remove the need for most of the paravirt ops stuff.
You are just shifting that possibilit
Hi,
> Compiled with CONFIG_EARLY_PRINTK=mvebu, I see Xen's pre-DT boot
> messages. In addition to my Reviewed-by:
>
> Tested-by: Andre Przywara
>
Thank you!
Thanks
-Amit
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproje
Hi,
> Works like a charm, can log into Dom0, Xen console works as well. So in
> addition to my Reviewed-by:
>
> Tested-by: Andre Przywara
>
Thank you for your time on this!
Thanks
-Amit
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https
flight 121947 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121947/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 121876
build-armhf
This run is configured for baseline tests only.
flight 74488 xen-4.6-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74488/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64
flight 121817 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121817/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf e8debcece867acffc2c0c477f4572948c585940b
baseline version:
xtf 086cad25a948e54cf84319
flight 121799 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121799/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-intel 17 debian-hvm-install/l1/l2 fail REGR. vs.
119227
Tests w
This run is configured for baseline tests only.
flight 74496 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74496/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm
branch xen-unstable-smoke
xenbranch xen-unstable-smoke
job build-arm64-xsm
testid xen-build
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits.xen.org/xen.git
Bug introduced:
flight 121936 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121936/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 121876
build-armhf
flight 121771 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121771/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail like 121707
test-armhf-armhf-libvirt 14 saveresto
Hi all,
The main topic of the meeting was certifications for Xen on ARM. The gap
analysis document, mentioned in the previous call, is copyrighted. It
might not be possible to relicense it. Regardless of the document, we
started discussing the major work items and next steps.
1) Requirements to t
On 04/05/2018 11:42 AM, Paul Durrant wrote:
> My recent Xen patch series introduces a new HYPERVISOR_memory_op to
> support direct priv-mapping of certain guest resources (such as ioreq
> pages, used by emulators) by a tools domain, rather than having to access
> such resources via the guest P2M.
>
This run is configured for baseline tests only.
flight 74495 seabios real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74495/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm
flight 121920 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121920/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 121876
build-armhf
flight 121768 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121768/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-xsm 10 debian-install fail REGR. vs. 121723
test-arm64-arm64-xl
This run is configured for baseline tests only.
flight 74486 linux-3.18 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74486/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64
On Tue, 3 Apr 2018, Julien Grall wrote:
> Most of the users of page_to_mfn and mfn_to_page are either overriding
> the macros to make them work with mfn_t or use mfn_x/_mfn because the
> rest of the function use mfn_t.
>
> So make page_to_mfn and mfn_to_page return mfn_t by default. The __*
> vers
On Tue, 3 Apr 2018, Julien Grall wrote:
> At the same time replace MFN 0 by INVALID_MFN or drop the initializer
> when it is not necessary. This will make clearer that the MFN
> initialized is not valid.
>
> Other than MFN 0 -> INVALID_MFN, no functional change intended.
>
> Signed-off-by: Julien
On Tue, 3 Apr 2018, Julien Grall wrote:
> The current prototype is slightly confusing because it takes a guest
> physical address and a machine physical frame (not address!). Switching to
> MFN will improve safety and reduce the chance to mistakenly invert the
> 2 parameters.
>
> Signed-off-by: Ju
On Tue, 3 Apr 2018, Julien Grall wrote:
> The current prototype is slightly confusing because it takes a virtual
> address and a physical frame (not address!). Switching to MFN will improve
> safety and reduce the chance to mistakenly invert the 2 parameters.
>
> Also, take the opportunity to swit
On Tue, 3 Apr 2018, Julien Grall wrote:
> The function populate_pt_range is used to populate in advance the
> page-table but it will not do the actual mapping. So passing the MFN in
> parameter is pointless. Note that the only caller pass 0...
>
> At the same time replace 0 by INVALID_MFNs. While
On Tue, 3 Apr 2018, Julien Grall wrote:
> relinquish_shared_pages is never called on Arm.
>
> Signed-off-by: Julien Grall
> Reviewed-by: George Dunlap
Acked-by: Stefano Stabellini
> ---
>
> Cc: Stefano Stabellini
>
> Changes in v6:
> - Add George's reviewed-by
>
> Changes
On Tue, 3 Apr 2018, Julien Grall wrote:
> Arm does not have an M2P and very unlikely to get one in the future,
> therefore don't keep defines that are not necessary in the common code.
>
> At the same time move the remaining M2P define just above
> set_gpfn_from_mfn to keep all the dummy helpers f
On Tue, 3 Apr 2018, Julien Grall wrote:
> Signed-off-by: Julien Grall
> Reviewed-by: George Dunlap
Acked-by: Stefano Stabellini
> ---
> Cc: Stefano Stabellini
>
> Changes in v7:
> - Add George's reviewed-by
>
> Changes in v6:
> - Remove the justification from the com
On Tue, 3 Apr 2018, Julien Grall wrote:
> Signed-off-by: Julien Grall
> Reviewed-by: George Dunlap
Acked-by: Stefano Stabellini
> ---
> Cc: Stefano Stabellini
>
> Changes in v6:
> - Remove the justification from the commit message
> - Add George's reviewed-by
>
> Cha
On Thu, 5 Apr 2018, Julien Grall wrote:
> On 02/04/18 12:17, Manish Jaggi wrote:
> >
> >
> > On 04/02/2018 04:33 PM, Manish Jaggi wrote:
> > >
> > > On 03/27/2018 03:48 PM, Marc Zyngier wrote:
> > > > On 27/03/18 10:07, Manish Jaggi wrote:
> > > > > This patch is ported to xen from linux commit
On 05/04/18 11:16, Amit Singh Tomar wrote:
> Signed-off-by: Amit Singh Tomar
Compiled with CONFIG_EARLY_PRINTK=mvebu, I see Xen's pre-DT boot
messages. In addition to my Reviewed-by:
Tested-by: Andre Przywara
Cheers,
Andre.
> ---
> Changes since v2:
> * Addressed Andre's comments.
> Chang
On 05/04/18 11:16, Amit Singh Tomar wrote:
> This patch adds driver for UART controller found on Armada 3700 SoC.
>
> There is no reference manuals available for 3700 SoC in public and it
> is derived by looking at Linux driver[1].
>
> [1]https://github.com/torvalds/linux/blob/master/drivers/tty/
c/s 74fd984ae "tools/libxl: Drop xc_domain_configuration_t from
libxl__domain_build_state" removed state->config completely, but the GIC
version is available in info. Use the up-to-date version.
Signed-off-by: Andrew Cooper
---
CC: Ian Jackson
CC: Wei Liu
CC: Stefano Stabellini
CC: Julien Gra
On 04/05/2018 01:11 PM, Juergen Gross wrote:
> On 05/04/18 16:56, George Dunlap wrote:
>> On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
>>> On 05/04/18 15:42, George Dunlap wrote:
On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
> On 05/04/18 15:00, Boris Ostrovsky wrote:
flight 121905 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121905/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 121876
build-armhf
On 05/04/18 18:45, Marek Marczykowski-Górecki wrote:
> On Thu, Apr 05, 2018 at 01:54:03PM +0100, Wei Liu wrote:
>> CC Marek
>>
>> On Thu, Apr 05, 2018 at 12:49:23PM +, Petre Eftime wrote:
>>> When 0-indexing, maximum index is num_entries - 1. The python xc library
>>> had a
>>> sign error wher
On 05/04/18 16:56, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
>> On 05/04/18 15:42, George Dunlap wrote:
>>> On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
On 05/04/18 15:00, Boris Ostrovsky wrote:
> On 04/05/2018 08:19 AM, Juergen Gross wrote:
On Thu, Apr 05, 2018 at 01:54:03PM +0100, Wei Liu wrote:
> CC Marek
>
> On Thu, Apr 05, 2018 at 12:49:23PM +, Petre Eftime wrote:
> > When 0-indexing, maximum index is num_entries - 1. The python xc library
> > had a
> > sign error where the minus was replaced by a plus, making tools that
>
I think this is a good patch as it reduces the amount of copying. I
believe it is safe as it is. There is one place where I am a little
hesitant:
@@ -291,7 +291,9 @@ let access_logging ~con ~tid ?(data="") ~level
access_type =
let date = string_of_date() in
My recent Xen patch series introduces a new HYPERVISOR_memory_op to
support direct priv-mapping of certain guest resources (such as ioreq
pages, used by emulators) by a tools domain, rather than having to access
such resources via the guest P2M.
This patch adds the necessary infrastructure to the
flight 121889 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121889/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 121876
build-armhf
flight 121769 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121769/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf aae02dccf5b0ad07e60d2738f350b3b39df389d7
baseline version:
ovmf c4172f80051effc62f3ec
On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
> On 05/04/18 15:42, George Dunlap wrote:
>> On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
>>> On 05/04/18 15:00, Boris Ostrovsky wrote:
On 04/05/2018 08:19 AM, Juergen Gross wrote:
> On 05/04/18 12:06, George Dunlap wrote:
We universally use UTF-8 in git commit messages and other kinds of
messages. The RFC-*822 default is us-ascii. Fix this by providing a
set of MIME headers.
Reported-by: Andrew Cooper
Signed-off-by: Ian Jackson
---
Osstest.pm | 6 ++
cri-args-hostlists | 1 +
mg-execute-flight | 2
5d2466dc0f26 "cr-ensure-disk-space: Correct stdout output" was
supposed to change an `exit 0' into a `quit_ok' but erroneously
changed it into `check_space'. Fix this.
Signed-off-by: Ian Jackson
---
cr-ensure-disk-space | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cr-ensu
Hi All.
As suggested by Michael. I compiled the kernel as per
https://lkml.org/lkml/2018/2/23/59, containing the patch
https://lists.xenproject.org/archives/html/xen-devel/2018-02/msg00045.html.
Upon installing this fresh kernel, the machine booted fine with Xen
enabled (just needed an additional
flight 121765 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121765/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-intel 14 xen-boot/l1 fail REGR. vs. 120095
test-amd64-amd64-
On 05/04/18 15:42, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
>> On 05/04/18 15:00, Boris Ostrovsky wrote:
>>> On 04/05/2018 08:19 AM, Juergen Gross wrote:
On 05/04/18 12:06, George Dunlap wrote:
> Aren't there flags in the binary somewhere that could
> -Original Message-
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: 05 April 2018 10:32
> To: xen-devel@lists.xenproject.org; linux-ker...@vger.kernel.org;
> x...@kernel.org
> Cc: Paul Durrant ; Boris Ostrovsky
> ; Juergen Gross ; Thomas
> Gleixner ; Ingo Molnar
> Subject: [
> On 28 Mar 2018, at 16:40, George Dunlap wrote:
>
> On 03/22/2018 10:22 AM, Lars Kurth wrote:
>> Hi all,
>>
>> please find attached
>> a) Meeting details (just a link with timezones) – the meeting invite will
>> follow when we have an agenda
>> Bridge details – will be sent with the meetin
On Thu, Apr 05, 2018 at 02:04:18PM +0100, Ian Jackson wrote:
> Add four tests to most flights:
>
> test-amd64-amd64-xl-shadow
> test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow
> test-amd64-i386-xl-shadow
> test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow
>
> These are the same as
On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
> On 05/04/18 15:00, Boris Ostrovsky wrote:
>> On 04/05/2018 08:19 AM, Juergen Gross wrote:
>>> On 05/04/18 12:06, George Dunlap wrote:
>>>
Aren't there flags in the binary somewhere that could tell the
toolstack / Xen whether the kern
On 05/04/18 15:00, Boris Ostrovsky wrote:
> On 04/05/2018 08:19 AM, Juergen Gross wrote:
>> On 05/04/18 12:06, George Dunlap wrote:
>>
>>> Aren't there flags in the binary somewhere that could tell the
>>> toolstack / Xen whether the kernel in question needs the RSDP table in
>>> lowmem, or whether
Currently no callers pass these, so no functional change.
Signed-off-by: Ian Jackson
---
make-flight | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/make-flight b/make-flight
index 7cde5c2..1a8f0a6 100755
--- a/make-flight
+++ b/make-flight
@@ -396,9 +396,10 @@ do_hvm_de
Add four tests to most flights:
test-amd64-amd64-xl-shadow
test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow
test-amd64-i386-xl-shadow
test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow
These are the same as the corresponding ones without -shadow, except
that they set xen_boot_append
On 04/05/2018 08:19 AM, Juergen Gross wrote:
> On 05/04/18 12:06, George Dunlap wrote:
>
>> Aren't there flags in the binary somewhere that could tell the
>> toolstack / Xen whether the kernel in question needs the RSDP table in
>> lowmem, or whether it can be put higher?
> Not really. Analyzing th
CC Marek
On Thu, Apr 05, 2018 at 12:49:23PM +, Petre Eftime wrote:
> When 0-indexing, maximum index is num_entries - 1. The python xc library had a
> sign error where the minus was replaced by a plus, making tools that depended
> on it to look for CPUs that did not exist.
>
> Signed-off-by: P
When 0-indexing, maximum index is num_entries - 1. The python xc library had a
sign error where the minus was replaced by a plus, making tools that depended
on it to look for CPUs that did not exist.
Signed-off-by: Petre Eftime
---
tools/python/xen/lowlevel/xc/xc.c | 2 +-
1 file changed, 1 inse
On 05/04/18 11:03, Wei Liu wrote:
> On Thu, Apr 05, 2018 at 03:50:48AM +0200, Marek Marczykowski-Górecki wrote:
>> A few patches enabling build with gcc 8.
>>
>> Marek Marczykowski-Górecki (7):
>> tools/libxc: fix strncpy size
>> tools/misc: fix hypothetical buffer overflow in xen-lowmemd
>>
flight 121876 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121876/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
In some circumstances the trailing slash appears, in a way that is
outside our control. Eg some people with git submodules.
Signed-off-by: Ian Jackson
---
adhoc-revtuple-generator | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/adhoc-revtuple-generator b/adhoc-revtuple-gener
On 05/04/18 12:06, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 9:00 AM, Juergen Gross wrote:
>>> These are not just "patches to fix the issue", they are "patches to add
>>> new features" that touch core acpi bits, right? Support for new
>>> hardware and platforms and such are not normally part
Commit 4a5733771e6f33918eba07b584e564a67ac1 ("libxl: put RSDP for
PVH guest near 4GB") broke PVH guests with Linux kernels before 4.17
as those kernels are not taking the RSDP address from the PVH
start_info structure, but are searching it as on legacy system by
scanning low memory.
Add a quir
On Thu, Apr 05, 2018 at 11:08:59AM +0100, George Dunlap wrote:
>On 04/05/2018 10:59 AM, Roger Pau Monné wrote:
>> On Thu, Apr 05, 2018 at 10:52:09AM +0100, George Dunlap wrote:
>>> On 04/05/2018 10:46 AM, Roger Pau Monné wrote:
On Thu, Apr 05, 2018 at 10:40:37AM +0100, George Dunlap wrote:
>>>
On Thu, Apr 05, 2018 at 12:25:26PM +0100, Roger Pau Monné wrote:
>On Thu, Apr 05, 2018 at 07:00:41PM +0800, Chao Gao wrote:
>> On Thu, Apr 05, 2018 at 10:34:39AM +0100, Roger Pau Monné wrote:
>> >On Wed, Apr 04, 2018 at 11:29:39PM +0800, Chao Gao wrote:
>> >> diff --git a/xen/arch/x86/msi.c b/xen/a
On Thu, Apr 05, 2018 at 07:00:41PM +0800, Chao Gao wrote:
> On Thu, Apr 05, 2018 at 10:34:39AM +0100, Roger Pau Monné wrote:
> >On Wed, Apr 04, 2018 at 11:29:39PM +0800, Chao Gao wrote:
> >> diff --git a/xen/arch/x86/msi.c b/xen/arch/x86/msi.c
> >> index 5567990..2abf2cf 100644
> >> --- a/xen/arch/
On Thu, Apr 05, 2018 at 10:34:39AM +0100, Roger Pau Monné wrote:
>On Wed, Apr 04, 2018 at 11:29:39PM +0800, Chao Gao wrote:
>> ... the same page with other registers which are not relevant to MSI-X. Xen
>> marks pages where PBA resides as read-only. When assigning such devices to
>> guest, device d
The port of the ocaml libraries to the new safe-string interface
introduced some unnecessary copies between ocaml strings and bytes. The
bytes module provides unsafe conversion functions that avoid the copies
and are safe to use when the bytes are used immutably (as in Unix.write
calls) or when the
When xenstore was ported to the new safe-string interface, it mostly
happened by making copyies of string into bytes and back. The ideal
fix would be to rewrite all of the relevant interfaces to be uniformly
using bytes, but in the meanwhile we can improve the code by using unsafe
conversion funct
flight 121761 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121761/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 16 guest-localmigrate/x10 fail in
121704 pass in 121761
test-a
Hi,
On 05/04/18 11:16, Amit Singh Tomar wrote:
> This patch adds driver for UART controller found on Armada 3700 SoC.
>
> There is no reference manuals available for 3700 SoC in public and it
> is derived by looking at Linux driver[1].
>
> [1]https://github.com/torvalds/linux/blob/master/drivers
Hi Maran,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on next-20180405]
[cannot apply to tip/x86/core xen-tip/linux-next v4.16]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve
Hi,
On 05/04/18 11:16, Amit Singh Tomar wrote:
> Signed-off-by: Amit Singh Tomar
Reviewed-by: Andre Przywara
Cheers,
Andre.
> ---
> Changes since v2:
> * Addressed Andre's comments.
> Changes since v1:
> * Removed header file dependency.
> ---
> docs/misc/arm/early-printk.txt |
This patch adds driver for UART controller found on Armada 3700 SoC.
There is no reference manuals available for 3700 SoC in public and it
is derived by looking at Linux driver[1].
[1]https://github.com/torvalds/linux/blob/master/drivers/tty/serial/mvebu-uart.c
Signed-off-by: Amit Singh Tomar
-
This patch-set enables XEN booting[1] on ESPRESSObin board based
on Marvell Armada 3700 SoC.
I would like to Thanks Andre for helping on this.
[1]https://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/ESPRESSObin
Amit Singh Tomar (2):
xen/arm: Add MVEBU UART driver for Marvell Armada
Signed-off-by: Amit Singh Tomar
---
Changes since v2:
* Addressed Andre's comments.
Changes since v1:
* Removed header file dependency.
---
docs/misc/arm/early-printk.txt | 1 +
xen/arch/arm/Rules.mk | 1 +
xen/arch/arm/arm64/debug-mvebu.inc | 50 +++
On Thu, Apr 5, 2018 at 11:06 AM, George Dunlap wrote:
> The fact is, that as it stands, a user could have a perfectly working
> system with Xen 4.10 and a load of PVH guests running stock Linux
> 4.15, and then upgrade to Xen 4.11 and have all those guests break for
> no apparent reason. That's a
On 04/05/2018 10:59 AM, Roger Pau Monné wrote:
> On Thu, Apr 05, 2018 at 10:52:09AM +0100, George Dunlap wrote:
>> On 04/05/2018 10:46 AM, Roger Pau Monné wrote:
>>> On Thu, Apr 05, 2018 at 10:40:37AM +0100, George Dunlap wrote:
On 04/05/2018 10:34 AM, Roger Pau Monné wrote:
> On Wed, Apr
On Thu, Apr 5, 2018 at 9:00 AM, Juergen Gross wrote:
>> These are not just "patches to fix the issue", they are "patches to add
>> new features" that touch core acpi bits, right? Support for new
>> hardware and platforms and such are not normally part of the stable
>> kernel patches at all (with
On Thursday, 5 April 2018 7:19:15 PM AEST Ian Jackson wrote:
> Steven Haigh writes ("Re: Problem with Xen 4.7.5"):
> > On 2018-04-05 03:22, Ian Jackson wrote:
> > > Apologies for the inconvenience.
>
> ...
>
> > I'm wondering if the severity of this is high enough that I should
> > withdraw the 4
]
url:
https://github.com/0day-ci/linux/commits/Maran-Wilson/KVM-x86-Allow-Qemu-KVM-to-use-PVH-entry-point/20180405-165048
config: i386-randconfig-x019-201813 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
On Thu, Apr 05, 2018 at 10:52:09AM +0100, George Dunlap wrote:
> On 04/05/2018 10:46 AM, Roger Pau Monné wrote:
> > On Thu, Apr 05, 2018 at 10:40:37AM +0100, George Dunlap wrote:
> >> On 04/05/2018 10:34 AM, Roger Pau Monné wrote:
> >>> On Wed, Apr 04, 2018 at 11:29:39PM +0800, Chao Gao wrote:
> >>
On 04/05/2018 10:46 AM, Roger Pau Monné wrote:
> On Thu, Apr 05, 2018 at 10:40:37AM +0100, George Dunlap wrote:
>> On 04/05/2018 10:34 AM, Roger Pau Monné wrote:
>>> On Wed, Apr 04, 2018 at 11:29:39PM +0800, Chao Gao wrote:
... the same page with other registers which are not relevant to MSI-X
On Thu, Apr 05, 2018 at 10:40:37AM +0100, George Dunlap wrote:
> On 04/05/2018 10:34 AM, Roger Pau Monné wrote:
> > On Wed, Apr 04, 2018 at 11:29:39PM +0800, Chao Gao wrote:
> >> ... the same page with other registers which are not relevant to MSI-X. Xen
> >> marks pages where PBA resides as read-o
On 04/05/2018 10:34 AM, Roger Pau Monné wrote:
> On Wed, Apr 04, 2018 at 11:29:39PM +0800, Chao Gao wrote:
>> ... the same page with other registers which are not relevant to MSI-X. Xen
>> marks pages where PBA resides as read-only. When assigning such devices to
>> guest, device driver writes MSI-
Hi,
On 02/04/18 12:17, Manish Jaggi wrote:
On 04/02/2018 04:33 PM, Manish Jaggi wrote:
On 03/27/2018 03:48 PM, Marc Zyngier wrote:
On 27/03/18 10:07, Manish Jaggi wrote:
This patch is ported to xen from linux commit
b6f49035b4bf6e2709f2a5fed3107f5438c1fd02
KVM: arm64: vgic-v3: Add ICV_EOIR
On Wed, Apr 04, 2018 at 11:29:39PM +0800, Chao Gao wrote:
> ... the same page with other registers which are not relevant to MSI-X. Xen
> marks pages where PBA resides as read-only. When assigning such devices to
> guest, device driver writes MSI-X irrelevant registers on those pages would
> lead t
My recent Xen patch series introduces a new HYPERVISOR_memory_op to
support direct priv-mapping of certain guest resources (such as ioreq
pages, used by emulators) by a tools domain, rather than having to access
such resources via the guest P2M.
This patch adds the necessary infrastructure to the
Steven Haigh writes ("Re: Problem with Xen 4.7.5"):
> On 2018-04-05 03:22, Ian Jackson wrote:
> > Apologies for the inconvenience.
...
> I'm wondering if the severity of this is high enough that I should
> withdraw the 4.7.5 packages from my repos.
>
> Is this a show-stopper? Security issue? Dom0
On 20/03/18 20:24, Brijen Raval wrote:
Hello Julien,
Hello,
As requested I am moving the conversation to email from IRC
To summarize my setup:
1. I am running a custom kernel on QEMU ARM64(without KVM) on my linux
machine
2. I have my custom implementation of Hypervisor
3. I am trying to
On Thu, Apr 05, 2018 at 03:50:48AM +0200, Marek Marczykowski-Górecki wrote:
> A few patches enabling build with gcc 8.
>
> Marek Marczykowski-Górecki (7):
> tools/libxc: fix strncpy size
> tools/misc: fix hypothetical buffer overflow in xen-lowmemd
> tools/blktap2: fix hypothetical buffer ov
On 05/04/18 09:14, Greg KH wrote:
> On Thu, Apr 05, 2018 at 09:02:27AM +0200, Juergen Gross wrote:
>> On 05/04/18 08:33, Greg KH wrote:
>>> On Wed, Apr 04, 2018 at 06:32:17PM +0200, Juergen Gross wrote:
On 04/04/18 17:42, Greg KH wrote:
> On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen G
On 05/04/18 09:11, Juergen Gross wrote:
> On 03/04/18 18:55, Sander Eikelenboom wrote:
>> On 03/04/18 12:29, Juergen Gross wrote:
>>> On 03/04/18 12:19, osstest service owner wrote:
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-pvhv2-amd
testid guest-start
>
On Thu, Apr 05, 2018 at 09:02:27AM +0200, Juergen Gross wrote:
> On 05/04/18 08:33, Greg KH wrote:
> > On Wed, Apr 04, 2018 at 06:32:17PM +0200, Juergen Gross wrote:
> >> On 04/04/18 17:42, Greg KH wrote:
> >>> On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen Gross wrote:
> On 04/04/18 16:46,
On 03/04/18 18:55, Sander Eikelenboom wrote:
> On 03/04/18 12:29, Juergen Gross wrote:
>> On 03/04/18 12:19, osstest service owner wrote:
>>> branch xen-unstable
>>> xenbranch xen-unstable
>>> job test-amd64-amd64-xl-pvhv2-amd
>>> testid guest-start
>>>
>>> Tree: linux
>>> git://git.kernel.org/pub
flight 121758 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121758/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-xtf-amd64-amd64-5 50 xtf/test-hvm64-lbr-tsx-vmentry fail like 121093
test-armhf-armhf-xl-rtds 16 g
On 05/04/18 08:33, Greg KH wrote:
> On Wed, Apr 04, 2018 at 06:32:17PM +0200, Juergen Gross wrote:
>> On 04/04/18 17:42, Greg KH wrote:
>>> On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen Gross wrote:
On 04/04/18 16:46, Greg KH wrote:
> On Wed, Apr 04, 2018 at 04:30:30PM +0200, Juergen G
99 matches
Mail list logo
