On 21/03/18 05:46, Juergen Gross wrote:
> On 20/03/18 18:22, Andrew Cooper wrote:
>> On 20/03/18 16:58, Jan Beulich wrote:
>> On 19.03.18 at 20:13, wrote:
It is not entirely clear why this interlock was introduced in c/s 8cbb5278e
"x86/AMD: Add support for
On 28/02/2018 16:09, Sergey Dyasli wrote:
> diff --git a/xen/include/asm-x86/msr.h b/xen/include/asm-x86/msr.h
> index 419ab6f8a7..4747572871 100644
> --- a/xen/include/asm-x86/msr.h
> +++ b/xen/include/asm-x86/msr.h
> @@ -606,6 +606,9 @@ int init_vcpu_msr_policy(struct vcpu *v);
> int
On 28/02/2018 16:09, Sergey Dyasli wrote:
> @@ -474,6 +505,10 @@ int guest_wrmsr(struct vcpu *v, uint32_t msr, uint64_t
> val)
> break;
> }
>
> +case MSR_IA32_VMX_BASIC ... MSR_IA32_VMX_VMFUNC:
> +/* None of these MSRs are writeable. */
> +goto gp_fault;
There
On 03/14/2018 10:43 PM, Simon Gaiser wrote:
> Commit fd8aa9095a95 ("xen: optimize xenbus driver for multiple
> concurrent xenstore accesses") made a subtle change to the semantic of
> xenbus_dev_request_and_reply() and xenbus_transaction_end().
>
> Before on an error response to XS_TRANSACTION_END
On Wed, Mar 21, 2018 at 11:09:13AM -0500, Doug Goldstein wrote:
> On 3/21/18 6:11 AM, George Dunlap wrote:
> > On 03/21/2018 03:01 AM, Doug Goldstein wrote:
> >> Created a new section just called 'CI' since this is adding GitLab CI
> >> and still leaving the old Travis CI files around. This
On Wed, 21 Mar 2018 15:20:17 +
Roger Pau Monné wrote:
>On Thu, Mar 22, 2018 at 12:25:40AM +1000, Alexey G wrote:
>> Roger, Paul,
>>
>> Here is what you suggest, just to clarify:
>>
>> 1. Add to Xen a new hypercall (+corresponding dmop) so QEMU can tell
>> Xen where
On Wed, Mar 21, 2018 at 09:46:21AM -0700, Maran Wilson wrote:
> On 3/21/2018 2:40 AM, Juergen Gross wrote:
> > On 21/03/18 10:28, Roger Pau Monné wrote:
> > > On Tue, Mar 20, 2018 at 09:48:56AM -0700, Maran Wilson wrote:
> > > > +/*
> > > >* C representation of the x86/HVM start info layout.
>
On Wed, 2018-03-21 at 15:24 +, George Dunlap wrote:
>
> If you're OK with those changes,
>
I am cool with every one of them.
> I can make them on check-in (as well as
> changing your email address)
>
And thanks for this as well,
Dario
--
<> (Raistlin Majere)
flight 121036 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121036/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
On 28/02/2018 16:09, Sergey Dyasli wrote:
> Currently, when nested virt is enabled, the set of L1 VMX features
> is fixed and calculated by nvmx_msr_read_intercept() as an intersection
> between the full set of Xen's supported L1 VMX features, the set of
> actual H/W features and, for
flight 120981 rumprun real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120981/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumprun 6 rumprun-buildfail REGR. vs. 106754
build-i386-rumprun
On 03/19/2018 12:58 PM, Jason Andryuk wrote:
> Commit 2cc42bac1c79 ("x86-64/Xen: eliminate W+X mappings") introduced a
> call to get_cpu_cap, which is fstack-protected. This is works on x86-64
> as commit 4f277295e54c ("x86/xen: init %gs very early to avoid page
> faults with stack protector")
On 03/15/2018 10:22 AM, Joao Martins wrote:
> All uploaded PM data from non-dom0 CPUs takes the info from vCPU 0 and
> changing only the acpi_id. For processors which P-state coordination type
> is HW_ALL (0xFD) it is OK to upload bogus P-state dependency information
> (_PSD), because Xen will
On 28/02/18 16:09, Sergey Dyasli wrote:
> New definitions provide a convenient way of accessing contents of
> VMX MSRs. They are separated into 5 logical blocks based on the
> availability conditions of MSRs in the each block:
>
> 1. vmx: [VMX_BASIC, VMX_VMCS_ENUM]
> 2. VMX_PROCBASED_CTLS2
On 28/02/2018 16:09, Sergey Dyasli wrote:
> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
> index aa0505036b..4856ad7c24 100644
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -1699,7 +1699,7 @@ static void vmx_update_guest_cr(struct vcpu *v,
>
On Fri, Mar 16, 2018 at 11:04:22PM +0530, Amit Singh Tomar wrote:
> diff --git a/xen/drivers/char/mvebu-uart.c b/xen/drivers/char/mvebu-uart.c
> new file mode 100644
> index 000..c88d5e7
> --- /dev/null
> +++ b/xen/drivers/char/mvebu-uart.c
> @@ -0,0 +1,260 @@
> +/*
> + *
On 21/03/18 16:18, Roger Pau Monné wrote:
> On Mon, Mar 19, 2018 at 07:13:41PM +, Andrew Cooper wrote:
>> xc_config is only used by xc_domain_create(), but by calling
>> libxl__arch_domain_{prepare,save}_config() we clobber the real settings with
>> the default settings.
>>
>> Move all data
On Mon, Mar 19, 2018 at 07:13:40PM +, Andrew Cooper wrote:
> The data it stores is initialised and exclusively used within
> libxl__domain_make(), with the important details written back elsewhere by
> libxl__arch_domain_save_config(). Prepare xc_config on libxl__domain_make()'s
> stack, and
On Mon, Mar 19, 2018 at 07:13:48PM +, Andrew Cooper wrote:
> In future patches, the structure will be extended with further information,
> and this is far cleaner than adding extra parameters.
>
> The python stubs are the only user which passes NULL for the existing config
> option (which is
On Mon, Mar 19, 2018 at 07:13:51PM +, Andrew Cooper wrote:
> XEN_DOMCTL_max_vcpus is a mandatory hypercall, but nothing actually prevents a
> toolstack from unpausing a domain with no vcpus.
>
> Originally, d->vcpus[] was an embedded array in struct domain, but c/s
> fb442e217 "x86_64: allow
On Mon, Mar 19, 2018 at 07:13:50PM +, Andrew Cooper wrote:
> XEN_DOMCTL_set_gnttab_limits is a fairly new hypercall, and is strictly
> mandatory. Adding support for it introduced a state where a domain has a
> mostly un-constructed grant table, and there were cases where mis-ordering of
>
On 3/21/18 11:58 AM, Wei Liu wrote:
> On Wed, Mar 21, 2018 at 11:09:13AM -0500, Doug Goldstein wrote:
>> On 3/21/18 6:11 AM, George Dunlap wrote:
>>> On 03/21/2018 03:01 AM, Doug Goldstein wrote:
Created a new section just called 'CI' since this is adding GitLab CI
and still leaving the
On Fri, Mar 16, 2018 at 02:06:39PM +, Andrew Cooper wrote:
> The data it stores is initialised and exclusively used within
> libxl__domain_make(), with the important details written back elsewhere by
> libxl__arch_domain_save_config(). Prepare xc_config on libxl__domain_make()'s
> stack, and
On Mon, Mar 19, 2018 at 07:13:41PM +, Andrew Cooper wrote:
> xc_config is only used by xc_domain_create(), but by calling
> libxl__arch_domain_{prepare,save}_config() we clobber the real settings with
> the default settings.
>
> Move all data and calls relating to xc_domain_create() into the
On Mon, Mar 19, 2018 at 07:13:49PM +, Andrew Cooper wrote:
> set_max_evtchn is somewhat weird. It was introduced with the event_fifo work,
> but has never been used. Still, it is a bounding on resources consumed by the
> event channel infrastructure, and should be part of createdomain,
>>> On 21.03.18 at 17:32, wrote:
> --- a/xen/common/Kconfig
> +++ b/xen/common/Kconfig
> @@ -44,6 +44,9 @@ config HAS_GDBSX
> config HAS_IOPORTS
> bool
>
> +config NEEDS_LIST_SORT
> +bool
> +
> config HAS_BUILD_ID
> string
> option
On Thu, Mar 22, 2018 at 02:56:56AM +1000, Alexey G wrote:
> On Wed, 21 Mar 2018 15:20:17 +
> Roger Pau Monné wrote:
>
> >On Thu, Mar 22, 2018 at 12:25:40AM +1000, Alexey G wrote:
> >> 8. As these MMCONFIG PCI conf reads occur out of context (just
> >> address/len/data
On Mon, Mar 19, 2018 at 07:13:42PM +, Andrew Cooper wrote:
> This is a tools only hypercall so fine to change. Altering the name avoids
> having confusing code such as config->config all over the hypervisor and
> toolstack.
>
> Signed-off-by: Andrew Cooper
On Wed, 21 Mar 2018 14:54:16 +
Paul Durrant wrote:
>> -Original Message-
>> From: Alexey G [mailto:x19...@gmail.com]
>> Sent: 21 March 2018 14:26
>> To: Roger Pau Monne
>> Cc: xen-devel@lists.xenproject.org; Andrew Cooper
>>
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemuu-win7-amd64
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu
> -Original Message-
> From: Alexey G [mailto:x19...@gmail.com]
> Sent: 21 March 2018 16:57
> To: Roger Pau Monne
> Cc: xen-devel@lists.xenproject.org; Andrew Cooper
> ; Ian Jackson ; Jan
> Beulich
On Tue, Mar 20, 2018 at 09:50:50AM -0700, Maran Wilson wrote:
> case LIBXL_DOMAIN_TYPE_PV:
> -ret = libxl__build_pv(gc, domid, info, state);
> +ret = libxl__build_pv(gc, domid, d_config, info, state);
> if (ret)
> goto out;
>
> diff --git
On 03/21/2018 01:49 PM, Wei Liu wrote:
> On Tue, Mar 20, 2018 at 09:50:50AM -0700, Maran Wilson wrote:
>> case LIBXL_DOMAIN_TYPE_PV:
>> -ret = libxl__build_pv(gc, domid, info, state);
>> +ret = libxl__build_pv(gc, domid, d_config, info, state);
>> if (ret)
>>
On Wed, Mar 21, 2018 at 04:47:22AM +, Julien Grall wrote:
> From: Wei Liu
>
> In a follow-up patches, some callers will be switched to pass
s/patches/patch/
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
On Wed, Mar 21, 2018 at 02:42:10PM +, Roger Pau Monne wrote:
> The start_info size calculated in bootlate_hvm is wrong. It should use
> HVMLOADER_MODULE_MAX_COUNT instead of dom->num_modules and it doesn't
> take into account the size of the modules command line.
>
> This is not a problem so
On Wed, Mar 21, 2018 at 02:42:11PM +, Roger Pau Monne wrote:
> This will lead to writing a wrong module command line physical memory
> address if no command line is actually provided.
>
> This hasn't caused problems so far because hvmloader is the only
> consumer of the modules command line,
On Wed, Mar 21, 2018 at 04:27:43PM +, Wei Liu wrote:
> On Tue, Mar 20, 2018 at 09:11:10AM +, Roger Pau Monné wrote:
> > On Tue, Mar 20, 2018 at 08:11:49AM +1000, Alexey G wrote:
> > > On Mon, 19 Mar 2018 17:01:18 +
> > > Roger Pau Monné wrote:
> > >
> > > >On
On 03/21/2018 10:18 AM, Roger Pau Monné wrote:
> On Wed, Mar 21, 2018 at 09:37:09AM -0400, Boris Ostrovsky wrote:
>> On 03/21/2018 06:07 AM, Roger Pau Monné wrote:
>>> On Tue, Mar 20, 2018 at 09:50:52AM -0700, Maran Wilson wrote:
From: Boris Ostrovsky
Title: Please drop the full stop.
On 03/13/2018 03:20 PM, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
IORT has a hierarchical structure containing PCIRC nodes, IORT nodes
and SMMU nodes. Each node has with it an array of ids and a mapping
which maps a range
On 03/21/2018 02:15 PM, Julien Grall wrote:
On 03/21/2018 04:58 AM, Manish Jaggi wrote:
Hi Julien,
On 03/20/2018 01:16 PM, Julien Grall wrote:
On 03/16/2018 11:58 AM, Manish Jaggi wrote:
This patchset is a Xen port of Marc's patchset.
arm64: KVM: Mediate access to GICv3 sysregs at EL2
On Tue, Mar 20, 2018 at 09:50:50AM -0700, Maran Wilson wrote:
> From: Boris Ostrovsky
>
> Since hvm_start_info has now been expanded to include memory map (i.e.
> e820) we need to know size of this map by the time we create
> dom->start_info_seg in
On Wed, Mar 21, 2018 at 10:58:40AM +1000, Alexey G wrote:
> On Tue, 20 Mar 2018 08:50:48 +
> Roger Pau Monné wrote:
>
> >On Tue, Mar 20, 2018 at 05:49:22AM +1000, Alexey G wrote:
> >> On Mon, 19 Mar 2018 15:58:02 +
> >> Roger Pau Monné wrote:
On 03/21/2018 02:59 PM, Julien Grall wrote:
Hi Manish,
Hi Julien,
On 03/13/2018 03:20 PM, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
IORT has a hierarchical structure containing PCIRC nodes, IORT nodes
and SMMU nodes. Each node has with it an array of
> -Original Message-
>
> > The question is why IOREQ_TYPE_COPY -> IOREQ_TYPE_PCI_CONFIG
> > translation is a must have thing at all? It won't make handling simpler.
> > For current QEMU implementation IOREQ_TYPE_COPY (MMIO accesses for
> > MMCONFIG) would be preferable as it allows to use
flight 121022 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121022/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 7a1358bbe73e5f749c3d2f53478dc1f30720f949
baseline version:
xen
On 03/21/2018 03:01 AM, Doug Goldstein wrote:
> Created a new section just called 'CI' since this is adding GitLab CI
> and still leaving the old Travis CI files around. This consolidates the
> two sections and adds the new files as well as adding another Travis
> file that was missing.
>
>
On Tue, Mar 20, 2018 at 10:03:51PM -0500, Doug Goldstein wrote:
> Doug Goldstein (8):
> ci: add README and makefile for containers
> ci: add Dockerfile for CentOS 7.2
> ci: add Dockerfile for Ubuntu 14.04
> ci: add Dockerfile for Ubuntu 16.04
> ci: add Dockerfile for Debian jessie
>
Hi Manish,
On 03/13/2018 03:20 PM, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
IORT has a hierarchical structure containing PCIRC nodes, IORT nodes
and SMMU nodes. Each node has with it an array of ids and a mapping
which maps a range of ids to another
On Tue, Mar 20, 2018 at 09:48:56AM -0700, Maran Wilson wrote:
> The start info structure that is defined as part of the x86/HVM direct boot
> ABI and used for starting Xen PVH guests would be more versatile if it also
> included a way to pass information about the memory map to the guest. This
>
On 21/03/18 10:28, Roger Pau Monné wrote:
> On Tue, Mar 20, 2018 at 09:48:56AM -0700, Maran Wilson wrote:
>> The start info structure that is defined as part of the x86/HVM direct boot
>> ABI and used for starting Xen PVH guests would be more versatile if it also
>> included a way to pass
On Tue, Mar 20, 2018 at 09:50:51AM -0700, Maran Wilson wrote:
> From: Boris Ostrovsky
> diff --git a/tools/libxl/libxl_x86.c b/tools/libxl/libxl_x86.c
> index 7cbbfd0..651b7d5 100644
> --- a/tools/libxl/libxl_x86.c
> +++ b/tools/libxl/libxl_x86.c
> @@ -582,6 +582,10 @@
Hi,
On 03/21/2018 09:34 AM, Manish Jaggi wrote:
On 03/21/2018 02:59 PM, Julien Grall wrote:
Hi Manish,
Hi Julien,
On 03/13/2018 03:20 PM, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
IORT has a hierarchical structure containing PCIRC nodes, IORT nodes
On 21/03/2018 09:05, Wei Liu wrote:
> On Tue, Mar 20, 2018 at 10:03:51PM -0500, Doug Goldstein wrote:
>> Doug Goldstein (8):
>> ci: add README and makefile for containers
>> ci: add Dockerfile for CentOS 7.2
>> ci: add Dockerfile for Ubuntu 14.04
>> ci: add Dockerfile for Ubuntu 16.04
>>
On Mon, Mar 19, 2018 at 07:43:09AM -0600, Jan Beulich wrote:
> >>> On 19.03.18 at 14:38, wrote:
> > Use the respective ARCH_CAPABILITIES MSR bit, but don't expose the MSR
> > to guests yet.
> >
> > Signed-off-by: Jan Beulich
> > Tested-by: Juergen Gross
Hi Manish,
On 03/21/2018 09:38 AM, Manish Jaggi wrote:
On 03/21/2018 02:15 PM, Julien Grall wrote:
On 03/21/2018 04:58 AM, Manish Jaggi wrote:
Hi Julien,
On 03/20/2018 01:16 PM, Julien Grall wrote:
On 03/16/2018 11:58 AM, Manish Jaggi wrote:
This patchset is a Xen port of Marc's
On Tue, Mar 20, 2018 at 09:50:52AM -0700, Maran Wilson wrote:
> From: Boris Ostrovsky
>
> Signed-off-by: Boris Ostrovsky
> Signed-off-by: Maran Wilson
> ---
> tools/libxc/xc_dom_x86.c | 29
Title: Please drop the full stop.
On 03/13/2018 03:20 PM, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
Code to query estimated IORT size for hardware domain.
IORT for hardware domain is generated using the requesterid and
deviceid map. Xen code requires the
Hello all,
I need to setup Xen on Snapdragon 820 platform - armv8 64 bit architecture.
Is there support available for the same ? Is there Xen implementation on
any other similar platform ?
Thanks and Regards,
Jay
___
Xen-devel mailing list
On 03/21/2018 09:20 AM, Takashi Iwai wrote:
On Wed, 21 Mar 2018 08:15:36 +0100,
Oleksandr Andrushchenko wrote:
On 03/20/2018 10:22 PM, Takashi Iwai wrote:
On Mon, 19 Mar 2018 08:22:19 +0100,
Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
flight 121017 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121017/
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. 120949
Tests which
>>> On 20.03.18 at 21:53, wrote:
> On Tue, 20 Mar 2018 03:36:57 -0600
> "Jan Beulich" wrote:
> On 19.03.18 at 22:20, wrote:
>>> On Mon, 19 Mar 2018 17:49:09 +
>>> Roger Pau Monné wrote:
On Tue, Mar 13,
On 19/03/18 14:41, Jan Beulich wrote:
> ... despite quite likely the gain being rather limited.
>
> Signed-off-by: Jan Beulich
Tested-by: Juergen Gross
Reviewed-by: Juergen Gross
Juergen
___
On 19/03/18 14:39, Jan Beulich wrote:
> Now that we zero all registers early on all entry paths, use that to
> avoid a couple of immediates here.
>
> Signed-off-by: Jan Beulich
> Acked-by: Andrew Cooper
Tested-by: Juergen Gross
On 19/03/18 14:40, Jan Beulich wrote:
> This exposes less code pieces and at the same time reduces the range
> covered from slightly above 3 pages to a little below 2 of them.
>
> The code being moved is unchanged, except for the removal of trailing
> blanks, insertion of blanks between operands,
> On 20 Mar 2018, at 17:38, George Dunlap wrote:
>
> On 03/19/2018 04:37 PM, Lars Kurth wrote:
>> And this time with patch: note to myself - never try sendmail with --compose
>> again (-;
>>
>> This patch contains a proposal to change
>>
On Wed, 21 Mar 2018 08:15:36 +0100,
Oleksandr Andrushchenko wrote:
>
> On 03/20/2018 10:22 PM, Takashi Iwai wrote:
> > On Mon, 19 Mar 2018 08:22:19 +0100,
> > Oleksandr Andrushchenko wrote:
> >> From: Oleksandr Andrushchenko
> >>
> >> Hello, all!
> >>
> >> In
>>> On 21.03.18 at 05:10, wrote:
> On 03/20/2018 10:35 AM, Jan Beulich wrote:
> On 15.03.18 at 21:30, wrote:
>>> If we change something in a vCPU that affects its runnability or
>>> otherwise needs the vCPU's attention, we might need to tell
Hi,
On Wed, Mar 21, 2018 at 11:27 AM, Jayadev Kumaran wrote:
> Hello all,
>
> I need to setup Xen on Snapdragon 820 platform - armv8 64 bit architecture.
> Is there support available for the same ? Is there Xen implementation on any
> other similar platform ?
From Initial
On 03/21/2018 04:58 AM, Manish Jaggi wrote:
Hi Julien,
On 03/20/2018 01:16 PM, Julien Grall wrote:
On 03/16/2018 11:58 AM, Manish Jaggi wrote:
This patchset is a Xen port of Marc's patchset.
arm64: KVM: Mediate access to GICv3 sysregs at EL2 [1]
The current RFC patchset is a subset of
On 03/21/2018 05:06 AM, Manish Jaggi wrote:
On 03/20/2018 01:13 PM, Julien Grall wrote:
On 03/16/2018 11:58 AM, Manish Jaggi wrote:
diff --git a/xen/arch/arm/cpuerrata.c b/xen/arch/arm/cpuerrata.c
index fe9e9facbe..d49698f785 100644.
--- a/xen/arch/arm/cpuerrata.c
+++
Hi Manish,
On 03/16/2018 11:58 AM, Manish Jaggi wrote:
This patch is ported to xen from linux commit
d70c7b31a60f2458f35c226131f2a01a7a98b6cf
Add a handler for reading/writing the guest's view of the ICC_BPR1_EL1
register, which is located in the ICH_VMCR_EL2.BPR1 field.
Signed-off-by: Manish
On 03/16/2018 11:58 AM, Manish Jaggi wrote:
This patch is ported to xen from linux commit:
f8b630bc542e0368886ae193d3519c832b270359
Add a handler for reading/writing the guest's view of the
ICC_IGRPEN1_EL1
The wrapping looks wrong.
register, which is located in the ICH_VMCR_EL2.VENG1
On 03/20/2018 03:47 PM, Daniel Vetter wrote:
On Tue, Mar 20, 2018 at 01:58:01PM +0200, Oleksandr Andrushchenko wrote:
On 03/19/2018 05:28 PM, Daniel Vetter wrote:
There should be no difference between immediate removal and delayed
removal of the drm_device from the xenbus pov. The lifetimes of
On 20.03.2018 13:05, Michael S. Tsirkin wrote:
> On Tue, Mar 20, 2018 at 09:58:23AM +0100, Laurent Vivier wrote:
>> Le 20/03/2018 à 02:54, Michael S. Tsirkin a écrit :
>>> QEMU coding style at the moment asks for all non-system
>>> include files to be used with #include "foo.h".
>>> However this
On 03/20/2018 10:22 PM, Takashi Iwai wrote:
On Mon, 19 Mar 2018 08:22:19 +0100,
Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Hello, all!
In order to provide explicit synchronization between backend and
frontend the following changes are
On 19/03/18 14:37, Jan Beulich wrote:
> Introduce a synthetic feature flag to use alternative instruction
> patching to NOP out all code on entry/exit paths. Having NOPs here is
> generally better than using conditional branches.
>
> Also change the limit on the number of bytes we can patch in
flight 120964 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120964/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-xsm 20 guest-start/debian.repeat fail REGR. vs. 120866
> -Original Message-
> From: Roger Pau Monne [mailto:roger@citrix.com]
> Sent: 20 March 2018 15:16
> To: xen-devel@lists.xenproject.org
> Cc: Boris Ostrovsky ; Konrad Rzeszutek Wilk
> ; Roger Pau Monne ; Ian
>
For mitigation of Meltdown the current L4 page table is copied to the
cpu local root page table each time a 64 bit pv guest is entered.
Copying can be avoided in cases where the guest L4 page table hasn't
been modified while running the hypervisor, e.g. when handling
interrupts or any hypercall
Avoid flushing the complete TLB when switching %cr3 for mitigation of
Meltdown by using the PCID feature if available.
We are using 4 PCID values for a 64 bit pv domain subject to XPTI and
2 values for the non-XPTI case:
- guest active and in kernel mode
- guest active and in user mode
-
Today cpu_info->xen_cr3 is either 0 to indicate %cr3 doesn't need to
be switched on entry to Xen, or negative for keeping the value while
indicating not to restore %cr3, or positive in case %cr3 is to be
restored.
Switch to use a flag byte instead of a negative xen_cr3 value in order
to allow
On 20/03/18 18:05, Paul Durrant wrote:
> Only in the legacy 'default server' case do we pass anything other than
> current->domain->domain_id, and in that case we pass the value of
> HVM_PARAM_DM_DOMAIN.
>
> The only known user of HVM_PARAM_DM_DOMAIN is qemu-trad, which always sets
I'd include
This patch series aims at reducing the overhead of the XPTI Meltdown
mitigation. It is based on Jan's XPTI speedup series.
Patch 1 had been posted before, the main changes in this patch are due
to addressing Jan's comments on my first version. The main objective of
that patch is to avoid copying
On Wed, Mar 21, 2018 at 08:16:00AM +0100, Thomas Huth wrote:
> On 20.03.2018 13:05, Michael S. Tsirkin wrote:
> > On Tue, Mar 20, 2018 at 09:58:23AM +0100, Laurent Vivier wrote:
> >> Le 20/03/2018 à 02:54, Michael S. Tsirkin a écrit :
> >>> QEMU coding style at the moment asks for all non-system
>
Am 21.03.2018 um 14:08 schrieb Michael S. Tsirkin:
> It still leaves us with a host of problems e.g. the problem of stale
> headers in the source directory.
There have already been suggestions in the past to forbid in-tree
builds. Would it help if configure would refuse to run from the root
Instead of switching XPTI globally on or off add a per-domain flag for
that purpose. This allows to modify the xpti boot parameter to support
running dom0 without Meltdown mitigations. Using "xpti=nodom0" as boot
parameter will achieve that.
Move the xpti boot parameter handling to
If possible use the INVPCID instruction for flushing the TLB instead of
toggling cr4.pge for that purpose.
While at it remove the dependency on cr4.pge being required for mtrr
loading, as this will be required later anyway.
Add a command line option "noinvpcid" for deactivating the use of
When switching to a 64-bit pv context the TLB is flushed twice today:
the first time when switching to the new address space in
write_ptbase(), the second time when switching to guest mode in
restore_to_guest.
Avoid the first TLB flush in that case.
Signed-off-by: Juergen Gross
Instead of flushing the TLB from global pages when switching address
spaces with XPTI being active just disable global pages via %cr4
completely when a domain subject to XPTI is active. This avoids the
need for extra TLB flushes as loading %cr3 will remove all TLB
entries.
In order to avoid
On Wed, Mar 21, 2018 at 03:08:36PM +0200, Michael S. Tsirkin wrote:
> On Wed, Mar 21, 2018 at 08:16:00AM +0100, Thomas Huth wrote:
> > On 20.03.2018 13:05, Michael S. Tsirkin wrote:
> > > On Tue, Mar 20, 2018 at 09:58:23AM +0100, Laurent Vivier wrote:
> > >> Le 20/03/2018 à 02:54, Michael S.
On Wed, Mar 21, 2018 at 01:29:53PM +, Daniel P. Berrangé wrote:
> On Wed, Mar 21, 2018 at 03:08:36PM +0200, Michael S. Tsirkin wrote:
> > On Wed, Mar 21, 2018 at 08:16:00AM +0100, Thomas Huth wrote:
> > > On 20.03.2018 13:05, Michael S. Tsirkin wrote:
> > > > On Tue, Mar 20, 2018 at 09:58:23AM
> -Original Message-
> From: Roger Pau Monne [mailto:roger@citrix.com]
> Sent: 20 March 2018 15:16
> To: xen-devel@lists.xenproject.org
> Cc: Boris Ostrovsky ; Konrad Rzeszutek Wilk
> ; Roger Pau Monne ; Jan
>
On 03/21/2018 05:42 AM, Roger Pau Monné wrote:
> On Tue, Mar 20, 2018 at 09:50:51AM -0700, Maran Wilson wrote:
>> From: Boris Ostrovsky
>> diff --git a/tools/libxl/libxl_x86.c b/tools/libxl/libxl_x86.c
>> index 7cbbfd0..651b7d5 100644
>> --- a/tools/libxl/libxl_x86.c
On Wed, Mar 21, 2018 at 02:15:20PM +0100, Stefan Weil wrote:
> Am 21.03.2018 um 14:08 schrieb Michael S. Tsirkin:
> > It still leaves us with a host of problems e.g. the problem of stale
> > headers in the source directory.
>
> There have already been suggestions in the past to forbid in-tree
>
flight 121021 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/121021/
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. 120949
Tests which
> -Original Message-
> From: Roger Pau Monne [mailto:roger@citrix.com]
> Sent: 20 March 2018 15:16
> To: xen-devel@lists.xenproject.org
> Cc: Boris Ostrovsky ; Konrad Rzeszutek Wilk
> ; Roger Pau Monne ; Jan
>
On 03/21/2018 06:07 AM, Roger Pau Monné wrote:
> On Tue, Mar 20, 2018 at 09:50:52AM -0700, Maran Wilson wrote:
>> From: Boris Ostrovsky
>>
>> Signed-off-by: Boris Ostrovsky
>> Signed-off-by: Maran Wilson
>> ---
>>
On 03/21/2018 02:11 PM, Jan Beulich wrote:
On 21.03.18 at 05:47, wrote:
From: Wei Liu
In a follow-up patches, some callers will be switched to pass
INVALID_MFN instead of zero for non-present mappings. So skip
incrementing mfn if it is not a valid
On Wed, 21 Mar 2018 17:06:28 +
Paul Durrant wrote:
[...]
>> Well, this might work actually. Although the overall scenario will be
>> overcomplicated a bit for _PCI_CONFIG ioreqs. Here is how it will
>> look:
>>
>> QEMU receives PCIEXBAR update -> calls the new dmop
flight 120965 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120965/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-1 50 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 120116
1 - 100 of 209 matches
Mail list logo