This run is configured for baseline tests only.
flight 38709 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38709/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-qcow2 9
On 01/27/2016 02:00 PM, Luis R. Rodriguez wrote:
On Wed, Jan 27, 2016 at 10:48 AM, Luis R. Rodriguez wrote:
Worth mentioning here also is hpa's clarification on when subarch type
PC (0) should be used: [it should be used if the hardware is]
"enumerable using standard PC
flight 79145 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79145/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 15 guest-localmigratefail REGR. vs. 60684
On Wed, Jan 27, 2016 at 10:25:46AM +, Will Deacon wrote:
> On Tue, Jan 26, 2016 at 11:58:20AM -0800, Paul E. McKenney wrote:
> > On Tue, Jan 26, 2016 at 12:16:09PM +, Will Deacon wrote:
> > > On Mon, Jan 25, 2016 at 10:03:22PM -0800, Paul E. McKenney wrote:
> > > > On Mon, Jan 25, 2016 at
On 01/27/2016 11:32 AM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wrote:
>> I would like to hear the community's opinion on supporting more qdisk types
>> in
>> xl/libxl, e.g. nbd, rbd, iSCSI, etc. I prefer supporting additional qdisk
>> types
>> in
flight 79155 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79155/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-xsm 6 xen-boot fail REGR. vs. 59254
From: Shannon Zhao
Refactor gic-v3 related functions into dt and generic parts. This will be
helpful when adding acpi support for gic-v3.
Signed-off-by: Shannon Zhao
---
v6: keep vsize check in gicv3_init_v2
---
xen/arch/arm/gic-v3.c | 84
O0 -g3 -D__XEN_TOOLS__ -MMD -MF .linux.opic.d
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls -Werror
-Wmissing-prototypes -I./include
-I/home/www/builds_xen_unstable/xen-src-2e46e3f2-20160127/tools/libs/evtchn/../../../tools/include
-I/home/www/builds_xen_unstable/xen-src-2e
On 01/27/2016 02:09 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 27, 2016 at 02:25:51PM -0600, Doug Goldstein wrote:
>> On 1/27/16 12:32 PM, Konrad Rzeszutek Wilk wrote:
>>> On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wrote:
I would like to hear the community's opinion on
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 -
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
On 01/27/2016 01:25 PM, Doug Goldstein wrote:
> On 1/27/16 12:32 PM, Konrad Rzeszutek Wilk wrote:
>> On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wrote:
>>> I would like to hear the community's opinion on supporting more qdisk types
>>> in
>>> xl/libxl, e.g. nbd, rbd, iSCSI, etc. I prefer
flight 79158 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79158/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd 9 debian-di-install fail REGR. vs. 78977
On 01/25/2016 02:47 AM, David Vrabel wrote:
> On 23/01/16 22:12, Sarah Newman wrote:
>> Greetings,
>>
>> We are having problems related to mptsas and "swiotlb buffer is full" with
>> the Xen4CentOS kernel (3.18). It looks like the last related work was
>> the series
>>
To help people avoid having to figure out what versions of make and
binutils need to be supported document them explicitly. The version of
binutils that had to be supported was mentioned in
http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg00609.html
as 2.17 recently. It was decided
On 01/27/2016 03:26 AM, Maciej W. Rozycki wrote:
On Fri, 15 Jan 2016, Leonid Yegoshin wrote:
So you need to build a different kernel for some types of MIPS systems?
Or do you do boot-time rewriting, like a number of other arches do?
I don't know. I would like to have responses. Ralf asked
>>> On 27.01.16 at 08:35, wrote:
> 1: xstate: don't unintentionally clear compaction bit
> 2: adjust xsave structure attributes
> 3: xstate: fix fault behavior on XRSTORS
>
> Signed-off-by: Jan Beulich
Actually - no, let me see whether I can figure out the
>>> On 26.01.16 at 19:02, wrote:
> Last time, I did absolutely nothing. System was idle
> and it crashed just after the login. Now, I booted the
> system again and this time, there is no reset. But,
> performance of the system is very slow. Browser
> (Mozilla Firefox)
flight 79068 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79068/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-cubietruck 6 xen-bootfail REGR. vs. 59254
Hi Shannon,
On 2016/1/23 11:19, Shannon Zhao wrote:
From: Shannon Zhao
When it's a Xen domain0 booting with ACPI, it will supply a /chosen and
a /hypervisor node in DT. So check if it needs to enable ACPI.
Signed-off-by: Shannon Zhao
---
CC:
On Jan 26, 2016 23:51, "Peter Zijlstra" wrote:
>
> So for a moment it looked like MIPS wanted to equal or surpass Alpha in
> this respect.
If there is an architecture that I'd expect to try to take the "sucks more"
crown, MIPS would be it. They've already done the "worst
On Wed, Jan 27, 2016 at 03:15:47PM +, Andrew Cooper wrote:
> On 27/01/16 15:11, Konrad Rzeszutek Wilk wrote:
> > On Wed, Jan 27, 2016 at 11:00:24AM +, Andrew Cooper wrote:
> >> On 27/01/16 06:47, Wen Congyang wrote:
> >>> On 01/27/2016 04:40 AM, Konrad Rzeszutek Wilk wrote:
> On Wed,
On Wed, Jan 27, 2016 at 02:50:36PM +, David Vrabel wrote:
> Surely the interesting comparison here is how is (early) microcode
> loading disabled in KVM guests?
It isn't - kvm simply ignores the write to the microcode application
MSRs MSR_AMD64_PATCH_LOADER and MSR_IA32_UCODE_REV,
>>> On 27.01.16 at 15:51, wrote:
> On 27/01/16 14:40, Jan Beulich wrote:
>>
>> int set_mmio_p2m_entry(struct domain *d, unsigned long gfn, mfn_t mfn,
>> - p2m_access_t access)
>> + unsigned int order, p2m_access_t
On 1/27/2016 11:12 PM, Jan Beulich wrote:
On 27.01.16 at 15:56, wrote:
On 1/27/2016 10:32 PM, Jan Beulich wrote:
On 27.01.16 at 15:13, wrote:
About the truncation issue:
I do not quite follow. Will this hurt if the value
flight 79108 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79108/
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. 78610
On 27/01/16 15:45, Ian Campbell wrote:
> On Wed, 2016-01-27 at 15:18 +, Lars Kurth wrote:
>>> Doug says that you can mark a repo as a 'mirror', which will prevent
>>> people from being able to send pull requests to it; so I think my
>>> technical objection has been answered.
>>>
>>> I think
Andrew Cooper writes ("Re: [Xen-devel] [PATCH v9 02/25] docs/libxl: Introduce
COLO_CONTEXT to support migration v2 colo streams"):
> On 27/01/16 15:28, Konrad Rzeszutek Wilk wrote:
> > On Wed, Jan 27, 2016 at 03:15:47PM +, Andrew Cooper wrote:
> >> Mandatory records may not be ignored, and
Hi Ian,
I'll try to make clear domain restart thing first. Currently there are only
device entries in domain config for frontends with backend paths in them,
e.g.:
FrontendDomain.cfg:
vdevice = [ 'backend=BackendDomain,devid=0,device=/dev/device' ]
it is parsed only on frontend domain start,
On 1/27/16 9:24 AM, Ian Campbell wrote:
> On Wed, 2016-01-27 at 09:11 -0600, Doug Goldstein wrote:
>> On 1/27/16 9:05 AM, Ian Campbell wrote:
>>> On Wed, 2016-01-27 at 07:44 -0700, Jan Beulich wrote:
>>> On 27.01.16 at 15:30, wrote:
> On 1/25/16 5:27 AM, Ian Campbell
On Wed, 2016-01-27 at 18:20 +0200, Pavlo Suikov wrote:
> Hi Ian,
Please don't top post and please use plain text emails, not html.
> I'll try to make clear domain restart thing first. Currently there are
> only device entries in domain config for frontends with backend paths in
> them, e.g.:
>
On 27/01/16 15:28, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 27, 2016 at 03:15:47PM +, Andrew Cooper wrote:
>> On 27/01/16 15:11, Konrad Rzeszutek Wilk wrote:
>>> On Wed, Jan 27, 2016 at 11:00:24AM +, Andrew Cooper wrote:
On 27/01/16 06:47, Wen Congyang wrote:
> On 01/27/2016
On Wed, 2016-01-27 at 15:18 +, Lars Kurth wrote:
> > Doug says that you can mark a repo as a 'mirror', which will prevent
> > people from being able to send pull requests to it; so I think my
> > technical objection has been answered.
> >
> > I think the idea is still only half-baked though,
>>> On 27.01.16 at 16:23, wrote:
>
> On 1/27/2016 11:12 PM, Jan Beulich wrote:
> On 27.01.16 at 15:56, wrote:
>>> On 1/27/2016 10:32 PM, Jan Beulich wrote:
>>> On 27.01.16 at 15:13, wrote:
> About
On Wed, Jan 27, 2016 at 03:53:38PM +, George Dunlap wrote:
> On 27/01/16 15:27, Konrad Rzeszutek Wilk wrote:
> > On Wed, Jan 27, 2016 at 03:10:01PM +, George Dunlap wrote:
> >> On 27/01/16 14:33, Konrad Rzeszutek Wilk wrote:
> >>> On Xen - the schedule() would go HLT.. and then later be
On 1/27/2016 11:58 PM, Jan Beulich wrote:
On 27.01.16 at 16:23, wrote:
On 1/27/2016 11:12 PM, Jan Beulich wrote:
On 27.01.16 at 15:56, wrote:
On 1/27/2016 10:32 PM, Jan Beulich wrote:
On 27.01.16 at 15:13,
Hi everyone,
we are rebooting a number of Xen Project services in the next few days to
upgrade operating systems. This means that a few services may be temporarily
unavailable. The following websites are affected and will be done during the
times below. If you notice any issues after the
On Wed, 2016-01-27 at 09:11 -0600, Doug Goldstein wrote:
> On 1/27/16 9:05 AM, Ian Campbell wrote:
> > On Wed, 2016-01-27 at 07:44 -0700, Jan Beulich wrote:
> > > > > > On 27.01.16 at 15:30, wrote:
> > > > On 1/25/16 5:27 AM, Ian Campbell wrote:
> > > > > On Wed, 2016-01-20 at
On Wed, Jan 27, 2016 at 10:17:56AM -0500, Boris Ostrovsky wrote:
> On 01/27/2016 10:09 AM, David Vrabel wrote:
> >On 27/01/16 15:06, Boris Ostrovsky wrote:
> >>On 01/27/2016 09:50 AM, David Vrabel wrote:
> >>>On 27/01/16 14:42, Konrad Rzeszutek Wilk wrote:
> On Tue, Jan 26, 2016 at 08:54:56PM
On Wed, Jan 27, 2016 at 03:10:01PM +, George Dunlap wrote:
> On 27/01/16 14:33, Konrad Rzeszutek Wilk wrote:
> > On Tue, Jan 26, 2016 at 11:21:36AM +, George Dunlap wrote:
> >> On 22/01/16 16:54, Elena Ufimtseva wrote:
> >>> Hello all!
> >>>
> >>> Dario, Gerorge or anyone else, your help
On Sat, 23 Jan 2016, Shannon Zhao wrote:
> From: Shannon Zhao
>
> There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, the
> former signals to the OS that the hardware is PSCI compliant. The latter
> selects the appropriate conduit for PSCI calls by toggling
On Wed, Jan 27, 2016 at 10:27:01AM -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 27, 2016 at 03:10:01PM +, George Dunlap wrote:
> > On 27/01/16 14:33, Konrad Rzeszutek Wilk wrote:
> > > On Tue, Jan 26, 2016 at 11:21:36AM +, George Dunlap wrote:
> > >> On 22/01/16 16:54, Elena Ufimtseva
On 01/27/2016 10:29 AM, Konrad Rzeszutek Wilk wrote:
On Wed, Jan 27, 2016 at 10:17:56AM -0500, Boris Ostrovsky wrote:
On 01/27/2016 10:09 AM, David Vrabel wrote:
On 27/01/16 15:06, Boris Ostrovsky wrote:
On 01/27/2016 09:50 AM, David Vrabel wrote:
On 27/01/16 14:42, Konrad Rzeszutek Wilk
On Sat, 23 Jan 2016, Shannon Zhao wrote:
> From: Shannon Zhao
>
> When MADT is parsed, print GIC information to make the boot log look
> pretty.
>
> Signed-off-by: Hanjun Guo
> Signed-off-by: Tomasz Nowicki
>
On 27/01/16 15:27, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 27, 2016 at 03:10:01PM +, George Dunlap wrote:
>> On 27/01/16 14:33, Konrad Rzeszutek Wilk wrote:
>>> On Xen - the schedule() would go HLT.. and then later be woken up by the
>>> VIRQ_TIMER. And since the two applications were on
On Wed, 2016-01-27 at 16:01 +, George Dunlap wrote:
> On 27/01/16 15:45, Ian Campbell wrote:
> > For most patch series setting up a GH account and pushing the changes to it
> > etc is pure overhead (or at least optional), there is no need to encourage
> > it for most series, nor even
flight 79162 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79162/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 66399
On Tue, Jan 12, 2016 at 12:05:48PM +, Wei Liu wrote:
> Drop xen-users@, CC xen-devel@ and blk maintainers, change title.
>
What is the MTU you are using?
How do you mount the disk?
> On Mon, Jan 11, 2016 at 03:08:24PM +0100, Kojedzinszky Richárd wrote:
> > Dear all,
> >
> > We are facing
xs_perm_to_string takes a size_t which isn't defined by anything
pulled in directly by this header.
Given the other headers xenstore_lib.h pulls in this looks to be an
oversight rather than a deliberate policy.
Signed-off-by: Ian Campbell
---
flight 79130 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79130/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 11 guest-start fail like 78683
Tests which did not
4.3-stable review patch. If anyone has any objections, please let me know.
--
From: David Vrabel
commit d8c98a1d1488747625ad6044d423406e17e99b7a upstream.
Adding the rtc platform device in non-privileged Xen PV guests causes
an IRQ conflict because
On Wed, Jan 13, 2016 at 02:59:09PM +, Stefano Stabellini wrote:
> On Xen MSIs can be remapped into pirqs, which are a type of event
> channels. It's mostly for the benefit of PCI passthrough devices, to
> avoid the overhead of interacting with the emulated lapic.
>
> However remapping
Most updates to the exception bitmaps set or clear an individual bits.
However, entering or exiting emulated real mode unilaterally clobbers it,
leaving the exit code to recalculate what it should have been. This is error
prone, and indeed currently fails to recalculate the TRAP_no_device
Compiling qemu-xen at 2ce1d30 ("xenfb.c: avoid expensive loops when prod
<= out_cons") leads to this error with -O1:
xen.git/tools/qemu-xen-dir/hw/i386/intel_iommu.c: In function
‘vtd_context_device_invalidate’:
xen.git/tools/qemu-xen-dir/hw/i386/intel_iommu.c:911:46: error: ‘mask’ may be
used
This run is configured for baseline tests only.
flight 38708 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38708/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 3
On Sat, Nov 28, 2015 at 04:44:58PM -0500, Don Slutz wrote:
> From: Don Slutz
>
> This allows use of QEMU's VMware emulated video card
>
> NOTE: vga=vmware is not supported by device_model_version=qemu-xen-traditional
>
> Signed-off-by: Don Slutz
> CC:
c/s 0f1cb96e "x86 hvm: Allow cross-vendor migration" caused HVM domains to
unconditionally intercept #UD exceptions. While cross-vendor migration is
cool as a demo, it is extremely niche.
Intercepting #UD allows userspace code in a multi-vcpu guest to execute
arbitrary instructions in the x86
On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wrote:
> I would like to hear the community's opinion on supporting more qdisk types in
> xl/libxl, e.g. nbd, rbd, iSCSI, etc. I prefer supporting additional qdisk
> types
> in libxl over apps like xl or libvirt doing all the setup, producing a
On 01/27/2016 01:59 PM, Andrew Cooper wrote:
On 27/01/16 18:49, Boris Ostrovsky wrote:
On 01/27/2016 01:11 PM, Andrew Cooper wrote:
diff --git a/xen/arch/x86/domctl.c b/xen/arch/x86/domctl.c
index 1d71216..1084e82 100644
--- a/xen/arch/x86/domctl.c
+++ b/xen/arch/x86/domctl.c
@@ -65,8 +65,20
On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote:
> Xen developers,
>
> After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed
> NIC stopped working.
> This bug was probably introduced in Debian Jessie sometime
> between 2015-12-30 and 2016-01-08 as 2015-12-30 as
On Tue, Jan 26, 2016 at 05:48:34PM +0100, Fabio Fantoni wrote:
> I take a fast look to virgl 3d project even if I not tested it for now. It
> seems interesting for adding 2d and 3d hw acceleration support to virtual
> machines with a large hw (gpu) choice.
> I take a look also to intel gvt-g but
Bleh moving forward please use mcg...@kernel.org, that will be sent to
my employer and my personal address. More below.
On Wed, Jan 27, 2016 at 8:15 AM, Boris Ostrovsky
wrote:
> On 01/27/2016 10:29 AM, Konrad Rzeszutek Wilk wrote:
>> On Wed, Jan 27, 2016 at 10:17:56AM
On Wed, Jan 27, 2016 at 10:48 AM, Luis R. Rodriguez wrote:
>
> Worth mentioning here also is hpa's clarification on when subarch type
> PC (0) should be used: [it should be used if the hardware is]
> "enumerable using standard PC mechanisms (PCI, ACPI) and doesn't need
> a
On 27/01/16 19:14, Boris Ostrovsky wrote:
> On 01/27/2016 01:59 PM, Andrew Cooper wrote:
>> On 27/01/16 18:49, Boris Ostrovsky wrote:
>>> On 01/27/2016 01:11 PM, Andrew Cooper wrote:
diff --git a/xen/arch/x86/domctl.c b/xen/arch/x86/domctl.c
index 1d71216..1084e82 100644
---
On 01/27/2016 01:11 PM, Andrew Cooper wrote:
c/s 0f1cb96e "x86 hvm: Allow cross-vendor migration" caused HVM domains to
unconditionally intercept #UD exceptions. While cross-vendor migration is
cool as a demo, it is extremely niche.
Intercepting #UD allows userspace code in a multi-vcpu guest
c/s 0f1cb96e "x86 hvm: Allow cross-vendor migration" caused HVM domains to
unconditionally intercept #UD exceptions. While cross-vendor migration is
cool as a demo, it is extremely niche.
Intercepting #UD allows userspace code in a multi-vcpu guest to execute
arbitrary instructions in the x86
On 27/01/16 18:49, Boris Ostrovsky wrote:
> On 01/27/2016 01:11 PM, Andrew Cooper wrote:
>> c/s 0f1cb96e "x86 hvm: Allow cross-vendor migration" caused HVM
>> domains to
>> unconditionally intercept #UD exceptions. While cross-vendor
>> migration is
>> cool as a demo, it is extremely niche.
>>
>>
On 01/27/2016 02:13 PM, Andrew Cooper wrote:
c/s 0f1cb96e "x86 hvm: Allow cross-vendor migration" caused HVM domains to
unconditionally intercept #UD exceptions. While cross-vendor migration is
cool as a demo, it is extremely niche.
Intercepting #UD allows userspace code in a multi-vcpu guest
On 27/01/2016 19:42, Razvan Cojocaru wrote:
> It is currently possible to leave a monitor flag enabled even
> after vm_event_cleanup_domain() has been called, potentially
> leading to a crash in hvm_msr_write_intercept() and hvm_set_crX()
> (when v->arch.vm_event has become NULL, but the
On 1/27/16 12:32 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wrote:
>> I would like to hear the community's opinion on supporting more qdisk types
>> in
>> xl/libxl, e.g. nbd, rbd, iSCSI, etc. I prefer supporting additional qdisk
>> types
>> in libxl
It is currently possible to leave a monitor flag enabled even
after vm_event_cleanup_domain() has been called, potentially
leading to a crash in hvm_msr_write_intercept() and hvm_set_crX()
(when v->arch.vm_event has become NULL, but the corresponding
corresponding v->domain->arch.monitor flag is
On Wed, Jan 27, 2016 at 12:42 PM, Razvan Cojocaru wrote:
> It is currently possible to leave a monitor flag enabled even
> after vm_event_cleanup_domain() has been called, potentially
> leading to a crash in hvm_msr_write_intercept() and hvm_set_crX()
> (when
On Wed, Jan 27, 2016 at 07:57:00PM +, Andrew Cooper wrote:
> On 27/01/2016 19:52, Konrad Rzeszutek Wilk wrote:
> >> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> >> index 674feea..7a15d49 100644
> >> --- a/xen/arch/x86/hvm/hvm.c
> >> +++ b/xen/arch/x86/hvm/hvm.c
> >> @@ -93,12
> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> index 674feea..7a15d49 100644
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -93,12 +93,10 @@ unsigned long __section(".bss.page_aligned")
> static bool_t __initdata opt_hap_enabled = 1;
> boolean_param("hap",
On 27/01/2016 19:52, Konrad Rzeszutek Wilk wrote:
>> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
>> index 674feea..7a15d49 100644
>> --- a/xen/arch/x86/hvm/hvm.c
>> +++ b/xen/arch/x86/hvm/hvm.c
>> @@ -93,12 +93,10 @@ unsigned long __section(".bss.page_aligned")
>> static bool_t
Extend the existing get_mem_access memop to allow querying permissions in
altp2m views as well.
Signed-off-by: Tamas K Lengyel
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
The altp2m subsystem in its current form uses its own HVMOP hypercall to set
mem_access permissions, duplicating some of the code already present for
setting regular mem_access permissions. In this patch we consolidate the two,
deprecate the HVMOP hypercall and update the corresponding tools.
On Wed, Jan 27, 2016 at 02:25:51PM -0600, Doug Goldstein wrote:
> On 1/27/16 12:32 PM, Konrad Rzeszutek Wilk wrote:
> > On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wrote:
> >> I would like to hear the community's opinion on supporting more qdisk
> >> types in
> >> xl/libxl, e.g. nbd,
flight 79146 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79146/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-raw 13 guest-saverestorefail never pass
test-armhf-armhf-libvirt-raw 11
On 27/01/16 06:47, Wen Congyang wrote:
> On 01/27/2016 04:40 AM, Konrad Rzeszutek Wilk wrote:
>> On Wed, Dec 30, 2015 at 10:37:32AM +0800, Wen Congyang wrote:
>>> It is the negotiation record for COLO.
>>> Primary->Secondary:
>>> control_id 0x: Secondary VM is out of sync, start a new
On Fri, 15 Jan 2016, Leonid Yegoshin wrote:
> > So you need to build a different kernel for some types of MIPS systems?
> > Or do you do boot-time rewriting, like a number of other arches do?
>
> I don't know. I would like to have responses. Ralf asked Maciej about old
> systems and that came
On Wed, Jan 27, 2016 at 10:55 AM, Andrew Cooper
wrote:
> On 27/01/16 09:45, Ian Campbell wrote:
>> On Tue, 2016-01-26 at 11:26 -0600, Doug Goldstein wrote:
>>> On 1/26/16 10:55 AM, Ian Campbell wrote:
On Sat, 2015-12-19 at 14:51 -0600, Doug Goldstein wrote:
>
On Wed, 2016-01-27 at 11:18 +, Ian Campbell wrote:
> On Tue, 2016-01-26 at 13:11 +, osstest service owner wrote:
> > flight 79008 linux-4.1 real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/79008/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are
On Sat, 23 Jan 2016, Shannon Zhao wrote:
> From: Shannon Zhao
>
> Refactor gic-v3 related functions into dt and generic parts. This will be
> helpful when adding acpi support for gic-v3.
>
> Signed-off-by: Shannon Zhao
> ---
> v5: none
> v4:
On Wed, 2016-01-27 at 11:01 +, Jason Long wrote:
> Hello.
> I look at below article :
>
> http://xenserver.org/blog/entry/a-new-year-a-new-way-to-build-for-xenserver.html
>
> What does it mean?
xenserver != xenproject (xenserver is a downstream project of xenproject).
If this discussion
> On January 27, 2016 at 6:48am, wrote:
> > From: Jan Beulich [mailto:jbeul...@suse.com]
> > Sent: Tuesday, January 26, 2016 11:53 PM
> > Once again: Before getting started, please assess which route is going
> > to be the better one. Remember that we had already discussed and put
flight 79090 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79090/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-cubietruck 15 guest-start/debian.repeat fail in 78925
REGR. vs. 66399
>>> On 27.01.16 at 12:09, wrote:
>> On January 27, 2016 at 6:48am, wrote:
>> > From: Jan Beulich [mailto:jbeul...@suse.com]
>> > Sent: Tuesday, January 26, 2016 11:53 PM
>
>
>> > Once again: Before getting started, please assess which route is going
>> > to be
On Wed, 27 Jan 2016, Ralf Baechle wrote:
> > So you need to build a different kernel for some types of MIPS systems?
>
> Yes. We can't really do without. Classic MIPS code is not relocatable
> without the complexity of PIC code as used by ELF DSOs - and their
> performanc penalty. Plus we
flight 38707 distros-debian-squeeze real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38707/
Perfect :-)
All tests in this flight passed
baseline version:
flight 38672
jobs:
build-amd64 pass
build-armhf
When __p2m_get_mem_access gets called, the p2m lock is already taken
by either get_page_from_gva or p2m_get_mem_access.
Possible code paths:
1) -> get_page_from_gva
-> p2m_mem_access_check_and_get_page
-> __p2m_get_mem_access
2) ->
On Tue, 2016-01-26 at 11:26 -0600, Doug Goldstein wrote:
> On 1/26/16 10:55 AM, Ian Campbell wrote:
> > On Sat, 2015-12-19 at 14:51 -0600, Doug Goldstein wrote:
> > > All,
> > >
> > > Now I'll start off by saying that "no" is a perfectly acceptable answer
> > > to this suggestion. Basically I
On Tue, Jan 26, 2016 at 11:58:20AM -0800, Paul E. McKenney wrote:
> On Tue, Jan 26, 2016 at 12:16:09PM +, Will Deacon wrote:
> > On Mon, Jan 25, 2016 at 10:03:22PM -0800, Paul E. McKenney wrote:
> > > On Mon, Jan 25, 2016 at 04:42:43PM +, Will Deacon wrote:
> > > > On Fri, Jan 15, 2016 at
On Thu, Jan 14, 2016 at 04:47:53PM -0800, Paul E. McKenney wrote:
> So you need to build a different kernel for some types of MIPS systems?
Yes. We can't really do without. Classic MIPS code is not relocatable
without the complexity of PIC code as used by ELF DSOs - and their
performanc
On 27/01/16 09:45, Ian Campbell wrote:
> On Tue, 2016-01-26 at 11:26 -0600, Doug Goldstein wrote:
>> On 1/26/16 10:55 AM, Ian Campbell wrote:
>>> On Sat, 2015-12-19 at 14:51 -0600, Doug Goldstein wrote:
All,
Now I'll start off by saying that "no" is a perfectly acceptable answer
On 27/01/16 10:00, Ian Campbell wrote:
> On Wed, 2016-01-27 at 15:12 +0800, Wen Congyang wrote:
>> On 01/27/2016 04:44 AM, Konrad Rzeszutek Wilk wrote:
+ 0x000F: DIRTY_PFN_LIST
+
>>> Perhaps make it part of the optional and prefix it with CHECKPOINT?
>> IIUC, optional
On Tue, 2016-01-26 at 13:11 +, osstest service owner wrote:
> flight 79008 linux-4.1 real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/79008/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>
This run is configured for baseline tests only.
flight 38706 linux-3.18 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38706/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 19
(we went offlist by mistake without noticing, resending my last reply which
I think has sufficient context/quoting to make sense)
On Wed, 2016-01-27 at 11:51 +0200, CORNELIU ZUZU wrote:
> On 1/26/2016 6:14 PM, Ian Campbell wrote:
> > On Tue, 2016-01-26 at 13:46 +0200, Corneliu ZUZU wrote:
> > >
1 - 100 of 178 matches
Mail list logo