Re: [Xen-devel] [PATCH v5 2/4] x86/ldt: Make modify_ldt synchronous

On Mon, Jul 27, 2015 at 10:29:39PM -0700, Andy Lutomirski wrote: > modify_ldt has questionable locking and does not synchronize > threads. Improve it: redesign the locking and synchronize all > threads' LDTs using an IPI on all modifications. > > This will dramatically slow down modify_ldt in mul

Re: [Xen-devel] [xen-unstable test] 60076: regressions - FAIL

On Wed, 2015-07-29 at 15:15 +0100, Julien Grall wrote: > On 29/07/15 15:10, Julien Grall wrote: > > osstest is waiting 40s to get the network ready in the guest. When the > > test pass, the osstest is likely waiting ~20s to pass it. I took the > > time between > > > > guest debian.guest.osstest 5

Re: [Xen-devel] Second regression due to libxl: Remove linux udev rules (2ba368d13893402b2f1fb3c283ddcc714659dd9b)

On Wed, 2015-07-29 at 11:45 -0400, Konrad Rzeszutek Wilk wrote: > relying on the (stale) 4.5 rules file having the UDEV_CALL=1 in them. > > I don't exactly understand how the hotplug scripts are invoked via 'xl'. They are called when the backend gets to (or passes through) XenbusStateInitWait (at

Re: [Xen-devel] Second regression due to libxl: Remove linux udev rules (2ba368d13893402b2f1fb3c283ddcc714659dd9b)

El 30/07/15 a les 10.17, Ian Campbell ha escrit: [...] > The udev scripts should have been unused since 4.5.0-rc1, where they were udev scripts have been unused since 4.2 on Dom0, not 4.5. See: b24dc64ef34437c958b40a71f510f404e0c4bbe4 57ad6afe2a08a03c40bcd336bfb27e008e1d3e53 Roger.

Re: [Xen-devel] [xen-unstable test] 60107: regressions - FAIL

On Wed, 2015-07-29 at 21:01 +, osstest service owner wrote: > flight 60107 xen-unstable real [real] > http://logs.test-lab.xenproject.org/osstest/logs/60107/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-xl-

Re: [Xen-devel] Second regression due to libxl: Remove linux udev rules (2ba368d13893402b2f1fb3c283ddcc714659dd9b)

El 28/07/15 a les 21.47, Konrad Rzeszutek Wilk ha escrit: > Hey, > > I launch a bunch of guests at the same time or in parallel and > the scripts end up timing out with: > > > Parsing config from //g-vm8.cfg > WARNING: you seem to be using "kernel" directive to override HVM guest > firmware. I

Re: [Xen-devel] Second regression due to libxl: Remove linux udev rules (2ba368d13893402b2f1fb3c283ddcc714659dd9b)

On Thu, 2015-07-30 at 10:43 +0200, Roger Pau Monné wrote: > El 30/07/15 a les 10.17, Ian Campbell ha escrit: > [...] > > The udev scripts should have been unused since 4.5.0-rc1, where they > > were > > udev scripts have been unused since 4.2 on Dom0, not 4.5. See: > > b24dc64ef34437c958b40a71f5

Re: [Xen-devel] Arndale secondary CPU boot issue Was Re: [xen-unstable test] 60076: regressions - FAIL

On Wed, 2015-07-29 at 19:18 +0100, Julien Grall wrote: As an aside from the issue you are seeing: > The old implementation of spinlock is sending an event (via the assembly > instruction SEV) to the other physical CPUs. This will wake up the > others CPUs waiting on the assembly instruction WFE (

Re: [Xen-devel] [PATCH for 4.6] x86/hvm.c: fix regression in guest destruction

On Wed, 2015-07-29 at 17:44 +0100, Andrew Cooper wrote: > On 29/07/15 17:39, Ravi Sahita wrote: > > As reported by Wei Lu on July 27 2015 > > Reported-by: Wei Liu Which leaves an effectively empty commit message: x86/hvm.c: fix regression in guest destruction Reported-by: Wei Liu <

Re: [Xen-devel] [PATCH for 4.6] x86/p2m.c: fix missed off-by-one in altp2m commit

On Wed, 2015-07-29 at 17:46 +0100, Andrew Cooper wrote: > On 29/07/15 17:40, Ravi Sahita wrote: > > Signed-off-by: Ravi Sahita > > Reviewed-by: Andrew Cooper Applied. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH for 4.6] x86/hvm.c: fix regression in guest destruction

On Thu, 2015-07-30 at 10:21 +0100, Ian Campbell wrote: > which I have applied with. I still don't think the commit message is very > satisfactory, but I'm not maintainer of any of this code so meh. For the benefit of the archives perhaps someone could explain why gating a per-vcpu teardown on a h

Re: [Xen-devel] [PATCH for 4.6] x86/hvm.c: fix regression in guest destruction

On 07/30/2015 10:32 AM, Ian Campbell wrote: > On Thu, 2015-07-30 at 10:21 +0100, Ian Campbell wrote: > >> which I have applied with. I still don't think the commit message is very >> satisfactory, but I'm not maintainer of any of this code so meh. > > For the benefit of the archives perhaps someo

Re: [Xen-devel] [PATCH for 4.6] x86/hvm.c: fix regression in guest destruction

On Thu, 2015-07-30 at 10:38 +0100, George Dunlap wrote: > On 07/30/2015 10:32 AM, Ian Campbell wrote: > > On Thu, 2015-07-30 at 10:21 +0100, Ian Campbell wrote: > > > > > which I have applied with. I still don't think the commit message is > > > very > > > satisfactory, but I'm not maintainer of

Re: [Xen-devel] PCI Pass-through in Xen ARM - Draft 2.

On Wed, 2015-07-29 at 15:07 +0530, Manish Jaggi wrote: > > On Monday 06 July 2015 03:50 PM, Ian Campbell wrote: > > On Mon, 2015-07-06 at 15:36 +0530, Manish Jaggi wrote: > > > On Monday 06 July 2015 02:41 PM, Ian Campbell wrote: > > > > On Sun, 2015-07-05 at 11:25 +0530, Manish Jaggi wrote: > > >

Re: [Xen-devel] [PATCH for 4.6] x86/hvm.c: fix regression in guest destruction

On 30/07/15 10:32, Ian Campbell wrote: > Also how come HVMOP_altp2m_set_domain_state does not have a > hvm_altp2m_supported check? (For the benefit of not leaving this question unanswered) There is an early exit at the top of do_altp2m_op(), ahead of even reading the hypercall body from the guest

Re: [Xen-devel] [PATCH for-4.6 0/2] Replace FSF street address with canonical URL

These are only mechanical changes and I deem this fall into "keep documentation up to date" category, so with my RM hat on. Release-acked-by: Wei Liu ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH for-4.6 0/2] Replace FSF street address with canonical URL

On 29/07/15 11:35, Ian Campbell wrote: > We currently have numerous variations on the FSF's addresses, old, new and > plain incorrect (there was a buggy version in circulation at one time). > > The current recommendation in http://www.gnu.org/licenses/gpl-howto.en.html > is to use "If not, see

Re: [Xen-devel] HVM guest max memory allocation

On Thu, Jul 30, 2015 at 06:21:06AM +, Hao, Xudong wrote: > > -Original Message- > > From: Wei Liu [mailto:wei.l...@citrix.com] > > Sent: Friday, July 24, 2015 3:29 PM > > To: Hao, Xudong > > Cc: xen-devel@lists.xen.org; Wu, Feng; wei.l...@citrix.com > > Subject: Re: [Xen-devel] HVM gues

Re: [Xen-devel] [PATCH for 4.6] x86/hvm.c: fix regression in guest destruction

On Thu, 2015-07-30 at 10:55 +0100, Andrew Cooper wrote: > On 30/07/15 10:32, Ian Campbell wrote: > > Also how come HVMOP_altp2m_set_domain_state does not have a > > hvm_altp2m_supported check? > > (For the benefit of not leaving this question unanswered) > > There is an early exit at the top of d

Re: [Xen-devel] [BUG] Emulation issues

> -Original Message- > From: Roger Pau Monné [mailto:roger@citrix.com] > Sent: 29 July 2015 14:54 > To: Paul Durrant; xen-devel; Andrew Cooper > Subject: Re: [BUG] Emulation issues > > El 29/07/15 a les 14.41, Paul Durrant ha escrit: > >> -Original Message- > >> From: Roger Pau

Re: [Xen-devel] [BUG] Emulation issues

El 30/07/15 a les 12.12, Paul Durrant ha escrit: >> -Original Message- >> From: Roger Pau Monné [mailto:roger@citrix.com] >> Sent: 29 July 2015 14:54 >> To: Paul Durrant; xen-devel; Andrew Cooper >> Subject: Re: [BUG] Emulation issues >> I've applied your patch and the one from Andrew,

Re: [Xen-devel] [BUG] Emulation issues

> -Original Message- > From: Roger Pau Monné [mailto:roger@citrix.com] > Sent: 30 July 2015 11:17 > To: Paul Durrant; xen-devel; Andrew Cooper > Subject: Re: [BUG] Emulation issues > > El 30/07/15 a les 12.12, Paul Durrant ha escrit: > >> -Original Message- > >> From: Roger Pau

Re: [Xen-devel] [PATCH v2] build: use correct qemu path in systemd service file and init script

On Thu, 2015-07-30 at 14:51 +0800, Ting-Wei Lan wrote: > When --with-system-qemu is used, it is possible that we cannot find > qemu-system-i386 in LIBEXEC_BIN, which can cause error in xencommons > init script and xen-qemu-dom0-disk-backend.service systemd service. > > Signed-off-by: Ting-Wei Lan

Re: [Xen-devel] [BUG] Emulation issues

On 30/07/15 11:24, Andrew Cooper wrote: > On 30/07/15 11:16, Roger Pau Monné wrote: >> El 30/07/15 a les 12.12, Paul Durrant ha escrit: -Original Message- From: Roger Pau Monné [mailto:roger@citrix.com] Sent: 29 July 2015 14:54 To: Paul Durrant; xen-devel; Andrew Coo

Re: [Xen-devel] [BUG] Emulation issues

On 30/07/15 11:16, Roger Pau Monné wrote: > El 30/07/15 a les 12.12, Paul Durrant ha escrit: >>> -Original Message- >>> From: Roger Pau Monné [mailto:roger@citrix.com] >>> Sent: 29 July 2015 14:54 >>> To: Paul Durrant; xen-devel; Andrew Cooper >>> Subject: Re: [BUG] Emulation issues >>>

[Xen-devel] Vote for Xen talks at OpenStack summit (deadline today)

So far, I am aware of one talk. Note that the OpenStack summit agenda's are determined by popular vote (which ends today). If there are others Xen related talks, feel free to add by replying to this mail https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/Presentation/6150

Re: [Xen-devel] [PATCH v2] build: use correct qemu path in systemd service file and init script

On Thu, Jul 30, 2015 at 11:24:47AM +0100, Ian Campbell wrote: > On Thu, 2015-07-30 at 14:51 +0800, Ting-Wei Lan wrote: > > When --with-system-qemu is used, it is possible that we cannot find > > qemu-system-i386 in LIBEXEC_BIN, which can cause error in xencommons > > init script and xen-qemu-dom0-d

Re: [Xen-devel] Arndale secondary CPU boot issue Was Re: [xen-unstable test] 60076: regressions - FAIL

On 29/07/15 19:18, Julien Grall wrote: > On 29/07/15 15:15, Julien Grall wrote: Can it be that things are "just" slow, since we're creating a 4 vcpus guest on a 1 pcpu (not so powerful, I guess) host? >>> The arndale board has a 2 physical CPUs. Although it looks like that the >>> seconda

Re: [Xen-devel] Arndale secondary CPU boot issue Was Re: [xen-unstable test] 60076: regressions - FAIL

On Thu, 30 Jul 2015, Ian Campbell wrote: > On Wed, 2015-07-29 at 19:18 +0100, Julien Grall wrote: > > As an aside from the issue you are seeing: > > > The old implementation of spinlock is sending an event (via the assembly > > instruction SEV) to the other physical CPUs. This will wake up the >

Re: [Xen-devel] [Xen-Devel] Enabling IRQ Crossbar (Secondary Interrupt Controller) Support

On Wed, 2015-07-29 at 16:36 -0400, Brandon Perez wrote: > On 07/21/2015 11:12 AM, Ian Campbell wrote: > > On Tue, 2015-07-21 at 10:07 -0400, Brandon Perez wrote: > > > > > > I'm not sure that these patches are quite ready yet to be put > > > into > > > the Xen repo. > > > > That's ok, but e

Re: [Xen-devel] [BUG] Emulation issues

> -Original Message- [big snip] > Sorry, missed that in the noise. So, the problem is that there is no > in-flight I/O > even though pio completion is being attempted. Something has got out of > sync. > I think I understand what may be happening... The code in hvmemul_do_io() basically

Re: [Xen-devel] [PATCH] tools: Update libxl flex outputs to Flex from Jessie.

On Wed, Jul 15, 2015 at 11:21:17AM +0100, Ian Campbell wrote: > This is the result of > $ find -name \*.l -exec touch {} \; > $ find -name \*.y -exec touch {} \; > > and then rebuilding. > > This avoids churn on the machine I use for committing which has been > updated, causing flex to go fro

Re: [Xen-devel] [PATCH for-2.4 0/3] Migration regressions with Xen.

Anthony PERARD wrote: > This is a critical issue for Xen as migration either with the same version > of QEMU, or from a previous version of QEMU is broken. > > Any suggestion on how to move forward? Will send a pull requset tomorrow. Thinking about creating a single function that is called for a

Re: [Xen-devel] [PATCH RFC] DRA7: Add specific mappings for devices/regions not in the device tree.

On Wed, 2015-07-29 at 16:53 -0400, Brandon Perez wrote: > The DRA7 chip, which is similar to the OMAP5 chip, also requires specific > mappings. These are MMIO mappings which are not explicitly stated in the > device > tree, so Xen does not know to map them. This patch adds these regions required >

Re: [Xen-devel] [PATCH RFC] Traps: Enable pass-through SMC call support for guest OS's.

On Wed, 2015-07-29 at 16:53 -0400, Brandon Perez wrote: > Originally, Xen did not allow for guests to make SMC calls. However, on the > DRA7 > chips, the kernel needs to make several SMC calls to interact with the secure > ROM code. > > There are two solutions for solving this in the patch. The s

Re: [Xen-devel] [PATCH v2] build: use correct qemu path in systemd service file and init script

On Thu, Jul 30, 2015 at 11:24:47AM +0100, Ian Campbell wrote: > On Thu, 2015-07-30 at 14:51 +0800, Ting-Wei Lan wrote: > > When --with-system-qemu is used, it is possible that we cannot find > > qemu-system-i386 in LIBEXEC_BIN, which can cause error in xencommons > > init script and xen-qemu-dom0-d

Re: [Xen-devel] [Xen-Devel] Enabling IRQ Crossbar (Secondary Interrupt Controller) Support

On Wed, 2015-07-29 at 16:36 -0400, Brandon Perez wrote: > On 07/21/2015 11:12 AM, Ian Campbell wrote: > > On Tue, 2015-07-21 at 10:07 -0400, Brandon Perez wrote: > > > > > > I'm not sure that these patches are quite ready yet to be put > > > into > > > the Xen repo. > > > > That's ok, but e

Re: [Xen-devel] [PATCH for-2.4 0/3] Migration regressions with Xen.

On Thu, 30 Jul 2015, Juan Quintela wrote: > Anthony PERARD wrote: > > This is a critical issue for Xen as migration either with the same version > > of QEMU, or from a previous version of QEMU is broken. > > > > Any suggestion on how to move forward? > > Will send a pull requset tomorrow. > > Th

Re: [Xen-devel] Arndale secondary CPU boot issue Was Re: [xen-unstable test] 60076: regressions - FAIL

On Thu, 2015-07-30 at 11:54 +0100, Stefano Stabellini wrote: > On Thu, 30 Jul 2015, Ian Campbell wrote: > > On Wed, 2015-07-29 at 19:18 +0100, Julien Grall wrote: > > > > As an aside from the issue you are seeing: > > > > > The old implementation of spinlock is sending an event (via the > > > as

Re: [Xen-devel] Arndale secondary CPU boot issue Was Re: [xen-unstable test] 60076: regressions - FAIL

On 30/07/15 11:54, Stefano Stabellini wrote: > On Thu, 30 Jul 2015, Ian Campbell wrote: >> On Wed, 2015-07-29 at 19:18 +0100, Julien Grall wrote: >> >> As an aside from the issue you are seeing: >> >>> The old implementation of spinlock is sending an event (via the assembly >>> instruction SEV) to

Re: [Xen-devel] [PATCH RFC] ARM/IRQ-Crossbar: Make Xen aware of devices being statically mapped in the IRQ crossbar.

On Wed, 2015-07-29 at 16:53 -0400, Brandon Perez wrote: > In general, Xen needs to own very few interrupts to run. Most of these are > timer > PPIs, which do not involve the crossbar. The notable exception to this is the > serial device, which is an SPI. On the DRA7 chips, this involves going thro

Re: [Xen-devel] [PATCH v2] build: use correct qemu path in systemd service file and init script

On Thu, 2015-07-30 at 12:23 +0100, Anthony PERARD wrote: > On Thu, Jul 30, 2015 at 11:24:47AM +0100, Ian Campbell wrote: > > On Thu, 2015-07-30 at 14:51 +0800, Ting-Wei Lan wrote: > > > When --with-system-qemu is used, it is possible that we cannot find > > > qemu-system-i386 in LIBEXEC_BIN, which

Re: [Xen-devel] Arndale secondary CPU boot issue Was Re: [xen-unstable test] 60076: regressions - FAIL

Hi Ian, On 30/07/15 09:55, Ian Campbell wrote: > On Wed, 2015-07-29 at 19:18 +0100, Julien Grall wrote: >> It appears to be required on the Arndale to boot secondaries CPUs. >> Although, depending on where I put the sev I don't have the same >> behavior: >> - sev in smp_init callback: the CP

Re: [Xen-devel] Vote for Xen talks at OpenStack summit (deadline today)

On 07/30/2015 12:29 PM, Lars Kurth wrote: So far, I am aware of one talk. Note that the OpenStack summit agenda's are determined by popular vote (which ends today). If there are others Xen related talks, feel free to add by replying to this mail https://www.openstack.org/summit/tokyo-2015/vote-f

Re: [Xen-devel] [PATCH v2 32/41] arm : acpi dynamically map mmio regions

On 2015/7/5 21:30, Parth Dixit wrote: > +shannon > > On 15 June 2015 at 06:49, Julien Grall wrote: >> Hi Parth, >> >> On 14/06/2015 11:27, Parth Dixit wrote: >>> >>> On 8 June 2015 at 22:20, Julien Grall wrote: Hi Parth, On 17/05/2015 21:03, Parth Dixit wrote: > > >

Re: [Xen-devel] PCI Pass-through in Xen ARM - Draft 2.

On Thursday 30 July 2015 03:24 PM, Ian Campbell wrote: On Wed, 2015-07-29 at 15:07 +0530, Manish Jaggi wrote: On Monday 06 July 2015 03:50 PM, Ian Campbell wrote: On Mon, 2015-07-06 at 15:36 +0530, Manish Jaggi wrote: On Monday 06 July 2015 02:41 PM, Ian Campbell wrote: On Sun, 2015-07-05 a

Re: [Xen-devel] [BUG] Emulation issues

El 30/07/15 a les 12.59, Paul Durrant ha escrit: >> -Original Message- > [big snip] >> Sorry, missed that in the noise. So, the problem is that there is no >> in-flight I/O >> even though pio completion is being attempted. Something has got out of >> sync. >> > > I think I understand what

Re: [Xen-devel] [BUG] Emulation issues

> -Original Message- > From: Roger Pau Monné [mailto:roger@citrix.com] > Sent: 30 July 2015 14:06 > To: Paul Durrant; xen-devel; Andrew Cooper > Subject: Re: [BUG] Emulation issues > > El 30/07/15 a les 12.59, Paul Durrant ha escrit: > >> -Original Message- > > [big snip] > >>

Re: [Xen-devel] [BUG] Emulation issues

On 30/07/15 14:12, Paul Durrant wrote: >> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1. >> (XEN) domain_crash called from io.c:166 >> (XEN) d19v0 weird emulation state 1 >> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1. >> (XEN) domain_crash called from io.c:166 >> (XEN) d19v0 weird em

Re: [Xen-devel] [BUG] Emulation issues

> -Original Message- > From: Andrew Cooper [mailto:andrew.coop...@citrix.com] > Sent: 30 July 2015 14:19 > To: Paul Durrant; Roger Pau Monne; xen-devel > Subject: Re: [BUG] Emulation issues > > On 30/07/15 14:12, Paul Durrant wrote: > >> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1.

Re: [Xen-devel] [Xen-Devel] Enabling IRQ Crossbar (Secondary Interrupt Controller) Support

On 07/30/2015 07:23 AM, Ian Campbell wrote: On Wed, 2015-07-29 at 16:36 -0400, Brandon Perez wrote: On 07/21/2015 11:12 AM, Ian Campbell wrote: On Tue, 2015-07-21 at 10:07 -0400, Brandon Perez wrote: I'm not sure that these patches are quite ready yet to be put into the Xen repo. Tha

Re: [Xen-devel] [Xen-Devel] Enabling IRQ Crossbar (Secondary Interrupt Controller) Support

On 07/30/2015 06:57 AM, Ian Campbell wrote: On Wed, 2015-07-29 at 16:36 -0400, Brandon Perez wrote: On 07/21/2015 11:12 AM, Ian Campbell wrote: On Tue, 2015-07-21 at 10:07 -0400, Brandon Perez wrote: I'm not sure that these patches are quite ready yet to be put into the Xen repo. Tha

[Xen-devel] [PATCH OSSTEST] Executive: Change Cambridge specific default

ControlDaemonHost is unused in production-config* since they both set {Owner,Queue}DaemonHost explicitly. Some sort of default seems useful, so switch it to just "control-daemons" in the DNS domain of the controller. Signed-off-by: Ian Campbell --- Osstest/Executive.pm | 2 +- 1 file changed, 1

[Xen-devel] [PATCH OSSTEST] crontab-cambridge: Add a commented out adhoc bisect line

This is handy to have, editing it in locally just means one cannot simply use "crontab contab-cambridge" to load a new one without remembering the content of the line for next time. Signed-off-by: Ian Campbell --- crontab-cambridge | 1 + 1 file changed, 1 insertion(+) diff --git a/crontab-camb

[Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad

(CC-ing 2x QEMU maintainers and stable release manager) The separate trees are a holdover from mercurial, which didn't (at the time) have a good in-repo branching model. I propose that Xen 4.6 should be the last release which uses these split trees and that instead we combine them into just qemu-

Re: [Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad

Ian Campbell writes ("[RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad"): ... > qemu-xen-traditional: ... > XXX why do staging/* exist, and what pushes from staging to the other? > Should we ditch one or the other? Once upon a time, some of these had their own

Re: [Xen-devel] PCI Pass-through in Xen ARM - Draft 2.

On Thu, 2015-07-30 at 18:21 +0530, Manish Jaggi wrote: > > On Thursday 30 July 2015 03:24 PM, Ian Campbell wrote: > > On Wed, 2015-07-29 at 15:07 +0530, Manish Jaggi wrote: > > > On Monday 06 July 2015 03:50 PM, Ian Campbell wrote: > > > > On Mon, 2015-07-06 at 15:36 +0530, Manish Jaggi wrote: > >

Re: [Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad

On 30/07/15 15:22, Ian Campbell wrote: > (CC-ing 2x QEMU maintainers and stable release manager) > > The separate trees are a holdover from mercurial, which didn't (at the > time) have a good in-repo branching model. > > I propose that Xen 4.6 should be the last release which uses these split > tre

Re: [Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad

On Thu, 2015-07-30 at 15:33 +0100, Ian Jackson wrote: > Ian Campbell writes ("[RFC for-4.7] Switching to a single qemu tree each > per qemu-xen and qemu-trad"): > ... > > qemu-xen-traditional: > ... > > XXX why do staging/* exist, and what pushes from staging to the > > other? > > Should

Re: [Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad

Ian Campbell writes: > (CC-ing 2x QEMU maintainers and stable release manager) > > The separate trees are a holdover from mercurial, which didn't (at the > time) have a good in-repo branching model. > > I propose that Xen 4.6 should be the last release which uses these split > trees and that inst

Re: [Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad

On Thu, 2015-07-30 at 16:51 +0200, Vitaly Kuznetsov wrote: > Ian Campbell writes: > > > (CC-ing 2x QEMU maintainers and stable release manager) > > > > The separate trees are a holdover from mercurial, which didn't (at the > > time) have a good in-repo branching model. > > > > I propose that Xe

Re: [Xen-devel] [PATCH v2] build: use correct qemu path in systemd service file and init script

On Thu, 2015-07-30 at 11:30 +0100, Wei Liu wrote: > On Thu, Jul 30, 2015 at 11:24:47AM +0100, Ian Campbell wrote: > > On Thu, 2015-07-30 at 14:51 +0800, Ting-Wei Lan wrote: > > > When --with-system-qemu is used, it is possible that we cannot find > > > qemu-system-i386 in LIBEXEC_BIN, which can cau

Re: [Xen-devel] [PATCH for-4.6 0/2] Replace FSF street address with canonical URL

On Thu, 2015-07-30 at 10:56 +0100, Wei Liu wrote: > These are only mechanical changes and I deem this fall into > "keep documentation up to date" category, so with my RM hat on. > > Release-acked-by: Wei Liu Thanks, I also ran this by Ian J and he saw no reason not to go ahead. So I have merged

[Xen-devel] 4.6 release bug lists

Hi all Here are some bugs that I'm aware of. The name after a item is the person who is working on it. # Blockers 1. Toolstack record breaks migration v2 (Andrew Cooper) 2. Block hotplug scripts invoked multiple times (Roger Pau Monne) # Non-blockers 1. QEMU block script doesn't work (George

Re: [Xen-devel] 4.6 release bug lists

El 30/07/15 a les 17.04, Wei Liu ha escrit: > Hi all > > Here are some bugs that I'm aware of. The name after a item is the > person who is working on it. > > # Blockers > > 1. Toolstack record breaks migration v2 (Andrew Cooper) > 2. Block hotplug scripts invoked multiple times (Roger Pau Monne

Re: [Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad

Andrew Cooper writes ("Re: [Xen-devel] [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad"): > And take the change to drop the other random branches in the repository > By my observations: > > $ git remote show upstream > * remote upstream > ... > Remote branches:

[Xen-devel] [PATCH for-4.6] xl/libxl: disable PV vNUMA

Update xl manual and disable PV vNUMA in libxl. Signed-off-by: Wei Liu --- Cc: Ian Campbell Cc: Ian Jackson Cc: Dario Faggioli --- docs/man/xl.cfg.pod.5 | 4 tools/libxl/libxl_create.c | 9 + 2 files changed, 13 insertions(+) diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl

Re: [Xen-devel] [PATCH for-4.6] xl/libxl: disable PV vNUMA

El 30/07/15 a les 17.12, Wei Liu ha escrit: > Update xl manual and disable PV vNUMA in libxl. > > Signed-off-by: Wei Liu > --- > Cc: Ian Campbell > Cc: Ian Jackson > Cc: Dario Faggioli > --- > docs/man/xl.cfg.pod.5 | 4 > tools/libxl/libxl_create.c | 9 + > 2 files changed,

Re: [Xen-devel] [PATCH v2] build: use correct qemu path in systemd service file and init script

On Thu, Jul 30, 2015 at 6:35 AM, Ian Campbell wrote: > On Thu, 2015-07-30 at 12:23 +0100, Anthony PERARD wrote: >> On Thu, Jul 30, 2015 at 11:24:47AM +0100, Ian Campbell wrote: >> > On Thu, 2015-07-30 at 14:51 +0800, Ting-Wei Lan wrote: >> > > When --with-system-qemu is used, it is possible that w

Re: [Xen-devel] [PATCH for-4.6] xl/libxl: disable PV vNUMA

On Thu, Jul 30, 2015 at 05:30:58PM +0200, Roger Pau Monné wrote: > El 30/07/15 a les 17.12, Wei Liu ha escrit: > > Update xl manual and disable PV vNUMA in libxl. > > > > Signed-off-by: Wei Liu > > --- > > Cc: Ian Campbell > > Cc: Ian Jackson > > Cc: Dario Faggioli > > --- > > docs/man/xl.cfg

Re: [Xen-devel] 4.6 release bug lists

On Thu, Jul 30, 2015 at 05:10:10PM +0200, Roger Pau Monné wrote: > El 30/07/15 a les 17.04, Wei Liu ha escrit: > > Hi all > > > > Here are some bugs that I'm aware of. The name after a item is the > > person who is working on it. > > > > # Blockers > > > > 1. Toolstack record breaks migration v2

Re: [Xen-devel] [PATCH v5 0/4] x86: modify_ldt improvement, test, and config option

On 07/28/2015 01:29 AM, Andy Lutomirski wrote: This is intended for x86/urgent. Sorry for taking so long, but it seemed nice to avoid breaking Xen. This fixes the "dazed and confused" issue which was exposed by the CVE-2015-5157 fix. It's also probably a good general attack surface reduction,

Re: [Xen-devel] [PATCH for-4.6] xl/libxl: disable PV vNUMA

On 30/07/15 16:45, Wei Liu wrote: > On Thu, Jul 30, 2015 at 05:30:58PM +0200, Roger Pau Monné wrote: >> El 30/07/15 a les 17.12, Wei Liu ha escrit: >>> Update xl manual and disable PV vNUMA in libxl. >>> >>> Signed-off-by: Wei Liu >>> --- >>> Cc: Ian Campbell >>> Cc: Ian Jackson >>> Cc: Dario Fa

[Xen-devel] [linux-3.4 test] 60108: regressions - FAIL

flight 60108 linux-3.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/60108/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-win7-amd64 6 xen-boot fail REGR. vs. 30511 Tests which are failing

Re: [Xen-devel] [PATCH v5 0/4] x86: modify_ldt improvement, test, and config option

On Thu, Jul 30, 2015 at 11:53:34AM -0400, Boris Ostrovsky wrote: > As far as Xen guests are concerned, > > Tested-by: Boris Ostrovsky Does that mean, this patch 1/4 fixes the 32bit issue you guys are still debugging on the v4 thread? Or does that need more fixing? -- Regards/Gruss, Boris.

[Xen-devel] [PATCH for-4.6 v2] xl/libxl: disable PV vNUMA

Update xl manual and disable PV vNUMA in libxl. Signed-off-by: Wei Liu --- Cc: Ian Campbell Cc: Ian Jackson Cc: Dario Faggioli v2: improve doc and code comment. --- docs/man/xl.cfg.pod.5 | 3 +++ tools/libxl/libxl_create.c | 9 + 2 files changed, 12 insertions(+) diff --git a/d

Re: [Xen-devel] [PATCH v5 0/4] x86: modify_ldt improvement, test, and config option

On 30/07/15 17:05, Borislav Petkov wrote: > On Thu, Jul 30, 2015 at 11:53:34AM -0400, Boris Ostrovsky wrote: >> As far as Xen guests are concerned, >> >> Tested-by: Boris Ostrovsky > Does that mean, this patch 1/4 fixes the 32bit issue you guys are still > debugging on the v4 thread? Or does that

[Xen-devel] [PATCH] x86, amd_ucode: Skip microcode updates for final levels

Some of older[Fam10h] systems require that the microcode versions that it comes up with should not be updated by the microcode driver. Otherwise, system hangs are known to occur. In this patch, we check for those microcode versions and abort the update process if existing microcode level is alread

Re: [Xen-devel] [PATCH v5 0/4] x86: modify_ldt improvement, test, and config option

On 07/30/2015 12:12 PM, Andrew Cooper wrote: On 30/07/15 17:05, Borislav Petkov wrote: On Thu, Jul 30, 2015 at 11:53:34AM -0400, Boris Ostrovsky wrote: As far as Xen guests are concerned, Tested-by: Boris Ostrovsky Does that mean, this patch 1/4 fixes the 32bit issue you guys are still debug

Re: [Xen-devel] [PATCH for-4.6 4/8] docs/libxl: Re-specify XENSTORE_DATA as EMULATOR_XENSTORE_DATA

On 29/07/15 12:28, Ian Jackson wrote: > Andrew Cooper writes ("[PATCH for-4.6 4/8] docs/libxl: Re-specify > XENSTORE_DATA as EMULATOR_XENSTORE_DATA"): >> The legacy "toolstack" record as implemented in libxl turns out not to >> be 32/64bit safe. As migration v2 has not shipped yet, take this >> o

Re: [Xen-devel] [PATCH for-4.6 4/8] docs/libxl: Re-specify XENSTORE_DATA as EMULATOR_XENSTORE_DATA

On 29/07/15 10:35, David Vrabel wrote: > >> +EMULATOR\_XENSTORE\_DATA >> + >> >> -A record containing xenstore key/value pairs of data. >> +A set of xenstore key/value pairs for a specific emulator associated with >> the >> +domain. >> >> 0 1 2 3 4

Re: [Xen-devel] [PATCH] x86, amd_ucode: Skip microcode updates for final levels

On 07/30/2015 12:23 PM, Aravind Gopalakrishnan wrote: Some of older[Fam10h] systems require that the microcode versions that it comes up with should not be updated by the microcode driver. Otherwise, system hangs are known to occur. In this patch, we check for those microcode versions and abort

Re: [Xen-devel] [RFC PATCH v3.1 1/2] xsplice: rfc.v3.1

Thanks for the work on this. I had some comments and questions on the latest draft. On Mon, Jul 27, 2015, Konrad Rzeszutek Wilk wrote: > +#define XSPLICE_HOWTO_FLAG_PC_REL0x1 /* Is PC relative. */ > +#define XSPLICE_HOWOT_FLAG_SIGN 0x2 /* Should the new value be treated > as signed va

Re: [Xen-devel] [PATCH] x86, amd_ucode: Skip microcode updates for final levels

On 30/07/15 17:23, Aravind Gopalakrishnan wrote: > Some of older[Fam10h] systems require that the microcode versions > that it comes up with should not be updated by the microcode driver. > Otherwise, system hangs are known to occur. > > In this patch, we check for those microcode versions and abor

[Xen-devel] [PATCHv3 05/10] xen/balloon: rationalize memory hotplug stats

The stats used for memory hotplug make no sense and are fiddled with in odd ways. Remove them and introduce total_pages to track the total number of pages (both populated and unpopulated) including those within hotplugged regions (note that this includes not yet onlined pages). This will be used

[Xen-devel] [PATCHv3 02/10] xen/balloon: remove scratch page left overs

Commit 0bb599fd30108883b00c7d4a226eeb49111e6932 (xen: remove scratch frames for ballooned pages and m2p override) removed the use of the scratch page for ballooned out pages. Remove some left over function definitions. Signed-off-by: David Vrabel Reviewed-by: Daniel Kiper --- include/xen/ballo

[Xen-devel] [PATCHv3 08/10] xen/balloon: use hotplugged pages for foreign mappings etc.

alloc_xenballooned_pages() is used to get ballooned pages to back foreign mappings etc. Instead of having to balloon out real pages, use (if supported) hotplugged memory. This makes more memory available to the guest and reduces fragmentation in the p2m. This is only enabled if the xen.balloon.h

[Xen-devel] [PATCHv3 06/10] xen/balloon: only hotplug additional memory if required

Now that we track the total number of pages (included hotplugged regions), it is easy to determine if more memory needs to be hotplugged. Add a new BP_WAIT state to signal that the balloon process needs to wait until kicked by the memory add notifier (when the new section is onlined by userspace).

[Xen-devel] [PATCHv3 09/10] x86/xen: export xen_alloc_p2m_entry()

Rename alloc_p2m() to xen_alloc_p2m_entry() and export it. This is useful for ensuring that a p2m entry is allocated (i.e., not a shared missing or identity entry) so that subsequent set_phys_to_machine() calls will require no further allocations. Signed-off-by: David Vrabel --- v3: - Make xen_a

[Xen-devel] [PATCHv3 01/10] mm: memory hotplug with an existing resource

Add add_memory_resource() to add memory using an existing "System RAM" resource. This is useful if the memory region is being located by finding a free resource slot with allocate_resource(). Xen guests will make use of this in their balloon driver to hotplug arbitrary amounts of memory in respon

[Xen-devel] [PATCHv3 00/10] mm, xen/balloon: memory hotplug improvements

The series improves the use of hotplug memory in the Xen balloon driver. - Reliably find a non-conflicting location for the hotplugged memory (this fixes memory hotplug in a number of cases, particularly in dom0). - Use hotplugged memory for alloc_xenballooned_pages() (keeping more memory a

[Xen-devel] [PATCHv3 07/10] xen/balloon: make alloc_xenballoon_pages() always allocate low pages

All users of alloc_xenballoon_pages() wanted low memory pages, so remove the option for high memory. Signed-off-by: David Vrabel Reviewed-by: Daniel Kiper --- arch/x86/xen/grant-table.c | 2 +- drivers/xen/balloon.c | 21 - drivers/xen/grant-table.c

[Xen-devel] [PATCHv3 03/10] x86/xen: discard RAM regions above the maximum reservation

During setup, discard RAM regions that are above the maximum reservation (instead of marking them as E820_UNUSABLE). This allows hotplug memory to be placed at these addresses. Signed-off-by: David Vrabel Reviewed-by: Daniel Kiper --- arch/x86/xen/setup.c | 6 -- 1 file changed, 4 insertio

[Xen-devel] [PATCHv3 04/10] xen/balloon: find non-conflicting regions to place hotplugged memory

Instead of placing hotplugged memory at the end of RAM (which may conflict with PCI devices or reserved regions) use allocate_resource() to get a new, suitably aligned resource that does not conflict. Signed-off-by: David Vrabel Reviewed-by: Daniel Kiper --- v3: - Remove stale comment. --- driv

Re: [Xen-devel] [PATCH v5 12/22] xen/arm: ITS: Add GICR register emulation

Hi Vijay, On 27/07/15 12:11, vijay.kil...@gmail.com wrote: > diff --git a/xen/arch/arm/gic-v3.c b/xen/arch/arm/gic-v3.c [..] > +static int gicv3_dist_supports_lpis(void) > +{ > +return readl_relaxed(GICD + GICD_TYPER) & GICD_TYPER_LPIS_SUPPORTED; > +} > + > static int __cpuinit gicv3_cpu_in

Re: [Xen-devel] [PATCH v5 0/4] x86: modify_ldt improvement, test, and config option

On 30/07/15 17:31, Boris Ostrovsky wrote: > On 07/30/2015 12:12 PM, Andrew Cooper wrote: >> On 30/07/15 17:05, Borislav Petkov wrote: >>> On Thu, Jul 30, 2015 at 11:53:34AM -0400, Boris Ostrovsky wrote: As far as Xen guests are concerned, Tested-by: Boris Ostrovsky >>> Does that mea

Re: [Xen-devel] [PATCH v5 13/22] xen/arm: ITS: Implement gic_is_lpi helper function

Hi Vijay, On 27/07/15 12:11, vijay.kil...@gmail.com wrote: > diff --git a/xen/include/asm-arm/gic.h b/xen/include/asm-arm/gic.h > index a9a5874..f80f291 100644 > --- a/xen/include/asm-arm/gic.h > +++ b/xen/include/asm-arm/gic.h > @@ -359,12 +359,14 @@ struct gic_hw_operations { > int (*second

[Xen-devel] [PATCHv3 10/10] xen/balloon: pre-allocate p2m entries for ballooned pages

Pages returned by alloc_xenballooned_pages() will be used for grant mapping which will call set_phys_to_machine() (in PV guests). Ballooned pages are set as INVALID_P2M_ENTRY in the p2m and thus may be using the (shared) missing tables and a subsequent set_phys_to_machine() will need to allocate n

Re: [Xen-devel] [PATCH v5 0/4] x86: modify_ldt improvement, test, and config option

On 07/30/2015 01:06 PM, Andrew Cooper wrote: On 30/07/15 17:31, Boris Ostrovsky wrote: On 07/30/2015 12:12 PM, Andrew Cooper wrote: On 30/07/15 17:05, Borislav Petkov wrote: On Thu, Jul 30, 2015 at 11:53:34AM -0400, Boris Ostrovsky wrote: As far as Xen guests are concerned, Tested-by: Boris

Re: [Xen-devel] [PATCH for-4.6 5/8] tools/libxl: Save and restore EMULATOR_XENSTORE_DATA content

On 29/07/15 12:49, Ian Jackson wrote: > Andrew Cooper writes ("[PATCH for-4.6 5/8] tools/libxl: Save and restore > EMULATOR_XENSTORE_DATA content"): >> The new EMULATOR_XENSTORE_DATA content is a sequence of NUL terminated >> key/value strings, with the key relative to the device model's xenstore

  1   2   >