Re: [Xen-devel] [PATCH 4/5] x86/pv: Drop support for paging out the LDT

>>> On 12.01.18 at 19:37, wrote: > Windows is the only OS which pages out kernel datastructures, so chances are > good that this is a vestigial remnant of the PV Windows XP experiment. This is based on what? How do you know there are no other OSes doing so, including

Re: [Xen-devel] [PATCH v4] kexec-tools: Perform run-time linking of libxenctrl.so

On Wed, Jan 17, 2018 at 10:39:01AM -0600, Eric DeVolder wrote: > When kexec is utilized in a Xen environment, it has an explicit > run-time dependency on libxenctrl.so. This dependency occurs > during the configure stage and when building kexec-tools. ... Thanks for addressing this and thanks

Re: [Xen-devel] Access I2C bus from guest/DomU on ARM board

On Wed, Jan 17, 2018 at 9:06 PM, Andrii Anisov wrote: > Rajesh, > > On 17.01.18 16:03, Saumya Rajesh wrote: > >> Just out of curiosity, is it possible to split the Driver for the Renesas >> RCar I2C unit [1] into frontend and backend to use the i2c bus from guest? >> Or

Re: [Xen-devel] [PATCH 1/5] x86/idt: Factor out enabling and disabling of ISTs

>>> On 17.01.18 at 15:43, wrote: > On Fri, Jan 12, 2018 at 06:37:20PM +, Andrew Cooper wrote: >> All alteration of IST settings (other than the crash path) happen in an >> identical triple. Introduce helpers to keep the triple in sync, and reduce >> the risk of opencoded

[Xen-devel] [linux-4.9 test] 118151: trouble: broken/fail/pass

flight 118151 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/118151/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-rtds broken Regressions which are

[Xen-devel] [xen-unstable-smoke test] 118199: regressions - FAIL

flight 118199 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118199/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 6 xen-buildfail REGR. vs. 118105 Tests which

[Xen-devel] [xen-unstable-smoke test] 118197: regressions - FAIL

flight 118197 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118197/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 6 xen-buildfail REGR. vs. 118105 Tests which

[Xen-devel] [PULL 06/19] machine: Replace has_dynamic_sysbus with list of allowed devices

The existing has_dynamic_sysbus flag makes the machine accept every user-creatable sysbus device type on the command-line. Replace it with a list of allowed device types, so machines can easily accept some sysbus devices while rejecting others. To keep exactly the same behavior as before, the

[Xen-devel] [PULL 10/19] xen: Add only xen-sysdev to dynamic sysbus device list

There's no need to make the machine allow every possible sysbus device. We can now just add xen-sysdev to the allowed list. Cc: Stefano Stabellini Cc: Anthony Perard Cc: xen-devel@lists.xenproject.org Cc: Juergen Gross

[Xen-devel] [xen-unstable-smoke test] 118187: regressions - FAIL

flight 118187 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118187/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 6 xen-buildfail REGR. vs. 118105 Tests which

Re: [Xen-devel] [PATCH 1/5] xen/arm: Introduce enable callback to enable a capabilities on each online CPU

On Wed, 17 Jan 2018, Stefano Stabellini wrote: > On Wed, 17 Jan 2018, Lars Kurth wrote: > > Regarding README.source, this is covering file and contain the same > > mention as in the commit message. As this is a single function. Isn't the > > commit message > > enough? > > > > > >

[Xen-devel] [xen-unstable-smoke test] 118178: regressions - FAIL

flight 118178 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118178/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 6 xen-buildfail REGR. vs. 118105 Tests which

[Xen-devel] [linux-3.18 test] 118149: regressions - FAIL

flight 118149 linux-3.18 real [real] http://logs.test-lab.xenproject.org/osstest/logs/118149/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-examine 6 xen-install fail REGR. vs. 117702 Tests which did not

[Xen-devel] [xen-unstable-smoke test] 118173: regressions - FAIL

flight 118173 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118173/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 6 xen-buildfail REGR. vs. 118105 Tests which

Re: [Xen-devel] [PATCH 4/5] xen/arm64: Add skeleton to harden the branch predictor aliasing attacks

On Tue, 16 Jan 2018, Julien Grall wrote: > Aliasing attacked against CPU branch predictors can allow an attacker to > redirect speculative control flow on some CPUs and potentially divulge > information from one context to another. > > This patch adds initial skeleton code behind a new Kconfig

Re: [Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

On 17/01/18 17:32, Roger Pau Monné wrote: > On Wed, Jan 17, 2018 at 04:24:27PM +, Ian Jackson wrote: >> Roger Pau Monne writes ("[PATCH 6/6] firmware/shim: fix build process to use >> POSIX find options"): >>> The -printf find option is not POSIX compatible, so replace it with >>> another

[Xen-devel] [seabios test] 118140: regressions - FAIL

flight 118140 seabios real [real] http://logs.test-lab.xenproject.org/osstest/logs/118140/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 115539 Tests which did not

Re: [Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

On Wed, Jan 17, 2018 at 04:24:27PM +, Ian Jackson wrote: > Roger Pau Monne writes ("[PATCH 6/6] firmware/shim: fix build process to use > POSIX find options"): > > The -printf find option is not POSIX compatible, so replace it with > > another rune. > ... > > cd $(D)/$(d); \ > >

Re: [Xen-devel] [PATCH v8 15/17] x86/ctxt: Issue a speculation barrier between vcpu contexts

On Mon, 2018-01-15 at 22:39 +0100, David Woodhouse wrote: > On Mon, 2018-01-15 at 14:23 +0100, David Woodhouse wrote: > > > > > > > > > > > > > > >   > > > > Also... if you're doing that in context_switch() does it do the right > > > > thing with idle? If a CPU switches to the idle domain and

[Xen-devel] Xen Security Advisory 254 (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754) - Information leak via side effects of speculative execution

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Xen Security Advisory CVE-2017-5753,CVE-2017-5715,CVE-2017-5754 / XSA-254 version 9 Information leak via side effects of speculative execution UPDATES IN VERSION 9 "Stage 1" pagetable

Re: [Xen-devel] [PATCH 5/5] xen/arm64: Implement branch predictor hardening for affected Cortex-A CPUs

On Wed, 17 Jan 2018, Julien Grall wrote: > Hi Stefano, > > On 17/01/18 00:42, Stefano Stabellini wrote: > > On Tue, 16 Jan 2018, Julien Grall wrote: > > > #define MIDR_RANGE(model, min, max) \ > > > @@ -205,6 +232,28 @@ static const struct arm_cpu_capabilities arm_errata[] > > > = { > > >

Re: [Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

Wei Liu writes ("Re: [PATCH 6/6] firmware/shim: fix build process to use POSIX find options"): > On Wed, Jan 17, 2018 at 04:55:01PM +, Ian Jackson wrote: > > FYI I am going to ship the patch as is to "comet" users via an XSA-254 > > update. I'm just quibbling about this for #staging. > >

Re: [Xen-devel] [PATCH] ocaml: fix arm build

CC Ocaml experts On Wed, Jan 17, 2018 at 04:43:54PM +, Wei Liu wrote: > ARM doesn't have emulation_flags in the arch_domainconfig. > > Signed-off-by: Wei Liu > --- > Cc: Ian Jackson > Cc: Julien Grall > Cc: Andrew

Re: [Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

On Wed, Jan 17, 2018 at 04:55:01PM +, Ian Jackson wrote: > Wei Liu writes ("Re: [PATCH 6/6] firmware/shim: fix build process to use > POSIX find options"): > > On Wed, Jan 17, 2018 at 04:24:27PM +, Ian Jackson wrote: > > > And finally, I don't really understand why it is necessary to

Re: [Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

Wei Liu writes ("Re: [PATCH 6/6] firmware/shim: fix build process to use POSIX find options"): > On Wed, Jan 17, 2018 at 04:24:27PM +, Ian Jackson wrote: > > And finally, I don't really understand why it is necessary to strip > > $(XEN_ROOT)/$(d)/ out at all. > > We want the path without

Re: [Xen-devel] [PATCH] ocaml: fix arm build

Hi Wei, On 17/01/18 16:43, Wei Liu wrote: ARM doesn't have emulation_flags in the arch_domainconfig. Signed-off-by: Wei Liu Reviewed-by: Julien Grall Cheers, --- Cc: Ian Jackson Cc: Julien Grall

[Xen-devel] [xen-unstable-smoke test] 118162: regressions - FAIL

flight 118162 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118162/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 6 xen-buildfail REGR. vs. 118105 Tests which

[Xen-devel] [PATCH v4] kexec-tools: Perform run-time linking of libxenctrl.so

When kexec is utilized in a Xen environment, it has an explicit run-time dependency on libxenctrl.so. This dependency occurs during the configure stage and when building kexec-tools. When kexec is utilized in a non-Xen environment (either bare metal or KVM), the configure and build of kexec-tools

Re: [Xen-devel] [PATCH v3] kexec-tools: Perform run-time linking of libxenctrl.so

Responses are inlined below. Eric On 01/16/2018 03:39 PM, Daniel Kiper wrote: On Fri, Jan 12, 2018 at 03:21:13PM -0600, Eric DeVolder wrote: When kexec is utilized in a Xen environment, it has an explicit run-time dependency on libxenctrl.so. This dependency occurs during the configure stage

[Xen-devel] [PATCH] ocaml: fix arm build

ARM doesn't have emulation_flags in the arch_domainconfig. Signed-off-by: Wei Liu --- Cc: Ian Jackson Cc: Julien Grall Cc: Andrew Cooper --- tools/ocaml/libs/xc/xenctrl_stubs.c | 6 ++ 1 file

Re: [Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

On Wed, Jan 17, 2018 at 04:24:27PM +, Ian Jackson wrote: > Roger Pau Monne writes ("[PATCH 6/6] firmware/shim: fix build process to use > POSIX find options"): > > The -printf find option is not POSIX compatible, so replace it with > > another rune. > ... > > cd $(D)/$(d); \ > >

Re: [Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

Roger Pau Monne writes ("[PATCH 6/6] firmware/shim: fix build process to use POSIX find options"): > The -printf find option is not POSIX compatible, so replace it with > another rune. ... > cd $(D)/$(d); \ > - find $(XEN_ROOT)/$(d)/ -type d -printf "./%P\n" | xargs

Re: [Xen-devel] Access I2C bus from guest/DomU on ARM board

Rajesh, On 17.01.18 16:03, Saumya Rajesh wrote: Just out of curiosity, is it possible to split the Driver for the Renesas RCar I2C unit [1] into frontend and backend to use the i2c bus from guest? Or to do something similar to PCI passthrough? Please forgive me if I sound illogical. I'm just

Re: [Xen-devel] [Embedded-pv-devel] Xen on RCarH3 Starter Kit

Hello Ganesh On 17.01.18 15:33, Ganesh H wrote: Dear Andrii, Sorry for the confusion. I am having an RCarH3 starter kit. Is there a Xen port available for RCarH3 starter kit right now? We did not run XEN on h3ulcb. But it can be done with minimal efforts IMHO. If not what are the steps to

[Xen-devel] [xen-unstable-smoke test] 118160: regressions - FAIL

flight 118160 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118160/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-xl-xsm 12 guest-start fail REGR. vs. 118105 build-armhf

Re: [Xen-devel] [PATCH 1/5] x86/idt: Factor out enabling and disabling of ISTs

On Fri, Jan 12, 2018 at 06:37:20PM +, Andrew Cooper wrote: > All alteration of IST settings (other than the crash path) happen in an > identical triple. Introduce helpers to keep the triple in sync, and reduce > the risk of opencoded mistakes. > > Signed-off-by: Andrew Cooper

Re: [Xen-devel] [PATCH 2/5] x86/pv: Rename invalidate_shadow_ldt() to pv_destroy_ldt()

On Fri, Jan 12, 2018 at 06:37:21PM +, Andrew Cooper wrote: > and move it into pv/descriptor-tables.c beside its GDT counterpart. Reduce > the !in_irq() check from a BUG_ON() to ASSERT(). > > Signed-off-by: Andrew Cooper Reviewed-by: Wei Liu

Re: [Xen-devel] [PATCH 1/5] xen/arm: Introduce enable callback to enable a capabilities on each online CPU

Hi Julien, > On 17 Jan 2018, at 12:31, Julien Grall wrote: > > If you took the code from Linux, you need to add the original Signed-off-by from the Linux commit. Aside from that: >>> >>> There are multiple commits touching this function. So I followed

[Xen-devel] [PATCH] Revert "xl: Default guest mode changed from PV to PVH with PV shim"

This breaks ARM. It should be protected by some x86 #if. For now, revert it, as it's not critical (and it isn't included in the comet/vixen security patch branches published via XSA-254). This reverts commit 63080b704351022cb7badb73339d47646fb465bd. Signed-off-by: Ian Jackson

Re: [Xen-devel] Access I2C bus from guest/DomU on ARM board

On Tue, Jan 16, 2018 at 9:22 PM, Andrii Anisov wrote: > Dear Rajesh, > > > You can try to get an I2C bus controller in DomU in PIO mode following > [1], keeping in mind [2]. > > If you want it DMA capable you need Renesas IPMMU support in XEN [3], [4] > to be

[Xen-devel] xl: Unable to boot Xen Arm guest when using latest staging

Hi all, Just a quick heads-up before I go into debugging. I have built and install the latest staging (db3ae8becc) for Arm. When I boot a guest, I get the following error message: libxl: debug: libxl_create.c:1664:do_domain_create: Domain 0:ao 0x386e44d0: create: how=(nil) callback=(nil)

[Xen-devel] [PATCH v2] x86/efi: fix build with linkers that support both coff-x86-64 and pe-x86-64

When using a linker that supports both formats the following error will be triggered: efi/buildid.o: file not recognized: File format is ambiguous efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 Solve this by specifying the efi/buildid.o format to pe-x86-64. Signed-off-by: Roger Pau

Re: [Xen-devel] [PATCH] x86/hvm: more sure APIC assist is aborted if guest EOIs APIC

> -Original Message- > From: Paul Durrant [mailto:paul.durr...@citrix.com] > Sent: 17 January 2018 12:54 > To: xen-devel@lists.xenproject.org > Cc: Paul Durrant ; Jan Beulich > ; Andrew Cooper > Subject: [PATCH]

Re: [Xen-devel] [PATCH for-4.10.0-shim-comet] x86/guest: use the vcpu_info area from shared_info

>>> On 17.01.18 at 12:04, wrote: > On 01/17/2018 10:57 AM, Roger Pau Monne wrote: >> If using less than 32 vCPUs (XEN_LEGACY_MAX_VCPUS). >> >> This is a workaround that should allow to boot the shim on hypervisors >> without commit "x86/upcall: inject a spurious event

[Xen-devel] [xen-unstable-smoke test] 118158: regressions - FAIL

flight 118158 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118158/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 118105 build-armhf

Re: [Xen-devel] [PATCH 1/5] xen/arm: Introduce enable callback to enable a capabilities on each online CPU

Hi Lars, On 17/01/18 12:23, Lars Kurth wrote: On 17 Jan 2018, at 10:31, Julien Grall > wrote: Hi Stefano, On 16/01/18 23:55, Stefano Stabellini wrote: On Tue, 16 Jan 2018, Julien Grall wrote: Once Xen knows what

Re: [Xen-devel] [PATCH] x86/efi: fix build with linkers that support both coff-x86-64 and pe-x86-64

>>> On 17.01.18 at 12:21, wrote: > On Mon, Jan 08, 2018 at 03:11:21AM -0700, Jan Beulich wrote: >> >>> On 05.01.18 at 17:43, wrote: >> > --- a/xen/arch/x86/Makefile >> > +++ b/xen/arch/x86/Makefile >> > @@ -188,20 +188,20 @@ endif >> > $(TARGET).efi:

Re: [Xen-devel] [PATCH 1/5] xen/arm: Introduce enable callback to enable a capabilities on each online CPU

> On 17 Jan 2018, at 10:31, Julien Grall wrote: > > Hi Stefano, > > On 16/01/18 23:55, Stefano Stabellini wrote: >> On Tue, 16 Jan 2018, Julien Grall wrote: >>> Once Xen knows what features/workarounds present on the platform, it >>> might be necessary to configure

Re: [Xen-devel] [PATCH v2 2/6] xen/pvh: place the trampoline at page 0x1

On Wed, Jan 17, 2018 at 12:00:41PM +, Roger Pau Monne wrote: > Since PVH guest jump straight into trampoline_setup trampoline_phys is > not initialized, thus the trampoline is relocated to address 0. > > This works, but has the undesirable effect of having VA 0 mapped to > MFN 0, which means

[Xen-devel] [PATCH v2] tools: fix arm build after bdf693ee61b48

The ramdisk fields were removed. We should use modules[0] instead. Signed-off-by: Wei Liu --- Cc: Stefano Stabellini Cc: Julien Grall Cc: Ian Jackson Verified the build with a qemu-chroot. ---

Re: [Xen-devel] [PATCH] x86/efi: fix build with linkers that support both coff-x86-64 and pe-x86-64

On Mon, Jan 08, 2018 at 03:11:21AM -0700, Jan Beulich wrote: > >>> On 05.01.18 at 17:43, wrote: > > When using a linker that supports both formats the following error > > will be triggered: > > > > efi/buildid.o: file not recognized: File format is ambiguous > >

Re: [Xen-devel] [PATCH] libxc: fix arm build after bdf693ee61b48

On Wed, Jan 17, 2018 at 10:43:40AM +, Wei Liu wrote: > The ramdisk fields were removed. We should use modules[0] instead. > > Signed-off-by: Wei Liu > --- > Cc: Stefano Stabellini > Cc: Julien Grall > Cc: Ian Jackson

Re: [Xen-devel] [PATCH for-4.10.0-shim-comet] x86/guest: use the vcpu_info area from shared_info

On 01/17/2018 11:16 AM, Ian Jackson wrote: > George Dunlap writes ("Re: [PATCH for-4.10.0-shim-comet] x86/guest: use the > vcpu_info area from shared_info"): >> Without this patch, people need to reboot their L0 hypervisor in order >> to use Comet. > > People running 4.10. On 4.8 this

Re: [Xen-devel] [PATCH for-4.10.0-shim-comet] x86/guest: use the vcpu_info area from shared_info

George Dunlap writes ("Re: [PATCH for-4.10.0-shim-comet] x86/guest: use the vcpu_info area from shared_info"): > Without this patch, people need to reboot their L0 hypervisor in order > to use Comet. People running 4.10. On 4.8 this presumably has no benefit. > The risk of checking it into the

Re: [Xen-devel] [PATCH 3/6] xen/pvshim: identity pin shim vCPUs to pCPUs

On Wed, Jan 17, 2018 at 09:48:11AM +, Roger Pau Monne wrote: > Since VCPUOP_{up/down} already identity pins vCPU hotplug to pCPU > hotplug also pin the vCPUs to the pCPUs in the scheduler. This prevent The description is a bit ambiguous. I read it as "the shim hotplug code pins vcpu to pcpu

Re: [Xen-devel] [PATCH v4] docs: note default for timer_mode in xl.cfg man

On Tue, Jan 16, 2018 at 10:28:56AM -0600, Doug Goldstein wrote: > There was no default documented but inspecting > libxl__domain_build_info_setdefault() shows the default to be > LIBXL_TIMER_MODE_NO_DELAY_FOR_MISSED_TICKS. > > Signed-off-by: Doug Goldstein Acked-by: Wei Liu

Re: [Xen-devel] [PATCH] libxc: fix arm build after bdf693ee61b48

Wei Liu writes ("[PATCH] libxc: fix arm build after bdf693ee61b48"): > The ramdisk fields were removed. We should use modules[0] instead. Acked-by: Ian Jackson ___ Xen-devel mailing list Xen-devel@lists.xenproject.org

Re: [Xen-devel] [Xen-users] DomU not starting under pvhv2

On Wed, 17 Jan 2018, Roger Pau Monné wrote: > On Mon, Jan 08, 2018 at 06:01:57PM +, George Dunlap wrote: > > Moving to xen-devel, and cc'ing Roger and Boris (who developed PVH) > > > > On Mon, Jan 8, 2018 at 5:24 AM, Peter wrote: > > > Hi. > > > > > > Running Xen

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

flight 118117 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/118117/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pygrub broken test-amd64-amd64-xl-qcow2

Re: [Xen-devel] [PATCH for-4.10.0-shim-comet] x86/guest: use the vcpu_info area from shared_info

On 01/17/2018 10:57 AM, Roger Pau Monne wrote: > If using less than 32 vCPUs (XEN_LEGACY_MAX_VCPUS). > > This is a workaround that should allow to boot the shim on hypervisors > without commit "x86/upcall: inject a spurious event after setting > upcall vector" as long as less than 32 vCPUs are

[Xen-devel] [PATCH for-4.10.0-shim-comet] x86/guest: use the vcpu_info area from shared_info

If using less than 32 vCPUs (XEN_LEGACY_MAX_VCPUS). This is a workaround that should allow to boot the shim on hypervisors without commit "x86/upcall: inject a spurious event after setting upcall vector" as long as less than 32 vCPUs are assigned to the shim. Signed-off-by: Roger Pau Monné

Re: [Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

On Wed, Jan 17, 2018 at 09:48:14AM +, Roger Pau Monne wrote: > The -printf find option is not POSIX compatible, so replace it with > another rune. > > Signed-off-by: Roger Pau Monné Acked-by: Wei Liu

Re: [Xen-devel] [PATCH 2/6] xen/pvh: place the trampoline at page 0x1

On Wed, Jan 17, 2018 at 09:48:10AM +, Roger Pau Monne wrote: > Since PVH guest jump straight into trampoline_setup trampoline_phys is > not initialized, thus the trampoline is relocated to address 0. > > This works, but has the undesirable effect of having VA 0 mapped to > MFN 0, which means

Re: [Xen-devel] [PATCH 5/6] xen/pvshim: fix coding style issues

On Wed, Jan 17, 2018 at 09:48:13AM +, Roger Pau Monne wrote: > Fix a couple of coding style issues. > > No code or functional change. > > Signed-off-by: Roger Pau Monné Reviewed-by: Wei Liu ___

Re: [Xen-devel] [PATCH 4/6] xen/pvshim: simplify replace_va_mapping code

On Wed, Jan 17, 2018 at 09:48:12AM +, Roger Pau Monne wrote: > No functional change. > > Signed-off-by: Roger Pau Monné Reviewed-by: Wei Liu ___ Xen-devel mailing list Xen-devel@lists.xenproject.org

[Xen-devel] [PATCH] libxc: fix arm build after bdf693ee61b48

The ramdisk fields were removed. We should use modules[0] instead. Signed-off-by: Wei Liu --- Cc: Stefano Stabellini Cc: Julien Grall Cc: Ian Jackson Verified the build with a qemu-chroot. ---

Re: [Xen-devel] [Xen-users] DomU not starting under pvhv2

On Mon, Jan 08, 2018 at 06:01:57PM +, George Dunlap wrote: > Moving to xen-devel, and cc'ing Roger and Boris (who developed PVH) > > On Mon, Jan 8, 2018 at 5:24 AM, Peter wrote: > > Hi. > > > > Running Xen 4.10.0 > > What version of Linux are you using? > > > > > A

Re: [Xen-devel] [PATCH 1/5] xen/arm: Introduce enable callback to enable a capabilities on each online CPU

Hi Stefano, On 16/01/18 23:55, Stefano Stabellini wrote: On Tue, 16 Jan 2018, Julien Grall wrote: Once Xen knows what features/workarounds present on the platform, it might be necessary to configure each online CPU. Introduce a new callback "enable" that will be called on each online CPU to

[Xen-devel] [xen-unstable-smoke test] 118150: regressions - FAIL

flight 118150 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118150/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 118105 build-armhf

Re: [Xen-devel] [PATCH v4] docs: note default for timer_mode in xl.cfg man

On Tue, Jan 16, 2018 at 10:28:56AM -0600, Doug Goldstein wrote: > There was no default documented but inspecting > libxl__domain_build_info_setdefault() shows the default to be > LIBXL_TIMER_MODE_NO_DELAY_FOR_MISSED_TICKS. > > Signed-off-by: Doug Goldstein Reviewed-by: Roger

[Xen-devel] [xen-unstable-coverity test] 118152: all pass - PUSHED

flight 118152 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/118152/ Perfect :-) All tests in this flight passed as required version targeted for testing: xen e871e80c38547d9faefc6604532ba3e985e65873 baseline version: xen

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

> -Original Message- [snip] > What I meant was that I'd expect the guest to have interrupts disabled whilst > poking the MSR to enable APIC assist on that CPU, since enabling APIC assist > is clearly going to modify the way in which interrupts are handled. If that's > not the case though

[Xen-devel] [linux-linus test] 118112: tolerable FAIL - PUSHED

flight 118112 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/118112/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 117996 test-armhf-armhf-libvirt 14

[Xen-devel] [PATCH 3/6] xen/pvshim: identity pin shim vCPUs to pCPUs

Since VCPUOP_{up/down} already identity pins vCPU hotplug to pCPU hotplug also pin the vCPUs to the pCPUs in the scheduler. This prevent vCPU migration and should improve performance. While there also use __cpumask_set_cpu instead of cpumask_set_cpu, there's no need to use the locked variant.

[Xen-devel] [PATCH 6/6] firmware/shim: fix build process to use POSIX find options

The -printf find option is not POSIX compatible, so replace it with another rune. Signed-off-by: Roger Pau Monné --- Cc: Ian Jackson Cc: Wei Liu --- tools/firmware/xen-dir/Makefile | 3 ++- 1 file changed, 2 insertions(+),

[Xen-devel] [PATCH 0/6] xen/pvshim: fix for staging

Hello, The following series contain some code and style fixes for the pvshim (comet) code that has been merged into staging. IMHO patches 1-3 should be backported to the stable comet branch. A branch with the series is also available at: git://xenbits.xen.org/people/royger/xen.git

[Xen-devel] [PATCH 2/6] xen/pvh: place the trampoline at page 0x1

Since PVH guest jump straight into trampoline_setup trampoline_phys is not initialized, thus the trampoline is relocated to address 0. This works, but has the undesirable effect of having VA 0 mapped to MFN 0, which means NULL pointed dereferences no longer trigger a page fault. In order to

[Xen-devel] [PATCH 5/6] xen/pvshim: fix coding style issues

Fix a couple of coding style issues. No code or functional change. Signed-off-by: Roger Pau Monné --- Cc: Jan Beulich Cc: Andrew Cooper --- xen/arch/x86/pv/shim.c | 18 +- 1 file changed, 9 insertions(+), 9

[Xen-devel] [PATCH 1/6] xen/pvshim: map vcpu_info earlier for APs

Or else init_percpu_time is going to dereference a NULL pointer when trying to access vcpu_info. Signed-off-by: Roger Pau Monné --- Cc: Jan Beulich Cc: Andrew Cooper Cc: Ian Jackson Cc: Wei Liu

[Xen-devel] [PATCH 4/6] xen/pvshim: simplify replace_va_mapping code

No functional change. Signed-off-by: Roger Pau Monné --- Cc: Jan Beulich Cc: Andrew Cooper --- xen/arch/x86/pv/shim.c | 21 ++--- 1 file changed, 6 insertions(+), 15 deletions(-) diff --git

Re: [Xen-devel] [PATCH v8 08/17] x86/msr: Emulation of MSR_{SPEC_CTRL, PRED_CMD} for guests

From: Jan Beulich [jbeul...@suse.com] Sent: 17 January 2018 09:11 To: Andrew Cooper Cc: David Woodhouse; Xen-devel Subject: Re: [Xen-devel] [PATCH v8 08/17] x86/msr: Emulation of MSR_{SPEC_CTRL, PRED_CMD} for guests >>> On 16.01.18 at 17:58,

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

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 17 January 2018 08:52 > To: Paul Durrant > Cc: xen-devel ; osstest- > ad...@xenproject.org > Subject: RE: [Xen-devel] [xen-unstable test] 118078:

Re: [Xen-devel] [PATCH v8 12/17] x86/entry: Organise the use of MSR_SPEC_CTRL at each entry/exit point

No, not really. Omitting it on the grounds of "we don't expect to take a double fault" don't beat uniformally altering all the entrypoints in a consistent manor. The only thing which can go wrong is that we forget to do it when it is needed. ~Andrew

Re: [Xen-devel] [PATCH v8 08/17] x86/msr: Emulation of MSR_{SPEC_CTRL, PRED_CMD} for guests

>>> On 16.01.18 at 17:58, wrote: > On 16/01/18 11:10, David Woodhouse wrote: >> On Fri, 2018-01-12 at 18:00 +, Andrew Cooper wrote: >>> @@ -152,14 +163,38 @@ int guest_wrmsr(struct vcpu *v, uint32_t msr, >>> uint64_t val) >>> { >>> const struct vcpu *curr =

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

>>> On 16.01.18 at 18:30, wrote: >> From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf >> Of Paul Durrant >> Sent: 16 January 2018 09:27 >> > From: Jan Beulich [mailto:jbeul...@suse.com] >> > Sent: 16 January 2018 08:58 >> > >>> On 16.01.18 at

Re: [Xen-devel] [PATCH v8 12/17] x86/entry: Organise the use of MSR_SPEC_CTRL at each entry/exit point

>>> On 16.01.18 at 22:24, wrote: > On 15/01/18 12:09, Jan Beulich wrote: > On 12.01.18 at 19:01, wrote: >>> @@ -586,6 +611,10 @@ ENTRY(double_fault) >>> movl $TRAP_double_fault,4(%rsp) >>> /* Set AC to reduce chance of

Re: [Xen-devel] [PATCH v8 11/17] x86: Protect unaware domains from meddling hyperthreads

On 17/01/2018 08:40, Jan Beulich wrote: On 16.01.18 at 22:11, wrote: >> An alternative to the current levelling logic would be to treat STIBP as >> a Special Bit (in CPUID terms, like OSXSAVE/etc) and unconditionally set >> it equal to IBRS, irrespective of the

Re: [Xen-devel] [PATCH v8 11/17] x86: Protect unaware domains from meddling hyperthreads

>>> On 16.01.18 at 22:11, wrote: > An alternative to the current levelling logic would be to treat STIBP as > a Special Bit (in CPUID terms, like OSXSAVE/etc) and unconditionally set > it equal to IBRS, irrespective of the toolstack setting. That way, > migration

[Xen-devel] [xen-unstable-smoke test] 118146: regressions - FAIL

flight 118146 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/118146/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 6 xen-buildfail REGR. vs. 118105 build-armhf

Re: [Xen-devel] [PATCH] xen/efi: Avoid EFI stub using absolute symbols

>>> On 16.01.18 at 18:43, wrote: > On 12/01/18 13:13, Jan Beulich wrote: > On 09.01.18 at 20:43, wrote: >>> When I compiled the snippet on x86 and Arm, no relocation is available >>> for the pointers to string in the array in the final