flight 92767 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92767/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 92382
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
arch/arm64/kernel/setup.c
between commit:
3194ac6e66cc ("arm64: Move unflatten_device_tree() call earlier.")
from the arm64 tree and commit:
3915fea959b6 ("ARM: XEN: Move xen_early_init() before efi_init()")
from
just for debug.
'xl debug-key q' do not dump d->tot_pages,
so it hard to understand p2m_pod_set_mem_target.
Signed-off-by: zhangcy
---
xen/arch/x86/mm/p2m-pod.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xen/arch/x86/mm/p2m-pod.c
On 2016/4/25 21:26, Ian Jackson wrote:
Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [PATCH] Fix cpumap setting before
passing to XEN"):
On Wed, Apr 20, 2016 at 03:33:13PM +0100, Wei Liu wrote:
In principle I think having python binding and xl/libxl behave more or less
the same is the right
flight 92720 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92720/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 3 host-install(3) broken REGR. vs. 92651
On April 25, 2016 5:22 PM, Jan Beulich wrote:
> >>> On 18.04.16 at 16:00, wrote:
> > --- a/xen/drivers/passthrough/vtd/iommu.c
> > +++ b/xen/drivers/passthrough/vtd/iommu.c
> > @@ -558,14 +558,16 @@ static void iommu_flush_all(void)
> > }
> > }
> >
> >
Hi Dario and all,
When RTDS scheduler is initialized, it will print out that the
scheduler is an experimental feature with the following lines:
printk("Initializing RTDS scheduler\n"
"WARNING: This is experimental software in development.\n"
"Use at your own
On April 25, 2016 5:22 PM, Jan Beulich wrote:
> >>> On 18.04.16 at 16:00, wrote:
>
> I thought we had agreed on best effort flushing when an error occurs. That
> means you shouldn't break out of the loop here, but accumulate errors.
> (Breaking out of the
flight 92725 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92725/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REGR. vs.
flight 92732 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92732/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
flight 92701 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92701/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 92382
Sadly I only have little nitpicks. Feel free to ignore them.
> diff --git a/xen/arch/x86/mm/mem_sharing.c b/xen/arch/x86/mm/mem_sharing.c
> index a522423..d5b4b2d 100644
> --- a/xen/arch/x86/mm/mem_sharing.c
> +++ b/xen/arch/x86/mm/mem_sharing.c
> @@ -35,6 +35,7 @@
> #include
> #include
>
On 04/25/2016 02:32 PM, Konrad Rzeszutek Wilk wrote:
On Tue, Apr 19, 2016 at 10:11:28AM +0100, Andrew Cooper wrote:
On 19/04/16 10:02, Doug Goldstein wrote:
On 4/18/16 12:20 PM, Lars Kurth wrote:
Hi all,
CC-ing XSM maintainer :-)
Thanks. I'm going to comment on this and the wiki.
[...]
This is a note to let you know that I have just added a patch titled
x86/mm/xen: Suppress hugetlbfs in PV guests
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-4.2.y-queue
This
flight 92731 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92731/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 13
On Wed, Apr 20, 2016 at 12:06:48PM +0200, Paulina Szubarczyk wrote:
> On Fri, 2016-04-01 at 15:35 +0200, Roger Pau Monné wrote:
> > Please don't top post, it breaks the flow of the conversation.
> >
> > I'm also adding Anthony (one of the QEMU/Xen maintainers).
> > On Fri, 1 Apr 2016, Paulina
flight 92668 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92668/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
test-amd64-amd64-xl
On Tue, Apr 19, 2016 at 10:11:28AM +0100, Andrew Cooper wrote:
> On 19/04/16 10:02, Doug Goldstein wrote:
> >On 4/18/16 12:20 PM, Lars Kurth wrote:
> >>Hi all,
CC-ing XSM maintainer :-)
> >>
> >>I took notes as much as I could. CC'ed the people who participated most. If
> >>I
On Mon, Apr 18, 2016 at 10:29:51AM +0100, Julien Grall wrote:
> UP guest usually uses TLB instruction to flush only on the local CPU. The
> TLB flush won't be broadcasted across all the CPUs within the same
> innershareable domain.
>
> When the vCPU is migrated between different CPUs, it may be
On 24/04/16 21:23, Borislav Petkov wrote:
> On Mon, Feb 01, 2016 at 10:38:48AM -0500, Boris Ostrovsky wrote:
>> Start HVMlite guest at XEN_ELFNOTE_PHYS32_ENTRY address. Setup hypercall
>> page, initialize boot_params, enable early page tables.
>>
>> Since this stub is executed before kernel entry
> -Original Message-
> From: George Dunlap [mailto:george.dun...@citrix.com]
> Sent: 25 April 2016 17:16
> To: Yu, Zhang; Jan Beulich; Paul Durrant
> Cc: Andrew Cooper; Wei Liu; Jun Nakajima; Kevin Tian; Zhiyuan Lv; xen-
> de...@lists.xen.org; Keir (Xen.org); Tim (Xen.org)
> Subject: Re:
flight 92695 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92695/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
On Mon, Apr 25, 2016 at 05:45:58PM +0100, Julien Grall wrote:
> Hi Ian,
>
> On 25/04/16 17:38, Ian Jackson wrote:
> >From: Fu Wei
> >
> >Improve the clarity of the wording introduced in 67831c4c
> >"docs/arm64: update the documentation for loading XSM support"
> >
>
Hi Ian,
On 25/04/16 17:38, Ian Jackson wrote:
From: Fu Wei
Improve the clarity of the wording introduced in 67831c4c
"docs/arm64: update the documentation for loading XSM support"
Signed-off-by: Ian Jackson
CC: Fu Wei
CC:
From: Fu Wei
Improve the clarity of the wording introduced in 67831c4c
"docs/arm64: update the documentation for loading XSM support"
Signed-off-by: Ian Jackson
CC: Fu Wei
CC: Julien Grall
CC: Stefano
Julien Grall writes ("Re: [Xen-devel] [PATCH] docs/arm64: clarify the
> Somehow, I am not in the mail CC. Maybe because of the "," at the end?
How odd.
> Otherwise, the text looks good to me. I have some questions about the
> formatting, see below.
I think there has been some damage from
On 4/26/2016 12:15 AM, George Dunlap wrote:
On 25/04/16 16:53, Yu, Zhang wrote:
On 4/25/2016 11:38 PM, Jan Beulich wrote:
On 25.04.16 at 17:29, wrote:
-Original Message-
From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
Sent: 25 April 2016 16:22
To:
On Mon, Apr 25, 2016 at 04:34:06PM +0100, Wei Liu wrote:
> On Mon, Apr 25, 2016 at 11:24:59AM -0400, Daniel De Graaf wrote:
> > On 04/25/2016 08:17 AM, Jan Beulich wrote:
> > On 18.03.16 at 17:46, wrote:
> > >>The command line instructions for FLASK include a note on how to
On 25/04/16 16:53, Yu, Zhang wrote:
>
>
> On 4/25/2016 11:38 PM, Jan Beulich wrote:
> On 25.04.16 at 17:29, wrote:
-Original Message-
From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
Sent: 25 April 2016 16:22
To: Paul Durrant; George
Hi Ian,
On 25/04/16 16:35, Ian Jackson wrote:
From: Fu Wei
Improve the clarity of the wording introduced in 67831c4c
"docs/arm64: update the documentation for loading XSM support"
Signed-off-by: Ian Jackson
CC: Fu Wei
CC:
On 4/25/2016 11:38 PM, Jan Beulich wrote:
On 25.04.16 at 17:29, wrote:
-Original Message-
From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
Sent: 25 April 2016 16:22
To: Paul Durrant; George Dunlap
Cc: xen-devel@lists.xen.org; Kevin Tian; Keir (Xen.org);
flight 92677 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92677/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REGR. vs.
>>> On 25.04.16 at 17:47, wrote:
> On Mon, Apr 25, 2016 at 11:41 AM, Jan Beulich wrote:
> On 25.04.16 at 17:34, wrote:
>>> Hey!
>>>
>>> Changelog:
>>> v8.1: http://lists.xen.org/archives/html/xen-devel/2016-04/msg01903.html
>>
On 4/25/2016 11:29 PM, Paul Durrant wrote:
-Original Message-
From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
Sent: 25 April 2016 16:22
To: Paul Durrant; George Dunlap
Cc: xen-devel@lists.xen.org; Kevin Tian; Keir (Xen.org); Jun Nakajima;
Andrew Cooper; Tim (Xen.org); Lv, Zhiyuan;
On Mon, Apr 25, 2016 at 09:48:37AM -0600, Jan Beulich wrote:
> >>> On 25.04.16 at 17:34, wrote:
> > This reverts commit d275ec9ca8a86f7c9c213f3551194d471ce90fbd.
> >
> > As we prefer to still utilize the old XENVER_ hypercall.
> >
> > Signed-off-by: Konrad Rzeszutek Wilk
On 04/25/2016 11:22 AM, Borislav Petkov wrote:
On Mon, Apr 25, 2016 at 10:42:15AM -0400, Boris Ostrovsky wrote:
Hmm... I thought that everything specified in boot.txt was ABI.
But those are not there.
>>> On 25.04.16 at 17:34, wrote:
> This reverts commit d275ec9ca8a86f7c9c213f3551194d471ce90fbd.
>
> As we prefer to still utilize the old XENVER_ hypercall.
>
> Signed-off-by: Konrad Rzeszutek Wilk
> Requested-and-acked-by: Jan Beulich
On Mon, Apr 25, 2016 at 11:41 AM, Jan Beulich wrote:
On 25.04.16 at 17:34, wrote:
>> Hey!
>>
>> Changelog:
>> v8.1: http://lists.xen.org/archives/html/xen-devel/2016-04/msg01903.html
>
> Old changelog?
>
It should have said: "Since v8.1:":
Worked
With this third payload one can do:
-bash-4.1# xen-xsplice load xen_hello_world.xsplice
Uploading xen_hello_world.xsplice (10148 bytes)
Performing check: completed
Performing apply:. completed
[xen_hello_world depends on hypervisor build-id]
-bash-4.1# xen-xsplice load xen_bye_world.xsplice
From: Dirk Behme
Add a section about what the firmware should do in EL3 before starting Xen.
E.g guest will use HVC instruction to issue hypercall. As this can be set only
at EL3, i.e. outside Xen, document this boot requirement.
Signed-off-by: Dirk Behme
>>> On 25.04.16 at 17:34, wrote:
> Hey!
>
> Changelog:
> v8.1: http://lists.xen.org/archives/html/xen-devel/2016-04/msg01903.html
Old changelog?
Jan
___
Xen-devel mailing list
Xen-devel@lists.xen.org
>>> On 25.04.16 at 17:29, wrote:
>> -Original Message-
>> From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
>> Sent: 25 April 2016 16:22
>> To: Paul Durrant; George Dunlap
>> Cc: xen-devel@lists.xen.org; Kevin Tian; Keir (Xen.org); Jun Nakajima;
>> Andrew
On Mon, Apr 25, 2016 at 11:24:59AM -0400, Daniel De Graaf wrote:
> On 04/25/2016 08:17 AM, Jan Beulich wrote:
> On 18.03.16 at 17:46, wrote:
> >>The command line instructions for FLASK include a note on how to compile
> >>Xen with FLASK but the note was out of date after
> -Original Message-
> From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
> Sent: 25 April 2016 16:22
> To: Paul Durrant; George Dunlap
> Cc: xen-devel@lists.xen.org; Kevin Tian; Keir (Xen.org); Jun Nakajima;
> Andrew Cooper; Tim (Xen.org); Lv, Zhiyuan; Jan Beulich; Wei Liu
> Subject: Re:
This reverts commit 2716d875379d538c1dfccad78a99ca7db2e09f90.
As it was decided that the existing XENVER hypercall - while having
grown organically over the years can still be expanded.
Signed-off-by: Konrad Rzeszutek Wilk
---
From: Andrew Cooper
To simply change the permissions on existing Xen mappings. The existing
destroy_xen_mappings() is altered to support changing the PTE permissions.
A new destroy_xen_mappings() is introduced, as the special case of not passing
_PAGE_PRESENT to
From: Fu Wei
Improve the clarity of the wording introduced in 67831c4c
"docs/arm64: update the documentation for loading XSM support"
Signed-off-by: Ian Jackson
CC: Fu Wei
CC: Julien Grall ,
CC: Stefano
For those users who want to use the virtual addresses that
are in the hypervisor's code/data region address space -
these three new functions allow that.
Implementation wise the vmap API keeps track of two virtual
address regions now:
a) VMAP_VIRT_START
b) Any provided virtual address space
From: Ross Lagerwall
Signed-off-by: Ross Lagerwall
Signed-off-by: Konrad Rzeszutek Wilk
Reviewed-by: Andrew Cooper
---
Cc: Ian Jackson
Cc: Jan Beulich
From: Ross Lagerwall
If in the payload we do not have the old_addr we can resolve
the virtual address based on the UNDEFined symbols.
We also use an boolean flag: new_symbol to track symbols. The usual
case this is used is by:
* A payload may introduce a new symbol
*
As it should be an useful debug mechanism.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Jan Beulich
Reviewed-by: Andrew Cooper
--
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir
If the hypervisor is built with we will display it.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Wei Liu
---
CC: Ian Jackson
CC: Wei Liu
v2: Include HAVE_*, use libxl_zalloc, s/rc/ret/
v3: Retry
During execution of the hypervisor we have two regions of
executable code - stext -> _etext, and _sinittext -> _einitext.
The later is not needed after bootup.
We also have various built-in macros and functions to search
in between those two swaths depending on the state of the system.
That is
From: Ross Lagerwall
Add support for loading xsplice payloads. This is somewhat similar to
the Linux kernel module loader, implementing the following steps:
- Verify the elf file.
- Parse the elf file.
- Allocate a region of memory mapped within a free area of
A mechanism is required to binarily patch the running hypervisor with new
opcodes that have come about due to primarily security updates.
This document describes the design of the API that would allow us to
upload to the hypervisor binary patches.
This document has been shaped by the input from:
The current mechanism is geared towards fast virtual address ->
symbol names lookup. This is fine for the normal use cases
(BUG_ON, WARN_ON, etc), but for xSplice - where we need to find
hypervisor symbols - it is slow.
To understand this patch, a description of the existing
method is explained
This change demonstrates how to generate an xSplice ELF payload.
The idea here is that we want to patch in the hypervisor
the 'xen_version_extra' function with an function that will
return 'Hello World'. The 'xl info | grep extraversion'
will reflect the new value after the patching.
To generate
From: Ross Lagerwall
Naturally the backtrace is presented when an instruction
hits an bug_frame or %p is used.
The payloads do not support bug_frames yet - however the functions
the payloads call could hit an BUG() or WARN().
The traps.c has logic to scan for it this
The implementation does not actually do any patching.
It just adds the framework for doing the hypercalls,
keeping track of ELF payloads, and the basic operations:
- query which payloads exist,
- query for specific payloads,
- check*1, apply*1, replace*1, and unload payloads.
*1: Which of
If you have a patch for xSplice send it our way!
Signed-off-by: Ross Lagerwall
Signed-off-by: Konrad Rzeszutek Wilk
Reviewed-by: Andrew Cooper
---
Cc: Ian Jackson
Cc: Jan Beulich
From: Ross Lagerwall
Add support for exception tables contained within xSplice payloads. If an
exception occurs search either the main exception table or a particular
active payload's exception table depending on the instruction pointer.
Also we add an test-case to
From: Ross Lagerwall
Implement support for the apply, revert and replace actions.
To perform and action on a payload, the hypercall sets up a data
structure to schedule the work. A hook is added in the reset_stack_and_jump
to check for work and execute it if needed
From: Ross Lagerwall
Add support for applying alternative sections within xsplice payload.
At payload load time, apply an alternative sections that are found.
Also we add an test-case exercising a rather useless alternative
(patching a NOP with a NOP) - but it does
The underlaying toolstack code to do the basic
operations when using the XEN_XSPLICE_op syscalls:
- upload the payload,
- get status of an payload,
- list all the payloads,
- apply, check, replace, and revert the payload.
Signed-off-by: Konrad Rzeszutek Wilk
We now expect that the ELF payloads be built with the
--build-id.
Also the .xsplice.deps section has to have the contents
of the hypervisor (or a preceding payload) build-id.
We already have the code to verify the Elf_Note build-id
so export parts of it.
This dependency means the hypervisor
From: Ross Lagerwall
Add support for handling bug frames contained with xsplice modules. If a
trap occurs search either the kernel bug table or an applied payload's
bug table depending on the instruction pointer.
Signed-off-by: Ross Lagerwall
From: Ross Lagerwall
Add Elf routines and data structures in preparation for loading an
xSplice payload.
We make an assumption that the max number of sections an ELF payload
can have is 64. We can in future make this be dependent on the
names of the sections and
This patch enables the Elf to be built with the build-id
and provide in the Xen hypervisor the code to extract it.
The man-page for ld --build-id says it is:
"Request the creation of a ".note.gnu.build-id" ELF note
section or a ".build-id" COFF section. The contents of the
note are unique bits
Hey!
Changelog:
v8.1: http://lists.xen.org/archives/html/xen-devel/2016-04/msg01903.html
- Worked on Jan's comments.
v8: since http://lists.xen.org/archives/html/xen-devel/2016-04/msg01873.html
- Posting the _RIGHT_ set of patches.
v7:
If the hypervisor was built with build-ids we can expose the
build-id value to the toolstack (if it is not built with
it will just return -ENODATA). This is a priviligied operation
so only the controlling stack is able to request this.
Signed-off-by: Konrad Rzeszutek Wilk
A simple tool that allows an system admin to perform
basic xsplice operations:
- Upload a xsplice file (with an unique name)
- List all the xsplice payloads loaded.
- Apply, revert, replace, or unload the payload using the
unique name.
- Do all two - upload, and apply the payload in one go
This reverts commit d275ec9ca8a86f7c9c213f3551194d471ce90fbd.
As we prefer to still utilize the old XENVER_ hypercall.
Signed-off-by: Konrad Rzeszutek Wilk
Requested-and-acked-by: Jan Beulich
---
tools/libxc/include/xenctrl.h | 32
On 04/25/2016 08:17 AM, Jan Beulich wrote:
On 18.03.16 at 17:46, wrote:
The command line instructions for FLASK include a note on how to compile
Xen with FLASK but the note was out of date after the change to Kconfig.
Signed-off-by: Doug Goldstein
---
On Mon, 25 Apr 2016, Ian Jackson wrote:
> Julien Grall writes ("Re: [PATCH v3] docs/arm64: update the documention for
> loading XSM support"):
> > Stefano has committed the previous version with some modifications. Is
> > it better to read?
>
> IMO it is better than the original but I still
On 4/25/2016 10:01 PM, Paul Durrant wrote:
-Original Message-
From: dunl...@gmail.com [mailto:dunl...@gmail.com] On Behalf Of
George Dunlap
Sent: 25 April 2016 14:39
To: Yu Zhang
Cc: xen-devel@lists.xen.org; Kevin Tian; Keir (Xen.org); Jun Nakajima;
Andrew Cooper; Tim (Xen.org); Paul
On Mon, Apr 25, 2016 at 10:42:15AM -0400, Boris Ostrovsky wrote:
> Hmm... I thought that everything specified in boot.txt was ABI.
But those are not there.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
___
Xen-devel
Jan Beulich writes ("Re: [Xen-devel] [PATCH v2] docs: update FLASK cmd line
instructions"):
> On 18.03.16 at 17:46, wrote:
> > The command line instructions for FLASK include a note on how to compile
> > Xen with FLASK but the note was out of date after the change to Kconfig.
On Mon, Apr 25, 2016 at 10:02:55AM -0500, Doug Goldstein wrote:
> On 4/25/16 9:53 AM, Wei Liu wrote:
> > On Mon, Apr 25, 2016 at 09:46:18AM -0500, Doug Goldstein wrote:
> >> For native (non-cross compiles) we now only require bcc, ld86, as86 for
> >> building rombios, we can build the toolstack
On 25/04/16 15:46, Doug Goldstein wrote:
> For native (non-cross compiles) we now only require bcc, ld86, as86 for
> building rombios, we can build the toolstack sans rombios and using the
> system SeaBIOS due to known build issues. At the same time capture the
> output of the configure scripts to
Julien Grall writes ("Re: [PATCH v3] docs/arm64: update the documention for
loading XSM support"):
> Stefano has committed the previous version with some modifications. Is
> it better to read?
IMO it is better than the original but I still think my proposed
wording is an improvement over
On 4/25/16 9:53 AM, Wei Liu wrote:
> On Mon, Apr 25, 2016 at 09:46:18AM -0500, Doug Goldstein wrote:
>> For native (non-cross compiles) we now only require bcc, ld86, as86 for
>> building rombios, we can build the toolstack sans rombios and using the
>> system SeaBIOS due to known build issues. At
On 25/04/16 14:35, Ian Jackson wrote:
> Andrew Cooper writes ("[PATCH for-4.7] docs/build: Work around apparent bug
> with multi-target rules"):
>> The `make` manual documents that a rule of the form
>>
>> target1 target2: prereq
>> recipe
>>
>> is equivilent to
>>
>> target1: prereq
>>
flight 92710 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92710/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 13
On Mon, Apr 25, 2016 at 09:46:18AM -0500, Doug Goldstein wrote:
> For native (non-cross compiles) we now only require bcc, ld86, as86 for
> building rombios, we can build the toolstack sans rombios and using the
> system SeaBIOS due to known build issues. At the same time capture the
> output of
On April 25, 2016 9:58pm, wrote:
> On 25/04/16 12:52, Jan Beulich wrote:
> On 18.04.16 at 16:00, wrote:
> >> --- a/xen/drivers/passthrough/arm/smmu.c
> >> +++ b/xen/drivers/passthrough/arm/smmu.c
> >> @@ -2540,7 +2540,7 @@ static int force_stage = 2;
For native (non-cross compiles) we now only require bcc, ld86, as86 for
building rombios, we can build the toolstack sans rombios and using the
system SeaBIOS due to known build issues. At the same time capture the
output of the configure scripts to help with tracking down future build
issues.
On Mon, Apr 25, 2016 at 09:39:03AM -0500, Doug Goldstein wrote:
> The #ifndef / #define value used was not consistent so it did not
> function as a proper header guard.
>
> Signed-off-by: Doug Goldstein
Acked-by: Wei Liu
Release-acked-by: Wei Liu
The #ifndef / #define value used was not consistent so it did not
function as a proper header guard.
Signed-off-by: Doug Goldstein
---
tools/libfsimage/ufs/ufs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/libfsimage/ufs/ufs.h
> -Original Message-
> From: George Dunlap
> Sent: 25 April 2016 15:28
> To: Paul Durrant
> Cc: Jan Beulich; Kevin Tian; Wei Liu; Andrew Cooper; Tim (Xen.org); xen-
> de...@lists.xen.org; Yu Zhang; Zhiyuan Lv; Jun Nakajima; Keir (Xen.org)
> Subject: Re: [Xen-devel] [PATCH v3 1/3] x86/ioreq
On Mon, Apr 25, 2016 at 3:19 PM, Paul Durrant wrote:
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: 25 April 2016 15:16
>> To: Paul Durrant
>> Cc: Andrew Cooper; George Dunlap; Wei Liu; Jun Nakajima; Kevin Tian;
>> Zhiyuan Lv; Yu
On Fri, Apr 01, 2016 at 11:03:28AM +0100, Wei Liu wrote:
> On Fri, Apr 01, 2016 at 01:41:40AM +, Xu, Quan wrote:
> > On March 31, 2016 9:50pm, Wei Liu wrote:
> > > On Thu, Mar 31, 2016 at 10:21:22AM +, Xu, Quan wrote:
> > > > On March 11, 2016 12:53am, Wei Liu
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 25 April 2016 15:16
> To: Paul Durrant
> Cc: Andrew Cooper; George Dunlap; Wei Liu; Jun Nakajima; Kevin Tian;
> Zhiyuan Lv; Yu Zhang; xen-devel@lists.xen.org; Keir (Xen.org); Tim (Xen.org)
> Subject: RE:
>>> On 25.04.16 at 16:01, wrote:
> The p2m type changes are also wrong. That type needs to be left alone,
> presumably, so that anything using HVMMEM_mmio_write_dm and compiled to the
> old interface version continues to function. I think HVMMEM_ioreq_server
> needs to
On 25/04/16 15:01, Paul Durrant wrote:
>> -Original Message-
>> From: dunl...@gmail.com [mailto:dunl...@gmail.com] On Behalf Of
>> George Dunlap
>> Sent: 25 April 2016 14:39
>> To: Yu Zhang
>> Cc: xen-devel@lists.xen.org; Kevin Tian; Keir (Xen.org); Jun Nakajima;
>> Andrew Cooper; Tim
flight 92666 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92666/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 60684
>>> On 25.04.16 at 15:39, wrote:
> On Mon, Apr 25, 2016 at 11:35 AM, Yu Zhang wrote:
>> --- a/xen/include/public/hvm/hvm_op.h
>> +++ b/xen/include/public/hvm/hvm_op.h
>> @@ -83,7 +83,13 @@ typedef enum {
>> HVMMEM_ram_rw,
>>> On 25.04.16 at 15:25, wrote:
> On Thu, Apr 21, 2016 at 03:38:26AM -0600, Jan Beulich wrote:
>> Recent changes to Linux result in there just being a single unmask
>> operation prior to expecting the first interrupts to arrive. However,
>> we've had a chicken-and-egg
On Mon, Apr 25, 2016 at 02:38:57AM -0600, Jan Beulich wrote:
> >>> On 22.04.16 at 17:21, wrote:
> > Here is what I came up using your idea. Do you want me to add
> > 'Suggested-by'
> > Jan on it?
>
> I'll leave that up to you; it was really just a vague idea that I
On Mon, Apr 25, 2016 at 09:54:37AM -0400, Boris Ostrovsky wrote:
> Yes, those.
I don't think the ones in arch/x86/kernel/head_{32,64}.S are ABI.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
___
Xen-devel mailing list
> -Original Message-
> From: dunl...@gmail.com [mailto:dunl...@gmail.com] On Behalf Of
> George Dunlap
> Sent: 25 April 2016 14:39
> To: Yu Zhang
> Cc: xen-devel@lists.xen.org; Kevin Tian; Keir (Xen.org); Jun Nakajima;
> Andrew Cooper; Tim (Xen.org); Paul Durrant; Lv, Zhiyuan; Jan Beulich;
1 - 100 of 184 matches
Mail list logo