[Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

Hi, I have a strange problem - xc_evtchn_status fails when running in HVM, while exactly the same code (same kernel, same application etc) works fine in PV. I've narrowed it down to copy_from_guest call in common/event_channel.c, but no idea why it fails there. Xen version is 4.8.0. kernel is

Re: [Xen-devel] [PATCH 3/8] x86emul: support BMI1 insns

On 13/01/17 15:31, Jan Beulich wrote: > --- a/xen/arch/x86/x86_emulate/x86_emulate.c > +++ b/xen/arch/x86/x86_emulate/x86_emulate.c > @@ -676,6 +676,16 @@ do{ asm volatile ( > #define __emulate_1op_8byte(_op, _dst, _eflags) > #endif /* __i386__ */ > > +#define emulate_stub(dst, src...) do {

Re: [Xen-devel] [PATCH 6/8] x86emul: support RDRAND/RDSEED

On 13/01/17 15:34, Jan Beulich wrote: > @@ -5737,14 +5739,82 @@ x86_emulate( > dst.val = src.val; > break; > > -case X86EMUL_OPC(0x0f, 0xc7): /* Grp9 (cmpxchg8b/cmpxchg16b) */ { > +case X86EMUL_OPC(0x0f, 0xc7): /* Grp9 */ { Style (while you are changing this).

[Xen-devel] [PATCH 3/4] efi: create new early memory allocator

From: Daniel Kiper There is a problem with place_string() which is used as early memory allocator. It gets memory chunks starting from start symbol and goes down. Sadly this does not work when Xen is loaded using multiboot2 protocol because then the start lives on 1 MiB

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On 13/01/17 18:59, Marek Marczykowski-Górecki wrote: > On Fri, Jan 13, 2017 at 06:37:06PM +, Andrew Cooper wrote: >> On 13/01/17 18:32, Marek Marczykowski-Górecki wrote: >>> On Fri, Jan 13, 2017 at 06:15:35PM +, Andrew Cooper wrote: Can you get the result of this piece of debugging in

Re: [Xen-devel] [OSSTEST PATCH v9 3/3] Create a flight to test OpenStack with xen-unstable and libvirt

Ian Jackson writes ("Re: [OSSTEST PATCH v9 3/3] Create a flight to test OpenStack with xen-unstable and libvirt"): > Can you provide this series to me as a git branch (catch me on irc > with the url perhaps) ? I will queue it and feed it to the osstest > self-push-gate at an opportune moment.

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On Fri, Jan 13, 2017 at 07:54:01PM +, Andrew Cooper wrote: > On 13/01/17 19:40, Marek Marczykowski-Górecki wrote: > > On Fri, Jan 13, 2017 at 07:27:20PM +, Andrew Cooper wrote: > >> On 13/01/17 18:59, Marek Marczykowski-Górecki wrote: > >>> On Fri, Jan 13, 2017 at 06:37:06PM +, Andrew

Re: [Xen-devel] PVH CPU hotplug design document

On Fri, 13 Jan 2017, Jan Beulich wrote: > >>> On 12.01.17 at 13:13, wrote: > > # Introduction > > > > One of the design goals of PVH is to be able to remove as much Xen PV > > specific > > code as possible, thus limiting the number of Xen PV interfaces used by > > guests,

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On 13/01/17 19:40, Marek Marczykowski-Górecki wrote: > On Fri, Jan 13, 2017 at 07:27:20PM +, Andrew Cooper wrote: >> On 13/01/17 18:59, Marek Marczykowski-Górecki wrote: >>> On Fri, Jan 13, 2017 at 06:37:06PM +, Andrew Cooper wrote: On 13/01/17 18:32, Marek Marczykowski-Górecki wrote:

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On 01/13/2017 01:44 PM, Stefano Stabellini wrote: > On Fri, 13 Jan 2017, Dan Streetman wrote: >> On Wed, Jan 11, 2017 at 6:25 PM, Dan Streetman wrote: >>> On Wed, Jan 11, 2017 at 1:46 PM, Stefano Stabellini >>> wrote: On Wed, 11 Jan 2017, Dan

Re: [Xen-devel] STAO spec in xen.git

On 01/13/2017 12:52 PM, Stefano Stabellini wrote: > On Fri, 13 Jan 2017, Ian Jackson wrote: >> Stefano Stabellini writes ("STAO spec in xen.git"): >>> I suggest we commit the STAO spec in the form of the attached ODT >>> document to xen.git under docs/misc, for easier editing and consumption >>>

Re: [Xen-devel] STAO spec in xen.git

On Fri, 13 Jan 2017, Al Stone wrote: > On 01/13/2017 12:52 PM, Stefano Stabellini wrote: > > On Fri, 13 Jan 2017, Ian Jackson wrote: > >> Stefano Stabellini writes ("STAO spec in xen.git"): > >>> I suggest we commit the STAO spec in the form of the attached ODT > >>> document to xen.git under

Re: [Xen-devel] [RFC PATCH 08/24] ARM: GICv3: introduce separate pending_irq structs for LPIs

On Thu, 12 Jan 2017, Andre Przywara wrote: > Hi Stefano, > > as just mentioned in my last reply, I missed that email last time. Sorry > for that. > > Replying to the comments that still apply to the new drop ... > > On 28/10/16 02:04, Stefano Stabellini wrote: > > On Wed, 28 Sep 2016, Andre

Re: [Xen-devel] STAO spec in xen.git

Hi, Sorry for the top postimg and formatting. I am sending this e-mail from my phone. We already had this discussion a couple of months ago (see [1]). We agreed on an URL but the pdfs were not uploaded. Regarding the format. Does ODT will allow git to do proper diff? If not I would prefer the

Re: [Xen-devel] [PATCH v2] x86emul: suppress memory writes after faulting FPU insns

On 13/01/17 14:32, Jan Beulich wrote: > FPU insns writing to memory must not touch memory if they latch #MF (to > be delivered on the next waiting FPU insn). Note that inspecting FSW.ES > needs to be avoided for all FNST* insns, as they don't raise exceptions > themselves, but may instead be

Re: [Xen-devel] STAO spec in xen.git

Hi Julien, I tried markdown, but there are too many tables, they all get garbled. git diff would only show binary diffs, but libreoffice can show changes. Cheers, Stefano On Fri, 13 Jan 2017, Julien Grall wrote: > Hi, > > Sorry for the top postimg and formatting. I am sending this e-mail from

[Xen-devel] [PATCH 4/4] x86: add multiboot2 protocol support for EFI platforms

From: Daniel Kiper This way Xen can be loaded on EFI platforms using GRUB2 and other boot loaders which support multiboot2 protocol. Signed-off-by: Daniel Kiper Signed-off-by: Doug Goldstein Reviewed-by: Doug Goldstein

[Xen-devel] [PATCH 1/4] x86: add multiboot2 protocol support

From: Daniel Kiper Add multiboot2 protocol support. Alter min memory limit handling as we now may not find it from either multiboot (v1) or multiboot2. This way we are laying the foundation for EFI + GRUB2 + Xen development. Signed-off-by: Daniel Kiper

Re: [Xen-devel] [RFC PATCH v2 06/26] ARM: GICv3 ITS: introduce device mapping

On Fri, 13 Jan 2017, Andre Przywara wrote: > Hi Stefano, > > On 05/01/17 00:13, Stefano Stabellini wrote: > > On Thu, 22 Dec 2016, Andre Przywara wrote: > >> The ITS uses device IDs to map LPIs to a device. Dom0 will later use > >> those IDs, which we directly pass on to the host. > >> For this

[Xen-devel] [PATCH 0/4] multiboot2 protocol support

This is a series based on v11 of Daniel Kiper's "x86: multiboot2 protocol support" series. It aims to collect up all the fixes and changes that Andrew Cooper, Jan Beulich and myself discovered in code review and testing on actual hardware. I've had problems with the relocation portion of the

[Xen-devel] [PATCH 2/4] efi: build xen.gz with EFI code

From: Daniel Kiper Build xen.gz with EFI code. We need this to support multiboot2 protocol on EFI platforms. If we wish to load non-ELF file using multiboot (v1) or multiboot2 then it must contain "linear" (or "flat") representation of code and data. This is requirement

Re: [Xen-devel] STAO spec in xen.git

Stefano Stabellini writes ("STAO spec in xen.git"): > I suggest we commit the STAO spec in the form of the attached ODT > document to xen.git under docs/misc, for easier editing and consumption > by the Xen community, and to be able to generate a stable URL for it. In > fact at the moment the link

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

This run is configured for baseline tests only. flight 68357 xen-unstable real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68357/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-xtf-amd64-amd64-33

[Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

Revert the main part of commit: af42b8d12f8a ("xen: fix MSI setup and teardown for PV on HVM guests") That commit introduced reading the pci device's msi message data to see if a pirq was previously configured for the device's msi/msix, and re-use that pirq. At the time, that was the correct

Re: [Xen-devel] STAO spec in xen.git

On Fri, 13 Jan 2017, Ian Jackson wrote: > Stefano Stabellini writes ("STAO spec in xen.git"): > > I suggest we commit the STAO spec in the form of the attached ODT > > document to xen.git under docs/misc, for easier editing and consumption > > by the Xen community, and to be able to generate a

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On Fri, 13 Jan 2017, Dan Streetman wrote: > Revert the main part of commit: > af42b8d12f8a ("xen: fix MSI setup and teardown for PV on HVM guests") > > That commit introduced reading the pci device's msi message data to see > if a pirq was previously configured for the device's msi/msix, and

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On Fri, Jan 13, 2017 at 07:27:20PM +, Andrew Cooper wrote: > On 13/01/17 18:59, Marek Marczykowski-Górecki wrote: > > On Fri, Jan 13, 2017 at 06:37:06PM +, Andrew Cooper wrote: > >> On 13/01/17 18:32, Marek Marczykowski-Górecki wrote: > >>> On Fri, Jan 13, 2017 at 06:15:35PM +, Andrew

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On Fri, Jan 13, 2017 at 3:00 PM, Boris Ostrovsky wrote: > On 01/13/2017 01:44 PM, Stefano Stabellini wrote: >> On Fri, 13 Jan 2017, Dan Streetman wrote: >>> On Wed, Jan 11, 2017 at 6:25 PM, Dan Streetman wrote: On Wed, Jan 11, 2017 at 1:46 PM,

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On 01/13/2017 03:07 PM, Dan Streetman wrote: > Revert the main part of commit: > af42b8d12f8a ("xen: fix MSI setup and teardown for PV on HVM guests") > > That commit introduced reading the pci device's msi message data to see > if a pirq was previously configured for the device's msi/msix, and

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On Fri, Jan 13, 2017 at 05:38:42PM +, Andrew Cooper wrote: > On 13/01/17 17:31, Marek Marczykowski-Górecki wrote: > > Hi, > > > > I have a strange problem - xc_evtchn_status fails when running in HVM, > > while exactly the same code (same kernel, same application etc) works > > fine in PV.

[Xen-devel] STAO spec in xen.git

Hi all, I suggest we commit the STAO spec in the form of the attached ODT document to xen.git under docs/misc, for easier editing and consumption by the Xen community, and to be able to generate a stable URL for it. In fact at the moment the link to the STAO spec from http://uefi.org/acpi is

[Xen-devel] XENV table in xen.git

Hi all, Similarly to STAO (http://marc.info/?l=xen-devel=148433427425627), I suggest we also commit the XENV spec in the form of the attached ODT document to xen.git under docs/misc. Cheers, Stefano xen-env-table-spec-v0.2.odt Description: application/vnd.oasis.opendocument.text

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On 13/01/17 17:31, Marek Marczykowski-Górecki wrote: > Hi, > > I have a strange problem - xc_evtchn_status fails when running in HVM, > while exactly the same code (same kernel, same application etc) works > fine in PV. I've narrowed it down to copy_from_guest call in > common/event_channel.c, but

Re: [Xen-devel] [PATCH 4/8] x86emul: support BMI2 insns

On 13/01/17 15:32, Jan Beulich wrote: > Note that the adjustment to the mode_64bit() definition is so that we > can avoid "#ifdef __x86_64__" around the 64-bit asm() portions. An > alternative would be single asm()s with a conditional branch over the > (manually encoded) REX64 prefix. This

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On Fri, 13 Jan 2017, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 6:25 PM, Dan Streetman wrote: > > On Wed, Jan 11, 2017 at 1:46 PM, Stefano Stabellini > > wrote: > >> On Wed, 11 Jan 2017, Dan Streetman wrote: > >>> On Tue, Jan 10, 2017 at 8:25 PM,

Re: [Xen-devel] [PATCH 7/8] x86emul: support RDPID

On 13/01/17 15:34, Jan Beulich wrote: > Signed-off-by: Jan Beulich Reviewed-by: Andrew Cooper ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH v3 1/8] arm: put types.h in uapi

On Fri, Jan 13, 2017 at 11:46:39AM +0100, Nicolas Dichtel wrote: > This header file is exported, thus move it to uapi. I'm taking this patch, but with the following commit log: Due to the way kbuild works, this header was unintentionally exported back in 2013 when it was created, despite it

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On 13/01/17 18:32, Marek Marczykowski-Górecki wrote: > On Fri, Jan 13, 2017 at 06:15:35PM +, Andrew Cooper wrote: >> On 13/01/17 18:03, Marek Marczykowski-Górecki wrote: >>> On Fri, Jan 13, 2017 at 05:38:42PM +, Andrew Cooper wrote: On 13/01/17 17:31, Marek Marczykowski-Górecki wrote:

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On Fri, Jan 13, 2017 at 06:37:06PM +, Andrew Cooper wrote: > On 13/01/17 18:32, Marek Marczykowski-Górecki wrote: > > On Fri, Jan 13, 2017 at 06:15:35PM +, Andrew Cooper wrote: > >> Can you get the result of this piece of debugging in the failure case? > > I've got this: > > ** d4v0

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On Fri, Jan 13, 2017 at 06:15:35PM +, Andrew Cooper wrote: > On 13/01/17 18:03, Marek Marczykowski-Górecki wrote: > > On Fri, Jan 13, 2017 at 05:38:42PM +, Andrew Cooper wrote: > >> On 13/01/17 17:31, Marek Marczykowski-Górecki wrote: > >>> Hi, > >>> > >>> I have a strange problem -

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On 13/01/17 18:03, Marek Marczykowski-Górecki wrote: > On Fri, Jan 13, 2017 at 05:38:42PM +, Andrew Cooper wrote: >> On 13/01/17 17:31, Marek Marczykowski-Górecki wrote: >>> Hi, >>> >>> I have a strange problem - xc_evtchn_status fails when running in HVM, >>> while exactly the same code (same

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On Wed, Jan 11, 2017 at 6:25 PM, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 1:46 PM, Stefano Stabellini > wrote: >> On Wed, 11 Jan 2017, Dan Streetman wrote: >>> On Tue, Jan 10, 2017 at 8:25 PM, Stefano Stabellini >>> wrote:

Re: [Xen-devel] [PATCH 5/8] x86emul: support TBM insns

On 13/01/17 15:32, Jan Beulich wrote: > --- a/xen/arch/x86/x86_emulate/x86_emulate.c > +++ b/xen/arch/x86/x86_emulate/x86_emulate.c > @@ -1355,6 +1355,7 @@ static bool vcpu_has( > #define vcpu_has_cr8_legacy() vcpu_has(0x8001, ECX, 4, ctxt, ops) > #define vcpu_has_lzcnt()

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

flight 104171 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/104171/ 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

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

On Fri, 13 Jan 2017, Pooya.Keshavarzi wrote: > On 01/12/2017 07:50 PM, Stefano Stabellini wrote: > > On Thu, 12 Jan 2017, Pooya.Keshavarzi wrote: > >> > >> Firstly sorry for the late reply on this. > >> > >> Regarding the problem with swiotlb-xen here are some more details: > >> > >> If we limit

Re: [Xen-devel] [PATCH 8/8] x86emul: rename the no_writeback label

On 13/01/17 15:35, Jan Beulich wrote: > This is to bring its name in line with what actually happens there. > > Suggested-by: Andrew Cooper > Signed-off-by: Jan Beulich Reviewed-by: Andrew Cooper

Re: [Xen-devel] [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On Fri, 13 Jan 2017, Boris Ostrovsky wrote: > On 01/12/2017 04:39 PM, Stefano Stabellini wrote: > > The following commit: > > > > commit 72a9b186292d98494f26cfd24a1621796209 > > Author: KarimAllah Ahmed > > Date: Fri Aug 26 23:55:36 2016 +0200 > > > > xen: Remove

Re: [Xen-devel] [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On 01/13/2017 01:26 PM, Stefano Stabellini wrote: > On Fri, 13 Jan 2017, Boris Ostrovsky wrote: >> On 01/12/2017 04:39 PM, Stefano Stabellini wrote: >>> The following commit: >>> >>> commit 72a9b186292d98494f26cfd24a1621796209 >>> Author: KarimAllah Ahmed >>> Date: Fri

[Xen-devel] [qemu-mainline test] 104169: regressions - FAIL

flight 104169 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/104169/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-arndale 6 xen-boot fail REGR. vs. 104159 Regressions

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On Fri, Jan 13, 2017 at 03:07:51PM -0500, Dan Streetman wrote: > Revert the main part of commit: > af42b8d12f8a ("xen: fix MSI setup and teardown for PV on HVM guests") > > That commit introduced reading the pci device's msi message data to see > if a pirq was previously configured for the

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

flight 104170 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/104170/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-armhf-xl-credit2 6 xen-boot fail in 104162 pass in 104170 test-armhf-armhf-xl-arndale 4

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On 13/01/2017 20:32, Marek Marczykowski-Górecki wrote: > On Fri, Jan 13, 2017 at 07:54:01PM +, Andrew Cooper wrote: >> On 13/01/17 19:40, Marek Marczykowski-Górecki wrote: >>> On Fri, Jan 13, 2017 at 07:27:20PM +, Andrew Cooper wrote: On 13/01/17 18:59, Marek Marczykowski-Górecki

[Xen-devel] [ovmf baseline-only test] 68364: all pass

This run is configured for baseline tests only. flight 68364 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68364/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 521981ee7608b75b51693ea367c9e1d83687d110 baseline

Re: [Xen-devel] PVH CPU hotplug design document

On 01/13/2017 10:51 AM, Jan Beulich wrote: On 12.01.17 at 13:13, wrote: >> # Introduction >> >> One of the design goals of PVH is to be able to remove as much Xen PV >> specific >> code as possible, thus limiting the number of Xen PV interfaces used by >> guests, >>

Re: [Xen-devel] Xen 4.8 + Linux 4.9 + Credit2 = can't bootup

On 01/13/2017 11:27 AM, Ian Jackson wrote: > > osstest's reports are posted to xen-devel. To give you an example of > what they look like, I have pasted below the top of the report from > last test report of linux-linus (including interesting mail headers). > > If you find the mail filtering of

Re: [Xen-devel] [PATCH v11 00/13] x86: multiboot2 protocol support

On Fri, Jan 13, 2017 at 09:45:13AM -0600, Doug Goldstein wrote: > On 1/11/17 2:46 PM, Daniel Kiper wrote: > > On Mon, Dec 05, 2016 at 11:25:05PM +0100, Daniel Kiper wrote: > >> Hi, > >> > >> I am sending eleventh version of multiboot2 protocol support for > >> legacy BIOS and EFI platforms. This

Re: [Xen-devel] [PATCH v3 1/8] arm: put types.h in uapi

On Fri, Jan 13, 2017 at 05:01:01PM +0100, Nicolas Dichtel wrote: > Please, do not remove the email subject when you reply. I restore it to > ease the thread follow-up. I mentioned it to David, and he says it's because the long list of recipients is breaking his mailer. I've already posed the

Re: [Xen-devel] Xen 4.8 + Linux 4.9 + Credit2 = can't bootup

Boris Ostrovsky writes ("Re: [Xen-devel] Xen 4.8 + Linux 4.9 + Credit2 = can't bootup"): > I can give it a try although I have practically no experience with > OSSTest. Is there a way to subscribe to notifications for those tests? osstest's reports are posted to xen-devel. To give you an

Re: [Xen-devel] [PATCH 1/8] x86emul: support POPCNT

On 13/01/17 15:30, Jan Beulich wrote: > Signed-off-by: Jan Beulich Reviewed-by: Andrew Cooper ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH 2/8] x86emul: support ADCX/ADOX

On 13/01/17 15:31, Jan Beulich wrote: > Signed-off-by: Jan Beulich Reviewed-by: Andrew Cooper ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH v3 4/8] x86: stop exporting msr-index.h to userland

On Fri, Jan 13, 2017 at 05:08:34PM +0100, Nicolas Dichtel wrote: > Le 13/01/2017 à 16:43, David Howells a écrit : > >> -header-y += msr-index.h > > > > I see it on my desktop as /usr/include/asm/msr-index.h and it's been there > > at > > least four years - and as such it's part of the UAPI. I

[Xen-devel] [xen-unstable test] 104175: regressions - FAIL

flight 104175 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/104175/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl 15 guest-start/debian.repeat fail REGR. vs. 104170 Regressions which

Re: [Xen-devel] xc_evtchn_status fails with EFAULT on HVM, the same on PV works

On Sat, Jan 14, 2017 at 01:47:49AM +, Andrew Cooper wrote: > On 13/01/2017 20:32, Marek Marczykowski-Górecki wrote: > > On Fri, Jan 13, 2017 at 07:54:01PM +, Andrew Cooper wrote: > >> This is a guest kernel bug. The guest kernel has used SMAP to say > >> "please disallow all userspace

[Xen-devel] [qemu-mainline test] 104176: regressions - trouble: broken/fail/pass

flight 104176 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/104176/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-multivcpu 3 host-install(3) broken REGR. vs. 104159

Re: [Xen-devel] [PATCH v2 2/2] x86/cpuid: Move x86_vendor from arch_domain to cpuid_policy

>>> On 13.01.17 at 14:56, wrote: > No functional change. > > Signed-off-by: Andrew Cooper Reviewed-by: Jan Beulich ___ Xen-devel mailing list Xen-devel@lists.xen.org

[Xen-devel] [PATCH v2] x86emul: suppress memory writes after faulting FPU insns

FPU insns writing to memory must not touch memory if they latch #MF (to be delivered on the next waiting FPU insn). Note that inspecting FSW.ES needs to be avoided for all FNST* insns, as they don't raise exceptions themselves, but may instead be invoked with the bit already set. Signed-off-by:

Re: [Xen-devel] [PATCH v2 1/2] x86/cpuid: Drop a guests cached x86 family and model information

>>> On 13.01.17 at 14:56, wrote: > The model information isn't used at all, and the family information is only > used once. > > Make get_cpu_family() a static inline (as it is just basic calculation, and > the function call is probably more expensive than the function

[Xen-devel] [PATCH RESEND] tools/libxl: add support for emulated NVMe drives

Upstream QEMU supports emulation of NVM Express a.k.a. NVMe drives. This patch adds a new vdev type into libxl to allow such drives to be presented to HVM guests. Because the purpose of the new vdev is purely to configure emulation, the syntax only supports specification of whole disks. Also

Re: [Xen-devel] [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On 01/12/2017 04:39 PM, Stefano Stabellini wrote: > The following commit: > > commit 72a9b186292d98494f26cfd24a1621796209 > Author: KarimAllah Ahmed > Date: Fri Aug 26 23:55:36 2016 +0200 > > xen: Remove event channel notification through Xen PCI platform device > >

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

flight 104166 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/104166/ 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

Re: [Xen-devel] Xen 4.8 + Linux 4.9 + Credit2 = can't bootup

On Thu, 2017-01-12 at 11:22 -0500, Boris Ostrovsky wrote: > On 01/12/2017 07:50 AM, Dario Faggioli wrote: > > I don't think we do that any longer, and that may be part of the > > reason > > why we missed this one? > > I believe you needed to be on a multi-socket system to catch this > bug. >

Re: [Xen-devel] [PATCH v3 1/8] public / x86: Introduce __HYPERCALL_dm_op...

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 12 January 2017 16:29 > To: Andrew Cooper ; Paul Durrant > > Cc: Ian Jackson ; Jennifer Herbert > ; Wei Liu

[Xen-devel] [libvirt test] 104158: regressions - FAIL

flight 104158 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/104158/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt-raw 6 xen-boot fail REGR. vs. 104134 Regressions which are

Re: [Xen-devel] Granularity of Credit and RTDS Scheduler

On Sun, 2017-01-08 at 22:06 +, Dario Faggioli wrote: > Il 08 gen 2017 08:31, Meng Xu ha scritto: > [cc. Dario and George] > On Fri, Jan 6, 2017 at 1:34 PM, wy11 wrote: > > Recently I read a paper about possible theft of service attacks in > Xen > >

Re: [Xen-devel] [PATCH v2 5/5] libxl: Add explicit cast to libxl_psr_cat_set_cbm

On Thu, 2017-01-12 at 18:08 +, George Dunlap wrote: > On Tue, Jan 19, 2016 at 2:35 PM, Ian Jackson > wrote: > > > > > On Tue, 2016-01-19 at 14:06 +, Ian Jackson wrote: > > > > > > > >  * XEN_DOMCTL_PSR_CAT_OP_SET_L3_* (public/domctl.h) > > > >  * enum

[Xen-devel] [xen-unstable test] 104157: trouble: blocked/broken/fail/pass

flight 104157 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/104157/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-xsm 3 host-install(3)broken REGR. vs.

Re: [Xen-devel] [PATCH] xen-netback: fix memory leaks on XenBus disconnect

> -Original Message- > From: Igor Druzhinin [mailto:igor.druzhi...@citrix.com] > Sent: 12 January 2017 17:52 > To: Wei Liu ; xen-de...@lists.xenproject.org; Paul > Durrant > Cc: net...@vger.kernel.org; linux-ker...@vger.kernel.org; Igor

[Xen-devel] [PATCH v3 7/8] uapi: export all headers under uapi directories

Regularly, when a new header is created in include/uapi/, the developer forgets to add it in the corresponding Kbuild file. This error is usually detected after the release is out. In fact, all headers under uapi directories should be exported, thus it's useless to have an exhaustive list. After

[Xen-devel] [PATCH v3 3/8] nios2: put setup.h in uapi

This header file is exported, but from a userland pov, it's just a wrapper to asm-generic/setup.h. Signed-off-by: Nicolas Dichtel --- arch/nios2/include/uapi/asm/Kbuild | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/nios2/include/uapi/asm/Kbuild

[Xen-devel] [PATCH v3 0/8] uapi: export all headers under uapi directories

Here is the v3 of this series. The first 5 patches are just cleanup: some exported headers were still under a non-uapi directory or (x86 case) were wrongly exported. The patch 6 was spotted by code review: there is no in-tree user of this functionality. Patches 7 and 8 remove the need to list

[Xen-devel] [PATCH v3 6/8] Makefile.headersinst: remove destination-y option

This option was added in commit c7bb349e7c25 ("kbuild: introduce destination-y for exported headers") but never used in-tree. Signed-off-by: Nicolas Dichtel --- Documentation/kbuild/makefiles.txt | 23 --- scripts/Makefile.headersinst | 2 +-

[Xen-devel] [PATCH v3 1/8] arm: put types.h in uapi

This header file is exported, thus move it to uapi. Signed-off-by: Nicolas Dichtel --- arch/arm/include/asm/types.h | 40 --- arch/arm/include/uapi/asm/types.h | 40 +++ 2 files changed, 40

[Xen-devel] [PATCH v3 2/8] h8300: put bitsperlong.h in uapi

This header file is exported, thus move it to uapi. Signed-off-by: Nicolas Dichtel --- arch/h8300/include/asm/bitsperlong.h | 14 -- arch/h8300/include/uapi/asm/bitsperlong.h | 14 ++ 2 files changed, 14 insertions(+), 14 deletions(-)

[Xen-devel] [PATCH v3 4/8] x86: stop exporting msr-index.h to userland

Suggested-by: Borislav Petkov Signed-off-by: Nicolas Dichtel --- arch/x86/include/uapi/asm/Kbuild | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/x86/include/uapi/asm/Kbuild b/arch/x86/include/uapi/asm/Kbuild index 3dec769cadf7..1c532b3f18ea

[Xen-devel] [PATCH v3 5/8] Makefile.headersinst: cleanup input files

After the last four patches, all exported headers are under uapi/, thus input-files2 are not needed anymore. The side effect is that input-files1-name is exactly header-y. Note also that input-files3-name is genhdr-y. Signed-off-by: Nicolas Dichtel ---

Re: [Xen-devel] [PATCH 2/4] x86/cpuid: Store the toolstacks choice of hypervisor max leaf

On 13/01/17 11:32, Jan Beulich wrote: On 11.01.17 at 18:44, wrote: >> --- a/xen/arch/x86/domctl.c >> +++ b/xen/arch/x86/domctl.c >> @@ -136,6 +136,14 @@ static int update_domain_cpuid_info(struct domain *d, >> p->basic.raw[ctl->input[0]] = leaf; >>

Re: [Xen-devel] [PATCH v3 3/8] dm_op: convert HVMOP_track_dirty_vram

>>> On 12.01.17 at 15:58, wrote: > v3: > - Check d->max_vcpus rather than d->vcpu, as requested by Jan. > - The handle type changes (from uint8 to void) are still necessary, hence > omitting Jan's R-b until this is confirmed to be acceptable. Hmm, talk really was of

Re: [Xen-devel] [PATCH v2] kexec: implement STATUS hypercall to check if image is loaded

>>> On 13.01.17 at 12:40, wrote: > On Fri, Jan 13, 2017 at 04:16:01AM -0700, Jan Beulich wrote: >> >>> On 12.01.17 at 22:59, wrote: >> > CC: Elena Ufimtseva >> > CC: Daniel Kiper >> >> Cc:

Re: [Xen-devel] [PATCH 1/2] tools/xenstore: start with empty data base

On Tue, Jan 10, 2017 at 05:13:38PM +0100, Juergen Gross wrote: > Today xenstored tries to open a tdb data base file on disk when it is > started. As this is problematic in most cases the scripts used to start > xenstored ensure xenstored won't find such a file in order to start > with an empty

Re: [Xen-devel] [PATCH] xen-netback: fix memory leaks on XenBus disconnect

> -Original Message- > From: Wei Liu [mailto:wei.l...@citrix.com] > Sent: 13 January 2017 10:38 > To: Igor Druzhinin > Cc: Wei Liu ; xen-de...@lists.xenproject.org; Paul > Durrant ; net...@vger.kernel.org; linux- >

Re: [Xen-devel] [PATCH v2] kexec: implement STATUS hypercall to check if image is loaded

>>> On 12.01.17 at 22:59, wrote: > CC: Elena Ufimtseva > CC: Daniel Kiper Cc: Andrew Cooper (as the kexec maintainer) > Note: The __XEN_LATEST_INTERFACE_VERSION__ has been bumped to >

Re: [Xen-devel] [PATCH v2] kexec: implement STATUS hypercall to check if image is loaded

On Fri, Jan 13, 2017 at 04:16:01AM -0700, Jan Beulich wrote: > >>> On 12.01.17 at 22:59, wrote: > > CC: Elena Ufimtseva > > CC: Daniel Kiper > > Cc: Andrew Cooper > (as the kexec

Re: [Xen-devel] [PATCH 2/4] x86/cpuid: Store the toolstacks choice of hypervisor max leaf

>>> On 13.01.17 at 12:45, wrote: > On 13/01/17 11:32, Jan Beulich wrote: > On 11.01.17 at 18:44, wrote: >>> --- a/xen/arch/x86/domctl.c >>> +++ b/xen/arch/x86/domctl.c >>> @@ -136,6 +136,14 @@ static int update_domain_cpuid_info(struct

Re: [Xen-devel] [PATCH] xen-netback: fix memory leaks on XenBus disconnect

On Thu, Jan 12, 2017 at 05:51:56PM +, Igor Druzhinin wrote: > Eliminate memory leaks introduced several years ago by cleaning the queue > resources which are allocated on XenBus connection event. Namely, queue > structure array and pages used for IO rings. > vif->lock is used to protect

Re: [Xen-devel] [PATCH v3 1/8] public / x86: Introduce __HYPERCALL_dm_op...

On Fri, Jan 13, 2017 at 09:05:19AM +, Paul Durrant wrote: > > -Original Message- > > From: Jan Beulich [mailto:jbeul...@suse.com] > > Sent: 12 January 2017 16:29 > > To: Andrew Cooper ; Paul Durrant > > > > Cc: Ian Jackson

Re: [Xen-devel] [PATCH] x86/cpuid: Fix feature flags reported to dom0

>>> On 12.01.17 at 20:55, wrote: > c/s a11e8c9 "x86/pv: Use per-domain policy information in pv_cpuid()" switched > PV domains from using a (hardware for dom0, toolstack-chosen from domU) value > masked against pv_featureset[], to actually using the value calculated by

Re: [Xen-devel] [PATCH 2/4] x86/cpuid: Store the toolstacks choice of hypervisor max leaf

>>> On 11.01.17 at 18:44, wrote: > --- a/xen/arch/x86/domctl.c > +++ b/xen/arch/x86/domctl.c > @@ -136,6 +136,14 @@ static int update_domain_cpuid_info(struct domain *d, > p->basic.raw[ctl->input[0]] = leaf; > break; > > +case 0x4000: > +

Re: [Xen-devel] [PATCH v3 1/8] public / x86: Introduce __HYPERCALL_dm_op...

>>> On 13.01.17 at 10:05, wrote: >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: 12 January 2017 16:29 >> >>> On 12.01.17 at 17:10, wrote: >> >> The userspace side should be >> >> >> >> struct xen_dm_op_buf { >> >> void *h; >> >>

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

Dear Pooya, On our site we did not face those issues 'cause we limited dom0 memory space to the 32-bit addressable range. BTW, it looks you use nfs root in you setups, do you? Issues we faced and got fixes/workarounds was as following: MMC driver did not work due to dma_mmap fixed with the

Re: [Xen-devel] [PATCH v3 3/8] dm_op: convert HVMOP_track_dirty_vram

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 13 January 2017 11:45 > To: Paul Durrant > Cc: Andrew Cooper ; George Dunlap > ; Ian Jackson ; xen- >

  1   2   >