[Xen-devel] Linux 4.4 boot crash on xen 4.5.3 with dom0_mem == max

I'm trying to figure out a crash when booting a Linux 4.4 dom0 on a recent stable xen 4.5. I'm capping the dom0 memory by setting dom0_mem=18432M,max:18432M on the xen command line, and the kernel config has CONFIG_XEN_BALLOON unset. The crash seems dependent on the contents of the e820 table;

[Xen-devel] [xen-4.6-testing test] 94491: regressions - FAIL

flight 94491 xen-4.6-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/94491/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-libvirt 5 libvirt-build fail REGR. vs. 93932

[Xen-devel] [qemu-upstream-4.3-testing test] 94494: trouble: blocked/broken

flight 94494 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/94494/ 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

Re: [Xen-devel] Question about running Xen on NVIDIA Jetson-TK1

On Mon, May 16, 2016 at 7:27 PM, Kyle Temkin wrote: > Hi, Meng: > Hi Kyle, > Julien is correct-- a coworker and I are working on support for Tegra > SoCs, and we've made pretty good progress; there's work yet to be > done, but we have dom0 and guests booting on the

Re: [Xen-devel] [PATCH v10 1/3] vt-d: add a timeout parameter for Queued Invalidation

> From: Xu, Quan > Sent: Monday, May 16, 2016 11:26 PM > > On May 13, 2016 11:28 PM, Jan Beulich wrote: > > >>> On 22.04.16 at 12:54, wrote: > > > --- a/docs/misc/xen-command-line.markdown > > > +++ b/docs/misc/xen-command-line.markdown > > > @@ -1532,6

[Xen-devel] [xen-4.5-testing test] 94488: regressions - FAIL

flight 94488 xen-4.5-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/94488/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-libvirt5 libvirt-build fail REGR. vs. 93989

[Xen-devel] [ovmf test] 94497: regressions - FAIL

flight 94497 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/94497/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-xsm5 xen-build fail REGR. vs. 65543 build-amd64

Re: [Xen-devel] xen: 82599 passthrough problem

Thank you for your reply. For the first question, the BUG I hit is : static irq_guest_action_t *__pirq_guest_unbind( struct domain *d, int pirq, struct irq_desc *desc) { unsigned intirq; irq_guest_action_t *action; cpumask_t cpu_eoi_map; int

[Xen-devel] [ovmf test] 94493: regressions - FAIL

flight 94493 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/94493/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-xsm5 xen-build fail REGR. vs. 65543 build-amd64

[Xen-devel] [xen-unstable test] 94487: tolerable FAIL - PUSHED

flight 94487 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/94487/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 15 guest-start/debian.repeat fail REGR. vs. 94461 test-amd64-amd64-xl-rtds

Re: [Xen-devel] Question about running Xen on NVIDIA Jetson-TK1

Hi, Meng: Julien is correct-- a coworker and I are working on support for Tegra SoCs, and we've made pretty good progress; there's work yet to be done, but we have dom0 and guests booting on the Jetson TK1, Jetson TX1, and the Google Pixel C. We hope to get a patch set out soon-- unfortunately,

Re: [Xen-devel] [BUG] Linux process vruntime accounting in Xen

On Mon, May 16, 2016 at 3:38 PM, Tony S wrote: > On Mon, May 16, 2016 at 5:37 AM, Dario Faggioli > wrote: >> [Adding George again, and a few Linux/Xen folks] >> >> On Sat, 2016-05-14 at 18:25 -0600, Tony S wrote: >>> In virtualized environments,

Re: [Xen-devel] [BUG] Linux process vruntime accounting in Xen

On 05/16/2016 05:38 PM, Tony S wrote: > The issue behind it is that the process execution calculation(e.g., > delta_exec) in virtualized environment should not be calculated as it > did in physical enviroment. > > Here are two solutions to fix it: > > 1) Based on the

Re: [Xen-devel] Problem Reading from XenStore in DomU

On May 16, 2016 6:25 PM, "Doug Goldstein" wrote: > > On 5/16/16 3:18 PM, Dagaen Golomb wrote: > > On Mon, May 16, 2016 at 3:56 PM, Dagaen Golomb wrote: > >> On Mon, May 16, 2016 at 3:52 PM, Dagaen Golomb wrote: > >>> On Mon, May

Re: [Xen-devel] Problem Reading from XenStore in DomU

On 5/16/16 3:18 PM, Dagaen Golomb wrote: > On Mon, May 16, 2016 at 3:56 PM, Dagaen Golomb wrote: >> On Mon, May 16, 2016 at 3:52 PM, Dagaen Golomb >> wrote: >>> On Mon, May 16, 2016 at 3:12 PM, Doug Goldstein wrote: On

Re: [Xen-devel] [PATCHv1 0/2] xen/xenfs: fix /proc/xen/xenbus

On 5/16/16 12:44 PM, David Vrabel wrote: > "Fix" /proc/xen/xenbus by making it a symlink to the working > /dev/xen/xenbus. Do the same for /proc/xen/privcmd so it matches. > > If there's agreement on this approach I'll resend to Cc the fs > maintainers. > > David > Looks good to me. Looks

[Xen-devel] [xen-unstable baseline-only test] 44420: regressions - trouble: blocked/broken/fail/pass

This run is configured for baseline tests only. flight 44420 xen-unstable real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/44420/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-xsm 4 capture-logs

Re: [Xen-devel] [BUG] Linux process vruntime accounting in Xen

On Mon, May 16, 2016 at 5:37 AM, Dario Faggioli wrote: > [Adding George again, and a few Linux/Xen folks] > > On Sat, 2016-05-14 at 18:25 -0600, Tony S wrote: >> In virtualized environments, sometimes we need to limit the CPU >> resources to a virtual machine(VM). For

[Xen-devel] [qemu-upstream-4.3-testing test] 94492: trouble: blocked/broken

flight 94492 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/94492/ 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

Re: [Xen-devel] Problem Reading from XenStore in DomU

On Mon, May 16, 2016 at 3:56 PM, Dagaen Golomb wrote: > On Mon, May 16, 2016 at 3:52 PM, Dagaen Golomb wrote: >> On Mon, May 16, 2016 at 3:12 PM, Doug Goldstein wrote: >>> On 5/16/16 11:20 AM, Dagaen Golomb wrote: On Mon,

Re: [Xen-devel] Problem Reading from XenStore in DomU

On Mon, May 16, 2016 at 3:52 PM, Dagaen Golomb wrote: > On Mon, May 16, 2016 at 3:12 PM, Doug Goldstein wrote: >> On 5/16/16 11:20 AM, Dagaen Golomb wrote: >>> On Mon, May 16, 2016 at 12:11 PM, Dagaen Golomb >>> wrote: On

Re: [Xen-devel] Problem Reading from XenStore in DomU

On Mon, May 16, 2016 at 3:12 PM, Doug Goldstein wrote: > On 5/16/16 11:20 AM, Dagaen Golomb wrote: >> On Mon, May 16, 2016 at 12:11 PM, Dagaen Golomb >> wrote: >>> On Mon, May 16, 2016 at 12:03 PM, Dagaen Golomb >>> wrote:

Re: [Xen-devel] [HACKATHON 2016] ARM Status

On Thu, May 05, 2016 at 04:41:51PM +0100, Steve Capper wrote: > [Apologies for the late send] > > Xen - ARM Status > > There was discussion on the following items: > > *) Booting Xen on 64-bit ARM SoC > o) Unfortunately Xen was executed in EL1. > o) Advice was given that the

Re: [Xen-devel] Question about running Xen on NVIDIA Jetson-TK1

Hi Julien, On Mon, May 16, 2016 at 1:33 PM, Julien Grall wrote: > (CC Kyle who is also working on Tegra?) > > Hi Meng, > > Many people are working on Nvidia platform with different issues :/. I have > CCed another person which IIRC is also working on it. Sure. It's good to

Re: [Xen-devel] Problem Reading from XenStore in DomU

On 5/16/16 11:20 AM, Dagaen Golomb wrote: > On Mon, May 16, 2016 at 12:11 PM, Dagaen Golomb > wrote: >> On Mon, May 16, 2016 at 12:03 PM, Dagaen Golomb >> wrote: >>> On Mon, May 16, 2016 at 11:55 AM, Doug Goldstein wrote:

Re: [Xen-devel] [PATCHv1 0/2] xen/xenfs: fix /proc/xen/xenbus

On 05/16/2016 01:44 PM, David Vrabel wrote: > "Fix" /proc/xen/xenbus by making it a symlink to the working > /dev/xen/xenbus. Do the same for /proc/xen/privcmd so it matches. > > If there's agreement on this approach I'll resend to Cc the fs > maintainers. Looks good to me. -boris

[Xen-devel] [ovmf test] 94490: regressions - FAIL

flight 94490 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/94490/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-xsm5 xen-build fail REGR. vs. 65543 build-amd64

Re: [Xen-devel] [BUG] Bugs existing Xen's credit scheduler cause long tail latency issues

On Mon, May 16, 2016 at 5:30 AM, Dario Faggioli wrote: > [Adding George, and avoiding trimming, for his benefit] > > On Sat, 2016-05-14 at 22:11 -0600, Tony S wrote: >> Hi all, >> > Hi Tony, > >> When I was running latency-sensitive applications in VMs on Xen, I >>

[Xen-devel] [PATCHv1 2/2] xen/xenfs: replace xenbus and privcmd with symlinks

/proc/xen/xenbus does not work correctly. A read blocked waiting for a xenbus message will deadlock a write to the same file handle due to the requirement for atomic file position updates on regular files. /proc/xen/xenbus and /proc/xen/privcmd are supposed to be identical to the character

[Xen-devel] [xen-unstable-smoke test] 94489: tolerable all pass - PUSHED

flight 94489 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/94489/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass test-armhf-armhf-xl 12

[Xen-devel] [PATCHv1 1/2] libfs: allow simple_fill_super() to add symlinks

simple_fill_super() will add symlinks if an entry has mode & S_IFLNK. The target is provided in the new "link" field. Signed-off-by: David Vrabel --- fs/libfs.c | 23 --- include/linux/fs.h | 2 +- 2 files changed, 21 insertions(+), 4

[Xen-devel] [PATCHv1 0/2] xen/xenfs: fix /proc/xen/xenbus

"Fix" /proc/xen/xenbus by making it a symlink to the working /dev/xen/xenbus. Do the same for /proc/xen/privcmd so it matches. If there's agreement on this approach I'll resend to Cc the fs maintainers. David ___ Xen-devel mailing list

Re: [Xen-devel] Question about running Xen on NVIDIA Jetson-TK1

(CC Kyle who is also working on Tegra?) Hi Meng, Many people are working on Nvidia platform with different issues :/. I have CCed another person which IIRC is also working on it. On 16/05/16 17:33, Meng Xu wrote: On Mon, May 16, 2016 at 7:33 AM, Julien Grall wrote:

Re: [Xen-devel] [PATCH net-next v4 0/4] xen-netback: support for control ring

From: Paul Durrant Date: Fri, 13 May 2016 09:37:25 +0100 > My recent patch to import an up-to-date include/xen/interface/io/netif.h > from the Xen Project brought in the necessary definitions to support the > new control shared ring and protocol. This patch series

[Xen-devel] [qemu-upstream-4.3-testing test] 94480: trouble: blocked/broken

flight 94480 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/94480/ 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

Re: [Xen-devel] Question about running Xen on NVIDIA Jetson-TK1

On 16/05/16 18:26, Konrad Rzeszutek Wilk wrote: Have you tried to dump the registers using Xen console (CTLR-x 3 times then 0) and see where it get stucks? I tried to type CTLR -x 3 times and then 0, nothing happens... :-( Just to confirm, once the system got stuck, I directly type Ctrl-x

Re: [Xen-devel] Question about running Xen on NVIDIA Jetson-TK1

> > > > Have you tried to dump the registers using Xen console (CTLR-x 3 times then > > 0) and see where it get stucks? > > > I tried to type CTLR -x 3 times and then 0, nothing happens... :-( > Just to confirm, once the system got stuck, I directly type Ctrl-x for > three times on the host's

Re: [Xen-devel] [PATCH v3 4/9] arm/vm_event: get/set registers

On 16/05/16 17:26, Tamas K Lengyel wrote: On May 16, 2016 09:59, "Julien Grall" > wrote: >> > By defining 2 distinct structures, it will be more difficult for the >> introspection tools to inspect registers of an Aarch64 domain running in

[Xen-devel] [PATCH] x86/cpuid: Avoid unconditionally clobbering ITSC for guests

In general, Invariant TSC is not a feature which can be advertised to guests, because it cannot be guaranteed across migrate. domain_cpuid() goes so far as to deliberately clobber the feature flag under a number of circumstances. Because ITSC is absent from the static {pv,hvm}_featureset masks,

[Xen-devel] [xen-4.6-testing test] 94474: regressions - FAIL

flight 94474 xen-4.6-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/94474/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-libvirt 5 libvirt-build fail REGR. vs. 93932

Re: [Xen-devel] Question about running Xen on NVIDIA Jetson-TK1

On Mon, May 16, 2016 at 7:33 AM, Julien Grall wrote: > > On 15/05/16 20:35, Meng Xu wrote: >> >> Hi Julien and Ian, > > > Hello Meng, Hi Julien, > >> >> I'm trying to run Xen on NVIDIA Jetson TK1 board. (Right now, Xen does >> not support the Jetson board officially. But

Re: [Xen-devel] [PATCH v2 0/1] xen/device-tree: Do not remap IRQs for secondary IRQ controllers

Hi Wei, On 16/05/16 16:47, Wei Liu wrote: On Mon, May 16, 2016 at 05:03:54PM +0200, Edgar E. Iglesias wrote: From: "Edgar E. Iglesias" I'm sending this as a v2 considering that I previously posted a diff in email discussions. This patch fixes an DT problem with

Re: [Xen-devel] [PATCH v3 4/9] arm/vm_event: get/set registers

On May 16, 2016 09:59, "Julien Grall" wrote: > > Hi Tamas, > > > On 16/05/16 16:37, Tamas K Lengyel wrote: >> >> >> On May 16, 2016 04:14, "Julien Grall" > > wrote: >> > On 04/05/16 15:51, Tamas K Lengyel wrote: >> >> >>

Re: [Xen-devel] Problem Reading from XenStore in DomU

On Mon, May 16, 2016 at 12:11 PM, Dagaen Golomb wrote: > On Mon, May 16, 2016 at 12:03 PM, Dagaen Golomb > wrote: >> On Mon, May 16, 2016 at 11:55 AM, Doug Goldstein wrote: >>> On 5/15/16 8:41 PM, Dagaen Golomb wrote: > On

[Xen-devel] [ovmf test] 94482: regressions - FAIL

flight 94482 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/94482/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-xsm5 xen-build fail REGR. vs. 65543 build-amd64

Re: [Xen-devel] [PATCH V2 1/2] x86/hvm: Add check when register io handler

> -Original Message- > From: Suravee Suthikulpanit [mailto:suravee.suthikulpa...@amd.com] > Sent: 16 May 2016 17:03 > To: Paul Durrant; xen-devel@lists.xen.org; George Dunlap; > jbeul...@suse.com > Subject: Re: [PATCH V2 1/2] x86/hvm: Add check when register io handler > > Hi Paul, > >

Re: [Xen-devel] Problem Reading from XenStore in DomU

On Mon, May 16, 2016 at 12:03 PM, Dagaen Golomb wrote: > On Mon, May 16, 2016 at 11:55 AM, Doug Goldstein wrote: >> On 5/15/16 8:41 PM, Dagaen Golomb wrote: On 5/15/16 8:28 PM, Dagaen Golomb wrote: >> On 5/15/16 11:40 AM, Dagaen Golomb wrote:

[Xen-devel] [PATCH RFC] Tmem cleanups for 4.7 (hopefully?).

Hey, These four little cleanups move the bulk of tmem control ops from tmem.c to tmem_control.c. Last release I moved the control tmem ops from being part of tmem hypercall to be part of the syscall subops - and this is the next step in this cleanup. (See

Re: [Xen-devel] Problem Reading from XenStore in DomU

On Mon, May 16, 2016 at 11:55 AM, Doug Goldstein wrote: > On 5/15/16 8:41 PM, Dagaen Golomb wrote: >>> On 5/15/16 8:28 PM, Dagaen Golomb wrote: > On 5/15/16 11:40 AM, Dagaen Golomb wrote: >> Hi All, >> >> I'm having an interesting issue. I am working on a

Re: [Xen-devel] [PATCH V2 1/2] x86/hvm: Add check when register io handler

Hi Paul, On 05/16/2016 03:01 AM, Paul Durrant wrote: -Original Message- >From:suravee.suthikulpa...@amd.com >[mailto:suravee.suthikulpa...@amd.com] >Sent: 13 May 2016 20:37 >To:xen-devel@lists.xen.org; George Dunlap;jbeul...@suse.com >Cc: Paul Durrant; Suravee Suthikulpanit; Suravee

[Xen-devel] [PATCH RFC 4/4] tmem: Move bulk of tmem control functions in its own file.

The functionality that is related to migration is left inside tmem.c. The list of control operations that are in tmem_control with XEN_SYSCTL_TMEM_OP prefix are: DESTROY, FLUSH, FREEZE, THAW, LIST, QUERY_FREEABLE_MB SAVE_GET_CLIENT_CAP, SAVE_GET_CLIENT_FLAGS, SAVE_GET_CLIENT_WEIGHT,

[Xen-devel] [PATCH RFC 1/4] tmem: Move global stats in a tmem_statistics structure

And adjust the macro: atomic_inc_and_max to update the structure. Sadly one entry: pool->pgp_count cannot use this macro anymore so unroll the macro for this instance. No functional change. The name has the 'tmem_stats' as it will be eventually non-local. Signed-off-by: Konrad Rzeszutek Wilk

[Xen-devel] [PATCH RFC 3/4] tmem: Move global_ individual variables in a global structure.

Put them all in one structure to make it easier to figure out what can be removed. The structure is called 'tmem_global' as it will be eventually non-static. Signed-off-by: Konrad Rzeszutek Wilk --- xen/common/tmem.c | 76

Re: [Xen-devel] [PATCH v3 4/9] arm/vm_event: get/set registers

Hi Tamas, On 16/05/16 16:37, Tamas K Lengyel wrote: On May 16, 2016 04:14, "Julien Grall" > wrote: > On 04/05/16 15:51, Tamas K Lengyel wrote: >> >> diff --git a/xen/include/asm-arm/vm_event.h b/xen/include/asm-arm/vm_event.h >> index

[Xen-devel] [PATCH RFC 2/4] tmem: Wrap atomic_t in struct tmem_statistics as well.

The macros: atomic_inc_and_max and atomic_dec_and_assert use also the 'stats' to access them. Had to open-code access to pool->pgp_count as it would not work anymore. No functional change. Signed-off-by: Konrad Rzeszutek Wilk --- xen/common/tmem.c | 57

[Xen-devel] [xen-4.6-testing bisection] complete build-armhf-libvirt

branch xen-4.6-testing xenbranch xen-4.6-testing job build-armhf-libvirt testid libvirt-build Tree: libvirt git://xenbits.xen.org/libvirt.git Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git Tree: qemuu git://xenbits.xen.org/qemu-xen.git Tree: xen git://xenbits.xen.org/xen.git *** Found and

Re: [Xen-devel] Problem Reading from XenStore in DomU

On 5/15/16 8:41 PM, Dagaen Golomb wrote: >> On 5/15/16 8:28 PM, Dagaen Golomb wrote: On 5/15/16 11:40 AM, Dagaen Golomb wrote: > Hi All, > > I'm having an interesting issue. I am working on a project that > requires me to share memory between dom0 and domUs. I have this >

Re: [Xen-devel] [PATCH v2 0/1] xen/device-tree: Do not remap IRQs for secondary IRQ controllers

On Mon, May 16, 2016 at 05:03:54PM +0200, Edgar E. Iglesias wrote: > From: "Edgar E. Iglesias" > > I'm sending this as a v2 considering that I previously posted a diff > in email discussions. > > This patch fixes an DT problem with the ZynqMP PCIe node. > Today, we

Re: [Xen-devel] Backport requests to stable for Xen ARM

On Mon, 16 May 2016, Julien Grall wrote: > Hello, > > It has been a while without any ARM backport request. Ian Campbell > used to keep a list of backport fixes for Xen ARM and apply them > to stable. Now that he left, I am not sure who will do it. > > I would be fine to keep the list of

Re: [Xen-devel] [PATCH v3 4/9] arm/vm_event: get/set registers

On May 16, 2016 04:14, "Julien Grall" wrote: > > Hi Tamas, > > > On 04/05/16 15:51, Tamas K Lengyel wrote: >> >> diff --git a/xen/include/asm-arm/vm_event.h b/xen/include/asm-arm/vm_event.h >> index a3fc4ce..814d0da 100644 >> --- a/xen/include/asm-arm/vm_event.h >> +++

Re: [Xen-devel] [PATCH v10 1/3] vt-d: add a timeout parameter for Queued Invalidation

On May 13, 2016 11:28 PM, Jan Beulich wrote: > >>> On 22.04.16 at 12:54, wrote: > > --- a/docs/misc/xen-command-line.markdown > > +++ b/docs/misc/xen-command-line.markdown > > @@ -1532,6 +1532,16 @@ Note that if **watchdog** option is also > specified vpmu

Re: [Xen-devel] [PATCH] xen/x86: actually allocate legacy interrupts on PV guests

On Mon, 16 May 2016, Boris Ostrovsky wrote: > On 05/16/2016 07:23 AM, Stefano Stabellini wrote: > > On Wed, 27 Apr 2016, Boris Ostrovsky wrote: > >> On 04/27/2016 09:40 AM, David Vrabel wrote: > >>> On 27/04/16 14:38, Boris Ostrovsky wrote: > int xen_nr_legacy_irqs() > { > if

[Xen-devel] [xen-4.5-testing test] 94469: regressions - FAIL

flight 94469 xen-4.5-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/94469/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-libvirt5 libvirt-build fail REGR. vs. 93989

[Xen-devel] [PATCH v2 0/1] xen/device-tree: Do not remap IRQs for secondary IRQ controllers

From: "Edgar E. Iglesias" I'm sending this as a v2 considering that I previously posted a diff in email discussions. This patch fixes an DT problem with the ZynqMP PCIe node. Today, we try to remap IRQs regardless of if they are directly connected to the primary

Re: [Xen-devel] xc_altp2m_set_vcpu_enable_notify fail

To solve that, I install xen and tools in the guest, so as to access its domain id and vcpu info to overcome the 'domain is null' error. Now the problem is solved, but errors comes at 'domain != DOMID_SELF' checking

[Xen-devel] [PATCH v2 1/1] xen/device-tree: Do not remap IRQs for secondary IRQ controllers

From: "Edgar E. Iglesias" Do not remap IRQs connected to secondary interrupt controllers. These IRQs have no meaning to us until they connect to the primary controller. Secondary IRQ controllers will at some point connect to the primary controller (possibly via other

Re: [Xen-devel] unable to create domain after enabling XSM

Actually I did that, but the policy is not loaded at all. 'xl list -Z' show no lable on guests. It seems like that the option 'xsm=xen-policy-4.6.0' is ingnored during booting. (the policy file is moved to the same directory as xen.cfg) 2016-05-16 21:43 GMT+08:00 Konrad Rzeszutek Wilk

[Xen-devel] [xen-unstable-smoke test] 94483: tolerable all pass - PUSHED

flight 94483 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/94483/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass test-armhf-armhf-xl 12

[Xen-devel] Backport requests to stable for Xen ARM

Hello, It has been a while without any ARM backport request. Ian Campbell used to keep a list of backport fixes for Xen ARM and apply them to stable. Now that he left, I am not sure who will do it. I would be fine to keep the list of patches, although I am not a committer. Stefano do you plan to

[Xen-devel] [for-4.7 2/2] xen/arm: p2m: Release the p2m lock before undoing the mappings

Since commit 4b25423a "arch/arm: unmap partially-mapped memory regions", Xen has been undoing the P2M mappings when an error occurred during insertion or memory allocation. This is done by calling recursively apply_p2m_changes, however the second call is done with the p2m lock taken which will

[Xen-devel] [for-4.7 0/2] xen/arm: Bug fixes in the P2M code

Hello, This small series fixes potential deadlock and the removal of unrelated mapping when the P2M code fails to insert/allocate mappings. This series contains bug fix for Xen 4.7 and candidate for backporting up to Xen 4.5. Yours sincerely, Julien Grall (2): xen/arm: p2m:

[Xen-devel] [for-4.7 1/2] xen/arm: p2m: apply_p2m_changes: Do not undo more than necessary

Since commit 4b25423a "arch/arm: unmap partially-mapped memory regions", Xen has been undoing the P2M mappings when an error occurred during insertion or memory allocation. The function apply_p2m_changes can work with region not-aligned to a block size (2MB, 1G) or page size (4K). The mapping

Re: [Xen-devel] [PATCH] xen/x86: actually allocate legacy interrupts on PV guests

On 05/16/2016 07:23 AM, Stefano Stabellini wrote: > On Wed, 27 Apr 2016, Boris Ostrovsky wrote: >> On 04/27/2016 09:40 AM, David Vrabel wrote: >>> On 27/04/16 14:38, Boris Ostrovsky wrote: int xen_nr_legacy_irqs() { if (xen_hvm_domain()) return nr_legacy_irqs();

Re: [Xen-devel] [RFC 11/16] xen/arm: Detect silicon revision and set cap bits accordingly

Hi Konrad, On 16/05/16 14:50, Konrad Rzeszutek Wilk wrote: On Sat, May 14, 2016 at 07:04:19PM +0100, Julien Grall wrote: Hi Konrad, On 13/05/2016 21:37, Konrad Rzeszutek Wilk wrote: diff --git a/xen/arch/arm/cpufeature.c b/xen/arch/arm/cpufeature.c index 7a1b56b..aa7c5b1 100644 ---

Re: [Xen-devel] [RFC 11/16] xen/arm: Detect silicon revision and set cap bits accordingly

On Sat, May 14, 2016 at 07:04:19PM +0100, Julien Grall wrote: > Hi Konrad, > > On 13/05/2016 21:37, Konrad Rzeszutek Wilk wrote: > >>diff --git a/xen/arch/arm/cpufeature.c b/xen/arch/arm/cpufeature.c > >>index 7a1b56b..aa7c5b1 100644 > >>--- a/xen/arch/arm/cpufeature.c > >>+++

Re: [Xen-devel] [TESTDAY] Test report

On 16/05/16 14:41, Edgar E. Iglesias wrote: On Mon, May 16, 2016 at 02:20:24PM +0100, Julien Grall wrote: No, they are not necessary. We have a few options. 1. If we do nothing, the ZynqMP boards with PCIe support won't even boot dom0. 2. A safe option is to disable the PCIe node in the

Re: [Xen-devel] unable to create domain after enabling XSM

On Mon, May 16, 2016 at 10:43:49AM +0100, Andrew Cooper wrote: > On 16/05/16 09:54, Big Strong wrote: > > Problem solved by booting xen with grub instead of efi. The deep > > reason is unknown. > > Ah - that is very useful to know, and now obvious. EFI has no concept > of modules, which probably

Re: [Xen-devel] [TESTDAY] Test report

On Mon, May 16, 2016 at 02:20:24PM +0100, Julien Grall wrote: > Hello Edgar, > > On 14/05/16 20:04, Edgar E. Iglesias wrote: > >On Sat, May 14, 2016 at 07:15:55PM +0100, Julien Grall wrote: > >You can see that it is used in the interrupt-map properties. > >IIUC, the interrupt lines connected to

Re: [Xen-devel] [TESTDAY] Test report

Hello Edgar, On 14/05/16 20:04, Edgar E. Iglesias wrote: On Sat, May 14, 2016 at 07:15:55PM +0100, Julien Grall wrote: You can see that it is used in the interrupt-map properties. IIUC, the interrupt lines connected to the pcie_intc controller are simply going to be combined into the "intx"

Re: [Xen-devel] Problem Reading from XenStore in DomU

Regards, Dagaen Golomb On May 16, 2016 09:13, "Jonathan Creekmore" wrote: > > > Dagaen Golomb writes: > > > It does, being the custom kernel on version 4.1.0. But Dom0 uses this same > > exact kernel and reads/writes just fine! The only solution if this is > > indeed

Re: [Xen-devel] Problem Reading from XenStore in DomU

Dagaen Golomb writes: > It does, being the custom kernel on version 4.1.0. But Dom0 uses this same > exact kernel and reads/writes just fine! The only solution if this is > indeed the problem appears to be changing the kernel source we build on or > some hacky method such as symlinking /proc/..

[Xen-devel] [xen-unstable test] 94461: tolerable FAIL - PUSHED

flight 94461 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/94461/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail in 94442 pass in 94461

[Xen-devel] [ovmf test] 94470: regressions - FAIL

flight 94470 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/94470/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-xsm5 xen-build fail REGR. vs. 65543 build-amd64

Re: [Xen-devel] potential problem with qdisk backend

On Wed, 11 May 2016, Juergen Gross wrote: > On 06/05/16 13:41, Juergen Gross wrote: > > Looking at the qdisk backend implementation I wondered whether > > blkif_get_x86_32_req() is really correct, especially for the > > BLKIF_OP_DISCARD case. The Linux kernel based blk backend seems to > >

Re: [Xen-devel] [BUG] Linux process vruntime accounting in Xen

[Adding George again, and a few Linux/Xen folks] On Sat, 2016-05-14 at 18:25 -0600, Tony S wrote: > In virtualized environments, sometimes we need to limit the CPU > resources to a virtual machine(VM). For example in Xen, we use > $ xl sched-credit -d 1 -c 50 > > to limit the CPU resource of dom

Re: [Xen-devel] Question about running Xen on NVIDIA Jetson-TK1

On 15/05/16 20:35, Meng Xu wrote: Hi Julien and Ian, Hello Meng, I'm trying to run Xen on NVIDIA Jetson TK1 board. (Right now, Xen does not support the Jetson board officially. But I'm thinking it may be very interesting and useful to see it happens, since it has GPU inside which is quite

Re: [Xen-devel] [BUG] Bugs existing Xen's credit scheduler cause long tail latency issues

[Adding George, and avoiding trimming, for his benefit] On Sat, 2016-05-14 at 22:11 -0600, Tony S wrote: > Hi all, > Hi Tony, > When I was running latency-sensitive applications in VMs on Xen, I > found some bugs in the credit scheduler which will cause long tail > latency in I/O-intensive VMs.

[Xen-devel] [libvirt test] 94465: tolerable FAIL - PUSHED

flight 94465 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/94465/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 14 guest-saverestorefail never pass test-armhf-armhf-libvirt 12

Re: [Xen-devel] [PATCH v4 4/4] arm64: update the introduction of xen boot commands in docs/grub.texi

Hi Fu Wei, (CC Stefano) On 10/05/16 15:03, fu@linaro.org wrote: From: Fu Wei delete: xen_linux, xen_initrd, xen_xsm add: xen_module This update bases on commit 0edd750e50698854068358ea53528100a9192902 Author: Vladimir Serbinenko

Re: [Xen-devel] [PATCH] xen/x86: actually allocate legacy interrupts on PV guests

On Wed, 27 Apr 2016, Boris Ostrovsky wrote: > On 04/27/2016 09:40 AM, David Vrabel wrote: > > On 27/04/16 14:38, Boris Ostrovsky wrote: > > > int xen_nr_legacy_irqs() > > > { > > > if (xen_hvm_domain()) > > > return nr_legacy_irqs(); > > > if (xen_initial_domain()) > > >

[Xen-devel] [qemu-upstream-4.3-testing test] 94472: trouble: blocked/broken

flight 94472 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/94472/ 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

Re: [Xen-devel] [PATCH] xen: remove incorrect forward declaration

On Wed, 11 May 2016, Arnd Bergmann wrote: > A bugfix patch for the xen balloon driver introduced a forward > declaration for a static function that is conditionally compiled, > causing a warning if only the declaration but not the definition > are there: > > drivers/xen/balloon.c:154:13: error:

Re: [Xen-devel] [PATCH] Xen: don't warn about 2-byte wchar_t in efi

On Wed, 11 May 2016, Arnd Bergmann wrote: > The XEN UEFI code has become available on the ARM architecture > recently, but now causes a link-time warning: > > ld: warning: drivers/xen/efi.o uses 2-byte wchar_t yet the output is to use > 4-byte wchar_t; use of wchar_t values across objects may

Re: [Xen-devel] [PATCH for-4.7] x86/compat: Cleanup and further debugging of SMAP/SMEP fixup

On Mon, May 16, 2016 at 11:49:31AM +0100, Andrew Cooper wrote: > * Abstract (X86_CR4_SMEP | X86_CR4_SMAP) behind XEN_CR4_PV32_BITS to avoid >opencoding the invidial bits which are fixed up behind a 32bit PV guests >back. > * In the debug case, perform the the AND and CMP on 64bit values

[Xen-devel] [PATCH for-4.7] x86/compat: Cleanup and further debugging of SMAP/SMEP fixup

* Abstract (X86_CR4_SMEP | X86_CR4_SMAP) behind XEN_CR4_PV32_BITS to avoid opencoding the invidial bits which are fixed up behind a 32bit PV guests back. * In the debug case, perform the the AND and CMP on 64bit values rather than 32bit values, to match the logic in then non-debug case.

Re: [Xen-devel] problem on running xen on CentOS 7 on APM X-Gene Aarch64 platform

CC'ing xen-devel and Julien and George. The grub2 package coming with CentOS is not capable of booting Xen on arm64. When you do "yum update" after "yum install centos-release-xen", you should be getting a new grub2 package with Xen support in it. But it looks like that is not happening for you.

Re: [Xen-devel] [PATCH V3 2/2] xen/arm: mm: clean up code in setup_pagetables

On Mon, 16 May 2016, Julien Grall wrote: > Hi Peng, > > On 12/05/16 12:48, Peng Fan wrote: > > The base of address for the relocated xen needs to be mapped > > at the same virtual address (BOOT_RELOC_VIRT_START) in both > > the boot and runtime page tables. So we can merge the two pieces > > of

Re: [Xen-devel] [PATCH v2] Xen: EFI: Parse DT parameters for Xen specific UEFI

On Fri, 13 May 2016, Matt Fleming wrote: > (Including more folks, quoting entire patch) > > On Thu, 12 May, at 08:19:54PM, Shannon Zhao wrote: > > From: Shannon Zhao > > > > The EFI DT parameters for bare metal are located under /chosen node, > > while for Xen Dom0 they

Re: [Xen-devel] [PATCH v3 4/9] arm/vm_event: get/set registers

Hi Tamas, On 04/05/16 15:51, Tamas K Lengyel wrote: diff --git a/xen/include/asm-arm/vm_event.h b/xen/include/asm-arm/vm_event.h index a3fc4ce..814d0da 100644 --- a/xen/include/asm-arm/vm_event.h +++ b/xen/include/asm-arm/vm_event.h @@ -48,15 +48,10 @@ void vm_event_register_write_resume(struct

Re: [Xen-devel] [TESTDAY] Test report

On Sat, May 14, 2016 at 09:04:35PM +0200, Edgar E. Iglesias wrote: [...] > > Was PCIe working on Xen 4.6? If yes, it's the regression and we could > > consider it as a blocker for the release (CC Wei for that). > > No, these PCIe nodes were added recently. > The device tree bindings were

  1   2   >