flight 131678 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131678/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131681 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131681/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 7b6e05c50fc39466fcc685fb6d4216f99af58743
baseline version:
xen ae7f
On Mon, Dec 31, 2018 at 05:35:21PM +, Andrew Cooper wrote:
> When the command line parsing was updated to use const strings and no longer
> tokenise with NUL characters, string matches could no longer be made with
> strcmp().
>
> Unfortunately, the replacement was buggy. strncmp(s, "opt", ss
On Mon, Dec 31, 2018 at 05:34:25PM +, Andrew Cooper wrote:
> A NT_GNU_BUILD_ID with namesz longer than 4 will cause the strncmp() to use
> bytes in adjacent stringtable entries.
>
> Instead, check for namesz exactly equal to 4, and use memcmp() with an
> explicit size.
>
> Signed-off-by: Andr
On Mon, Dec 31, 2018 at 05:34:25PM +, Andrew Cooper wrote:
> A NT_GNU_BUILD_ID with namesz longer than 4 will cause the strncmp() to use
> bytes in adjacent stringtable entries.
>
> Instead, check for namesz exactly equal to 4, and use memcmp() with an
> explicit size.
>
> Signed-off-by: Andr
flight 131683 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131683/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
On Wed, Dec 19, 2018 at 08:52:05PM +0200, Petre Pircalabu wrote:
> Define the type for each of the supported vm_event rings (paging,
> monitor and sharing) and replace the ring param field with this type.
>
> Replace XEN_DOMCTL_VM_EVENT_OP_ occurrences with their corresponding
> XEN_VM_EVENT_TYPE_
On Thu, Dec 20, 2018 at 09:15:57PM +0800, Pu Wen wrote:
> Add Hygon Dhyana support to caculate the cpuid policies for creating PV
> or HVM guest by using the code path of AMD.
>
> Signed-off-by: Pu Wen
Piggy-backing on AMD code is fine at this stage:
Acked-by: Wei Liu
This work started to fix a regression introduced by c/s a3a99df44
"docs/cmdline: Rewrite the cpuid_mask_* section" which has broken the
formatting of xen-command-line.html on xenbits.xen.org/docs.
It developed into several swamps of work...
Andrew Cooper (4):
docs/pandoc: Don't escape underscor
The original intent of this patch was to rename xen-vbd-interface.markdown.7
to xen-vbd-interface.pandoc.7 to remove the final markdown file from the docs/
tree.
The DOC_MANx lists are broken. They contain MANxSRC-y twice, the first half
with a partial %.pod substituation, and the second half wit
Pandoc deliberately (and contrary to markdown) doesn't treat underscores in
the middle of normal text as emphasis markers, as this is almost always the
unhelpful interpretation.
For text which is emphasised using _, an underscore in the middle is
interpreted, but the emphasis marker can be switche
Now that all use of markdown as been replaced with pandoc, drop it from
configure.ac and from the docs/ Makefile.
Instead of just deleting the markdown reference from README, adjust the line
to mention the other optional packages required for documentation.
Drop markdown from travis and the docke
c/s a3a99df44 "docs/cmdline: Rewrite the cpuid_mask_* section" completely
forgot about how markdown gets rendered to HTML (as opposed to PDF), because
we use different translators depending on the destination format.
markdown and pandoc are very similar markup languages, but a couple of details
ab
Where is 1/2 in this series?
On Tue, Dec 18, 2018 at 10:43:38PM +0800, Chao Gao wrote:
> When I destroyed a guest with 'xl destroy', I found the warning
> in msi_set_mask_bit() in Xen was triggered. After adding "WARN_ON(1)"
> to that place, I got the call trace below:
>
> (XEN) Xen call trace:
>
On Tue, Dec 18, 2018 at 05:11:44PM +0200, Razvan Cojocaru wrote:
> Allow altp2m users to disable #VE/VMFUNC alone. Currently it is
> only possible to disable this functionality when we disable altp2m
> completely; #VE/VMFUNC can only be enabled once per altp2m session.
>
> In addition to making th
On Thu, Dec 20, 2018 at 11:29:35PM +0800, Chao Gao wrote:
> When I destroyed a guest with 'xl destroy', I found the warning
> in msi_set_mask_bit() in Xen was triggered. After adding "WARN_ON(1)"
> to that place, I got the call trace below:
>
> (XEN) Xen call trace:
> (XEN)[] msi.c#msi_set_mas
On 02/01/2019 10:43, Wei Liu wrote:
> On Mon, Dec 31, 2018 at 05:34:25PM +, Andrew Cooper wrote:
>> A NT_GNU_BUILD_ID with namesz longer than 4 will cause the strncmp() to use
>> bytes in adjacent stringtable entries.
>>
>> Instead, check for namesz exactly equal to 4, and use memcmp() with an
flight 131684 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131684/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
Coverity understandably complains that get_reaper_lock_and_uid leaks
the fd and hence open-file. But this is intentional: the lock becomes
owned by the child process as a whole, which is entirely the property
of libxl.
(The coding style here in this subprocess is a bit anomalous but it's
probably
On Mon, Dec 24, 2018 at 09:04:35AM +0100, Roger Pau Monné wrote:
> On Fri, Dec 21, 2018 at 06:37:32PM +, George Dunlap wrote:
> >
> >
> > > On Dec 21, 2018, at 9:41 AM, Roger Pau Monne wrote:
> > >
> > > paging_log_dirty_op function takes mm locks from a subject domain and
> > > then attemp
On Fri, Dec 21, 2018 at 01:46:05PM +, Andrew Cooper wrote:
> All of this code lives inside CONFIG_PV which means gfn == mfn, and the
> fill_ro_mpt() calls clearly show that the value is used untranslated.
>
> Change cr3_gfn to a suitably typed cr3_mfn, and replace get_page_from_gfn()
> with a
On 02/01/2019 10:13, Roger Pau Monné wrote:
> On Mon, Dec 31, 2018 at 05:35:21PM +, Andrew Cooper wrote:
>> When the command line parsing was updated to use const strings and no longer
>> tokenise with NUL characters, string matches could no longer be made with
>> strcmp().
>>
>> Unfortunately,
On Mon, Dec 24, 2018 at 11:17:57AM +, Julien Grall wrote:
> (+ Wei and Ian)
>
> Hi Stefano,
>
> On 12/5/18 5:28 PM, Stefano Stabellini wrote:
> > Read the dtb fragment corresponding to a passthrough device from memory
> > at the location referred to by the "multiboot,dtb" compatible node.
> >
On Wed, Dec 26, 2018 at 01:20:24PM +0200, Andrii Anisov wrote:
> From: Andrii Anisov
>
> Simplify context restore from idle vcpu to the one ran before it.
> This improves low cpu load but high irq rate use-cases.
>
> Signed-off-by: Andrii Anisov
Can this be put under arch_vcpu instead? It has
On Wed, Jan 02, 2019 at 12:18:27PM +, Andrew Cooper wrote:
> On 02/01/2019 10:13, Roger Pau Monné wrote:
> > On Mon, Dec 31, 2018 at 05:35:21PM +, Andrew Cooper wrote:
> >> When the command line parsing was updated to use const strings and no
> >> longer
> >> tokenise with NUL characters,
Andrew Cooper writes ("[PATCH 1/4] docs/pandoc: Don't escape underscores in the
middle of text"):
> Pandoc deliberately (and contrary to markdown) doesn't treat underscores in
> the middle of normal text as emphasis markers, as this is almost always the
> unhelpful interpretation.
>
> For text wh
Andrew Cooper writes ("[PATCH 4/4] docs: Remove Markdown from configure.ac and
the build instructions"):
> Now that all use of markdown as been replaced with pandoc, drop it from
> configure.ac and from the docs/ Makefile.
>
> Instead of just deleting the markdown reference from README, adjust th
On 02/01/2019 12:25, Roger Pau Monné wrote:
> On Wed, Jan 02, 2019 at 12:18:27PM +, Andrew Cooper wrote:
>> On 02/01/2019 10:13, Roger Pau Monné wrote:
>>> On Mon, Dec 31, 2018 at 05:35:21PM +, Andrew Cooper wrote:
When the command line parsing was updated to use const strings and no
On 1/2/19 1:50 PM, Wei Liu wrote:
> On Tue, Dec 18, 2018 at 05:11:44PM +0200, Razvan Cojocaru wrote:
>> Allow altp2m users to disable #VE/VMFUNC alone. Currently it is
>> only possible to disable this functionality when we disable altp2m
>> completely; #VE/VMFUNC can only be enabled once per altp2m
Andrew Cooper writes ("[PATCH 2/4] docs/markdown: Switch to using pandoc, and
fix underscore escaping"):
> c/s a3a99df44 "docs/cmdline: Rewrite the cpuid_mask_* section" completely
> forgot about how markdown gets rendered to HTML (as opposed to PDF), because
> we use different translators dependi
On 02/01/2019 11:50, Wei Liu wrote:
> On Tue, Dec 18, 2018 at 05:11:44PM +0200, Razvan Cojocaru wrote:
>> Allow altp2m users to disable #VE/VMFUNC alone. Currently it is
>> only possible to disable this functionality when we disable altp2m
>> completely; #VE/VMFUNC can only be enabled once per altp
Andrew Cooper writes ("[PATCH 3/4] docs/man: Fix/simplify generation of
manpages"):
> The DOC_MANx lists are broken. They contain MANxSRC-y twice, the first half
> with a partial %.pod substituation, and the second half with a partial
> %.markdown substitution. This is also the root cause behind
On 1/2/19 2:29 PM, Andrew Cooper wrote:
> On 02/01/2019 11:50, Wei Liu wrote:
>> On Tue, Dec 18, 2018 at 05:11:44PM +0200, Razvan Cojocaru wrote:
>>> Allow altp2m users to disable #VE/VMFUNC alone. Currently it is
>>> only possible to disable this functionality when we disable altp2m
>>> completely
On Fri, Dec 28, 2018 at 12:18:57PM +0100, Roger Pau Monne wrote:
> Add a verbose option to the dom0 command line, so that dom0 builder
> can print extra debug information when required.
>
> Use this new verbose mode to print statistics about memory allocations
> when populating dom0 p2m.
>
> Sign
Replace all the TABs with spaces.
Signed-off-by: Razvan Cojocaru
---
tools/libxc/xc_altp2m.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/tools/libxc/xc_altp2m.c b/tools/libxc/xc_altp2m.c
index e61bacf..a86520c 100644
--- a/tools/libxc/xc_altp2m.c
+++ b/to
On 02/01/2019 12:30, Ian Jackson wrote:
> Andrew Cooper writes ("[PATCH 3/4] docs/man: Fix/simplify generation of
> manpages"):
>> The DOC_MANx lists are broken. They contain MANxSRC-y twice, the first half
>> with a partial %.pod substituation, and the second half with a partial
>> %.markdown su
On Fri, Dec 28, 2018 at 01:04:03PM +0100, Roger Pau Monne wrote:
> This implies there's no need to forcefully reserve the VGA MMIO
> region, since the memory map provided will be correct.
>
> Reported-by: Andrew Cooper
> Signed-off-by: Roger Pau Monné
Reviewed-by: Wei Liu
On Fri, Dec 28, 2018 at 01:04:02PM +0100, Roger Pau Monne wrote:
> And instead use the newly introduced e820_remove_range helper to
> remove any RAM region from the low 1MB VGA/ROM region afterwards.
>
> No functional change intended.
>
> Signed-off-by: Roger Pau Monné
Reviewed-by: Wei Liu
__
On Wed, Jan 02, 2019 at 12:35:17PM +, Wei Liu wrote:
> On Fri, Dec 28, 2018 at 12:18:57PM +0100, Roger Pau Monne wrote:
> > Add a verbose option to the dom0 command line, so that dom0 builder
> > can print extra debug information when required.
> >
> > Use this new verbose mode to print statis
On Fri, Dec 28, 2018 at 12:39:32PM +, Andrew Cooper wrote:
> Future changes are going to want to use cpu_bug_* in a mannor similar to
mannor -> manner.
Wei.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mail
On Wed, Jan 02, 2019 at 01:48:43PM +0100, Roger Pau Monné wrote:
> On Wed, Jan 02, 2019 at 12:35:17PM +, Wei Liu wrote:
> > On Fri, Dec 28, 2018 at 12:18:57PM +0100, Roger Pau Monne wrote:
> > > Add a verbose option to the dom0 command line, so that dom0 builder
> > > can print extra debug info
On Fri, Dec 28, 2018 at 12:39:34PM +, Andrew Cooper wrote:
> AMD processors don't clear the base or limit fields when loading a NULL
> segment, and Hygon processors inherit this behaviour.
>
> Express the logic in terms of cpu_bug_null_seg, and rearrange
> preload_segment() have the more predi
On Fri, Dec 28, 2018 at 12:39:35PM +, Andrew Cooper wrote:
> AMD hardware before Zen doesn't safe/restore the FPU error pointers
safe -> save.
Wei.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listi
On Fri, Dec 21, 2018 at 08:03:49PM +, Liam Merwick wrote:
> diff --git a/include/hw/elf_ops.h b/include/hw/elf_ops.h
> index 74679ff8da3a..37d20a3800c1 100644
> --- a/include/hw/elf_ops.h
> +++ b/include/hw/elf_ops.h
> @@ -266,6 +266,7 @@ fail:
> }
>
> static int glue(load_elf, SZ)(const ch
On Fri, Dec 21, 2018 at 08:03:50PM +, Liam Merwick wrote:
> +while (note_type != elf_note_type) {
> +nhdr_namesz = nhdr->n_namesz;
> +nhdr_descsz = nhdr->n_descsz;
> +
> +elf_note_entry_offset = nhdr_size +
> +QEMU_ALIGN_UP(nhdr_namesz, phdr_align) +
> +
On Fri, Dec 21, 2018 at 08:03:52PM +, Liam Merwick wrote:
> @@ -1336,7 +1470,7 @@ void pc_memory_init(PCMachineState *pcms,
> int linux_boot, i;
> MemoryRegion *ram, *option_rom_mr;
> MemoryRegion *ram_below_4g, *ram_above_4g;
> -FWCfgState *fw_cfg;
> +FWCfgState *fw_cfg
I think you've called get_maintainers.pl on the wrong files -- it is not
applicable to xtf.git.
Wei.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
flight 131682 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131682/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
freebsd b65ae50c2b44f3e341ab70a5aa9c658630877191
baseline version:
freebsd 9e724bf2b7e
On Fri, Dec 28, 2018 at 08:42:41PM +0200, Petre Pircalabu wrote:
> This class starts alongside the domain a monitor application which opens
> an event channel corresponding to that domain and handles the received
> requests.
> Use the "monitor_args" key to pass test specific arguments to the
> moni
On Wed, Jan 02, 2019 at 02:42:25PM +0200, Razvan Cojocaru wrote:
> Replace all the TABs with spaces.
>
> Signed-off-by: Razvan Cojocaru
Acked-by: Wei Liu
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/l
flight 131669 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131669/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-rumprun-amd64 7 xen-boot fail REGR. vs. 125898
test-amd64-amd64-xl
flight 131679 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131679/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 131516
test-armhf-armhf-libvirt-raw 13 saveresto
On Wed, Jan 02, 2019 at 12:03:43PM +, Ian Jackson wrote:
> Coverity understandably complains that get_reaper_lock_and_uid leaks
> the fd and hence open-file. But this is intentional: the lock becomes
> owned by the child process as a whole, which is entirely the property
> of libxl.
>
> (The
On Wed, Dec 12, 2018 at 02:53:46PM +, Anthony PERARD wrote:
> Callbacks should be in the order that there are going to be executed.
> This patch fix the initiate_domain_create callbacks, and also reorder
> the callbacks prototytes. That way, it's easier to follow the flow.
Two typos here. I wi
flight 131686 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131686/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
flight 131670 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131670/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 131660
test-amd64-amd64-xl-qemuu-win7-amd64
Andrew Cooper writes ("Re: [PATCH 3/4] docs/man: Fix/simplify generation of
manpages"):
> I'm fairly sure I haven't touched anything which affects -j-safety.
>
> The only content which has changed is to lose the mal-substituted origin
> source files from DOC_MANx. These caused unnecessary depend
flight 131685 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131685/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
On 02/01/2019 11:43, Andrew Cooper wrote:
> Now that all use of markdown as been replaced with pandoc, drop it from
> configure.ac and from the docs/ Makefile.
>
> Instead of just deleting the markdown reference from README, adjust the line
> to mention the other optional packages required for docu
On Thu, Dec 20, 2018 at 04:33:39PM +, Paul Durrant wrote:
>
> void viridian_vcpu_deinit(struct vcpu *v)
> {
> -viridian_synic_wrmsr(v, HV_X64_MSR_VP_ASSIST_PAGE, 0);
> +if ( !v->arch.hvm.viridian )
> +return;
> +
> +if ( is_viridian_vcpu(v) )
> +viridian_synic_wr
On Thu, Dec 20, 2018 at 04:33:44PM +, Paul Durrant wrote:
> ...from arch_domain_shutdown/pause/unpause().
>
> A subsequent patch will introduce an implementaion of synthetic timers
> which will also need freeze/thaw hooks, so make the exported hooks more
> generic and call through to (re-named
On Thu, Dec 20, 2018 at 04:33:38PM +, Paul Durrant wrote:
> This patch adds domain and vcpu init hooks for viridian features. The init
> hooks do not yet do anything; they will be added to by subsequent patches.
>
> Signed-off-by: Paul Durrant
Reviewed-by: Wei Liu
_
On Thu, Dec 20, 2018 at 04:33:40PM +, Paul Durrant wrote:
> diff --git a/xen/arch/x86/hvm/viridian/viridian.c
> b/xen/arch/x86/hvm/viridian/viridian.c
> index e200e2ed1d..4c0f04df8c 100644
> --- a/xen/arch/x86/hvm/viridian/viridian.c
> +++ b/xen/arch/x86/hvm/viridian/viridian.c
> @@ -424,6 +42
On Thu, Dec 20, 2018 at 04:33:43PM +, Paul Durrant wrote:
> This patch introduces an implementation of the SCONTROL, SVERSION, SIEFP,
> SIMP, EOM and SINT0-15 SynIC MSRs. No message source is added and, as such,
> nothing will yet generate a synthetic interrupt. A subsequent patch will
> add an
On Thu, Dec 20, 2018 at 04:33:42PM +, Paul Durrant wrote:
> Whilst the reference tsc page does not currently need to be kept mapped
> after it is initially set up (or updated after migrate), the code can
> be simplified by using the common guest page map/unmap and dump functions.
> New function
On Thu, Dec 20, 2018 at 04:33:41PM +, Paul Durrant wrote:
> Currently the time module lacks vcpu context save helpers and the synic
> module lacks domain context save helpers. These helpers are not yet
> required but subsequent patches will require at least some of them so this
> patch complete
On 20/12/2018 16:33, Paul Durrant wrote:
> This patch adds domain and vcpu init hooks for viridian features. The init
> hooks do not yet do anything; they will be added to by subsequent patches.
>
> Signed-off-by: Paul Durrant
Please can we start by fixing the current, broken, initialisation and
On 12/21/18 6:06 PM, Stefano Stabellini wrote:
> Hi all,
>
> This series is a collection of small pvcalls fixes.
>
> Cheers,
>
> Stefano
>
>
> Stefano Stabellini (5):
> pvcalls-front: read all data before closing the connection
> pvcalls-front: don't try to free unallocated rings
>
On Mon, Dec 31, Andrew Cooper wrote:
> * tbuf_size and tevt_mask
> Given that xentrace can set them at runtime, and it is debugging
> functionality, I don't see a plausible use the command line options at all.
'tbuf_size=-1 dom0_mem=N' collects events during boot.
xenalyze is (or was) unable to p
flight 131690 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131690/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
On 02/01/2019 16:56, Olaf Hering wrote:
> On Mon, Dec 31, Andrew Cooper wrote:
>
>> * tbuf_size and tevt_mask
>> Given that xentrace can set them at runtime, and it is debugging
>> functionality, I don't see a plausible use the command line options at all.
> 'tbuf_size=-1 dom0_mem=N' collects event
On Mon, Dec 31, 2018 at 12:43:39PM +, Andrew Cooper wrote:
> On 03/12/2018 09:56, Jan Beulich wrote:
> On 30.11.18 at 19:01, wrote:
> >> On Fri, Nov 30, 2018 at 05:09:42PM +, Ian Jackson wrote:
> >>> Wei Liu writes ("[PATCH v2 0/3] Remove tmem"):
> It is agreed that tmem can be r
On 02/01/2019 16:08, Andrew Cooper wrote:
> On 20/12/2018 16:33, Paul Durrant wrote:
>> This patch adds domain and vcpu init hooks for viridian features. The init
>> hooks do not yet do anything; they will be added to by subsequent patches.
>>
>> Signed-off-by: Paul Durrant
> Please can we start b
flight 131689 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131689/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
On Tue, 13 Nov 2018, Jan Beulich wrote:
> >>> On 13.11.18 at 00:06, wrote:
> > --- a/xen/arch/x86/alternative.c
> > +++ b/xen/arch/x86/alternative.c
> > @@ -194,7 +194,7 @@ void init_or_livepatch apply_alternatives(struct
> > alt_instr *start,
> > * So be careful if you want to change the s
On Wed, 14 Nov 2018, Jan Beulich wrote:
> >>> On 13.11.18 at 23:02, wrote:
> > On Tue, 13 Nov 2018, Jan Beulich wrote:
> >> >>> On 13.11.18 at 14:17, wrote:
> >> > On 13/11/2018 12:56, Jan Beulich wrote:
> >> > On 13.11.18 at 00:06, wrote:
> >> >>> @@ -33,8 +33,8 @@ static int init_percpu_ar
flight 131692 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131692/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 131689
build-armhf
On 26/12/2018 11:20, Andrii Anisov wrote:
> From: Andrii Anisov
>
> This patch series is an attempt to reduce IRQ latency with the
> old GIC implementation (gic-vgic). These patches originally based
> on XEN 4.10 release. The motivation was to improve benchmark
> results of a system given to a cu
The misc/xen-command-line.markdown reference in configure.ac should have been
updated in the same changeset.
Signed-off-by: Andrew Cooper
---
CC: George Dunlap
CC: Ian Jackson
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC: Stefano Stabellini
CC: Tim Deegan
CC: Wei Liu
CC: Julien Grall
---
On Mon, Dec 24, 2018 at 6:53 PM Souptick Joarder wrote:
>
> Convert to use vm_insert_range() to map range of kernel
> memory to user vma.
>
> Signed-off-by: Souptick Joarder
> Reviewed-by: Matthew Wilcox
> Reviewed-by: Boris Ostrovsky
> ---
> drivers/xen/gntdev.c | 11 ---
> 1 file cha
On 1/2/19 1:58 PM, Souptick Joarder wrote:
> On Mon, Dec 24, 2018 at 6:53 PM Souptick Joarder wrote:
>> Convert to use vm_insert_range() to map range of kernel
>> memory to user vma.
>>
>> Signed-off-by: Souptick Joarder
>> Reviewed-by: Matthew Wilcox
>> Reviewed-by: Boris Ostrovsky
>> ---
>>
On Wed, Jan 02, 2019 at 06:53:00PM +, Andrew Cooper wrote:
> The misc/xen-command-line.markdown reference in configure.ac should have been
> updated in the same changeset.
>
> Signed-off-by: Andrew Cooper
Acked-by: Wei Liu
___
Xen-devel mailing l
flight 131694 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131694/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 131689
build-armhf
On Wed, 2 Jan 2019, Stefano Stabellini wrote:
> On Tue, 13 Nov 2018, Jan Beulich wrote:
> > >>> On 13.11.18 at 00:06, wrote:
> > > --- a/xen/arch/x86/alternative.c
> > > +++ b/xen/arch/x86/alternative.c
> > > @@ -194,7 +194,7 @@ void init_or_livepatch apply_alternatives(struct
> > > alt_instr *st
branch xen-unstable-smoke
xenbranch xen-unstable-smoke
job build-amd64
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: d6
flight 131673 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131673/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-examine 8 reboot fail REGR. vs. 128858
test-amd64-i386-qemu
On Tue, 11 Dec 2018, Daniel wrote:
> On Tue, Dec 11, 2018 at 10:34:52AM +, Peter Maydell wrote:
> > On Tue, 25 Apr 2017 at 19:35, Stefano Stabellini
> > wrote:
> > >
> > > From: Juergen Gross
> > >
> > > Instead of trying to guess the Xen version to use by compiling various
> > > test progra
> +static int mem_access_init()
> +{
> +int rc = 0;
> +mem_access_monitor_t *pmon = (mem_access_monitor_t *)monitor;
> +
> +if ( !pmon )
> +return -EINVAL;
> +
> +rc = xc_domain_set_access_required(monitor->xch, monitor->domain_id, 1);
> +if ( rc < 0 )
> +{
> +
flight 131675 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131675/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 7 xen-boot fail REGR. vs. 129313
test-amd64-amd64-xl-
On Mon, 24 Dec 2018, Julien Grall wrote:
> (+ Wei and Ian)
>
> Hi Stefano,
>
> On 12/5/18 5:28 PM, Stefano Stabellini wrote:
> > Read the dtb fragment corresponding to a passthrough device from memory
> > at the location referred to by the "multiboot,dtb" compatible node.
> >
> > Copy the fragme
flight 131702 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131702/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
On Mon, 24 Dec 2018, Julien Grall wrote:
> Hi,
>
> On 12/5/18 5:28 PM, Stefano Stabellini wrote:
> > Detect "multiboot,dtb" compatible nodes. Add them to the bootmod array
> > as BOOTMOD_DTB. In kernel_probe, find the right BOOTMOD_DTB and store a
> > pointer to it in dtb_bootmodule.
>
> This is
Fix device assignment on ARM after 91d4eca7 "mm / iommu: split
need_iommu() into has_iommu_pt() and need_iommu_pt_sync()".
arch_iommu_populate_page_table returns -ENOSYS which causes
iommu_construct to return early, although it is not an error.
Interestingly, the if ( rc ) was present even before
On 03/01/2019 00:28, Stefano Stabellini wrote:
> Fix device assignment on ARM after 91d4eca7 "mm / iommu: split
> need_iommu() into has_iommu_pt() and need_iommu_pt_sync()".
>
> arch_iommu_populate_page_table returns -ENOSYS which causes
> iommu_construct to return early, although it is not an erro
flight 131691 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131691/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131680 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131680/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 7 xen-boot fail REGR. vs. 131659
test-amd64-amd64-xl-
96 matches
Mail list logo
