flight 83683 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83683/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 6 xen-build fail REGR. vs. 66399
build-i386-rumpuserxen
On Mon, Feb 22, 2016 at 10:18:42AM -0700, Jan Beulich wrote:
> > @@ -4703,7 +4703,19 @@ void hvm_cpuid(unsigned int input, unsigned int
> > *eax, unsigned int *ebx,
> > for ( sub_leaf = 2; sub_leaf < 63; sub_leaf++ )
> > if ( (v->arch.xcr0 |
On 02/22/2016 07:35 AM, Ján Tomko wrote:
> On Wed, Feb 17, 2016 at 05:33:45PM -0700, Jim Fehlig wrote:
>> xl/libxl already supports qemu's network-based block backends
>> such as nbd and rbd. libvirt has supported configuring such
>> s for long time too. This patch adds support for rbd
>> disks in
On 23/02/2016 23:44, Luis R. Rodriguez wrote:
> On Tue, Feb 23, 2016 at 10:44:56PM +, Andrew Cooper wrote:
>> On 23/02/2016 22:18, Luis R. Rodriguez wrote:
>>> On Tue, Feb 23, 2016 at 05:00:12PM -0500, Konrad Rzeszutek Wilk wrote:
On Tue, Feb 23, 2016 at 12:48:18PM -0800, Luis R.
> > > +static void reschedule_fn(void *unused)
> > > +{
> > > +smp_mb(); /* Synchronize with setting do_work */
> > > +raise_softirq(SCHEDULE_SOFTIRQ);
> >
> > As you have to IPI each processor to raise a schedule softirq, you can
> > set a per-cpu "xsplice enter rendezvous" variable.
On Tue, Feb 23, 2016 at 07:38:15PM +0200, Oleksii Kurochko wrote:
> Hello.
>
> Any updates?
>
> With best regards,
> Oleksii
>
> 2016-02-09 14:23 GMT+02:00 Oleksii Kurochko :
>
> > Hello.
> >
> > I want to use Mini-OS as Dom0.
> >
> > What should be done for this
flight 83624 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83624/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail REGR. vs. 82482
On 02/23/2016 01:00 PM, Corneliu ZUZU wrote:
> On 2/23/2016 12:54 PM, Razvan Cojocaru wrote:
>> On 02/23/2016 11:09 AM, Corneliu ZUZU wrote:
>>> On 2/18/2016 9:35 PM, Corneliu ZUZU wrote:
This patch adds ARM support for guest-request monitor vm-events.
Summary of changes:
==
The x86 architecture allows either: a) the 64-bit FIP/FDP registers to
be restored (clearing FCS and FDS); or b) the 32-bit FIP/FDP and
FCS/FDS registers to be restored (clearing the upper 32-bits).
Add a per-domain field to indicate which of these options a guest
needs. The options are: 8, 4 or
flight 83609 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83609/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail in 83289 pass in
83609
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Monday, January 11, 2016 5:59 PM
> To: Wei Liu; Li, Liang Z
> Cc: ian.campb...@citrix.com; stefano.stabell...@eu.citrix.com;
> ian.jack...@eu.citrix.com; xen-devel@lists.xen.org; jbeul...@suse.com
> Subject: Re: [Xen-devel] [PATCH]
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
intervention when guest is running in non-root mode.
You can find the VT-d Posted-Interrtups Spec. in
This is the core logic handling for VT-d posted-interrupts. Basically it
deals with how and when to update posted-interrupts during the following
scenarios:
- vCPU is preempted
- vCPU is slept
- vCPU is blocked
When vCPU is preempted/slept, we update the posted-interrupts during
scheduling by
Enable VT-d Posted-Interrupts and add a command line
parameter for it.
CC: Jan Beulich
Signed-off-by: Feng Wu
Reviewed-by: Kevin Tian
Acked-by: Jan Beulich
---
docs/misc/xen-command-line.markdown | 9 -
* Luis R. Rodriguez wrote:
> Although hardware_subarch has been in place since the x86 boot
> protocol 2.07 it hasn't been used much. Enumerate current possible
> values to avoid misuses and help with semantics later at boot
> time should this be used further.
>
> v2: fix
Hi Jan,
I found some issues in your patch, see the comments below.
> -Original Message-
> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
> boun...@lists.xen.org] On Behalf Of Jan Beulich
> Sent: Monday, October 19, 2015 11:23 PM
> To: xen-devel
> Cc: Tian, Kevin; Nakajima,
>>> On 23.02.16 at 05:59, wrote:
>
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Monday, February 22, 2016 9:08 PM
>> To: Wu, Feng
>> Cc: Andrew Cooper ; Dario Faggioli
>>
hi !
I am transplanting the xen-4.7 on my OMAP5432 uEVM board,but after booting the
xen ,the dom0 kernel didnot boot successfully(no console output while booting
the dom0 kernel).I followed my step from this link:
Xen_ARM_with_Virtualization_Extensions/OMAP5432_uEVM
my u-boot command and
>>> On 22.02.16 at 22:14, wrote:
(Please trim you replies.)
> Ping: Or would you prefer resubmitting with the comments so far?
Either way is fine. It's on my list of thing to look at, but being RFC
it ranges priority wise behind various other things; I've been hoping
>>> On 22.02.16 at 19:43, wrote:
> On 2/22/16 10:36 AM, Jan Beulich wrote:
> On 08.02.16 at 18:07, wrote:
>>> There is no reason for any of it to be modified. Additionally, link
>>> .init.setup beside the other constant .init data.
>>>
>>> No
20 matches
Mail list logo