From: Oleksandr Andrushchenko
It is now not fully possible to control if and which virtual devices
are created by the frontend, e.g. keyboard and pointer devices
are always created and multi-touch device is created if the
backend advertises multi-touch support. In some cases this
behavior is not
On 04/25/2018 08:16 PM, Dongwon Kim wrote:
On Wed, Apr 25, 2018 at 08:34:55AM +0200, Daniel Vetter wrote:
On Wed, Apr 25, 2018 at 09:07:07AM +0300, Oleksandr Andrushchenko wrote:
On 04/24/2018 11:35 PM, Dongwon Kim wrote:
Had a meeting with Daniel and talked about bringing out generic
part of
On 26/04/18 19:41, Stewart Hildebrand wrote:
> A user may choose to set his/her own PKG_CONFIG_PATH, which is useful in the
> case of cross-compiling. We don't want to completely override the
> PKG_CONFIG_PATH, just add to it.
>
> Signed-off-by: Stewart Hildebrand
Release-acked-by: Juergen Gros
On 04/27/2018 12:14 AM, Dmitry Torokhov wrote:
Hi Oleksandr,
On Tue, Apr 24, 2018 at 10:31:38AM +0300, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
It is now not possible to control if and which virtual devices
are created by the frontend, e.g. keyboard and pointer devices
are
flight 122408 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122408/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd 7 xen-boot fail REGR. vs. 122395
test-armhf-armhf-lib
flight 122457 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122457/
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 1
flight 122453 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122453/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
Hi Oleksandr,
On Tue, Apr 24, 2018 at 10:31:38AM +0300, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> It is now not possible to control if and which virtual devices
> are created by the frontend, e.g. keyboard and pointer devices
> are always created and multi-touch device i
On 04/26/2018 10:16 PM, Dmitry Torokhov wrote:
On Tue, Apr 24, 2018 at 08:55:19AM +0300, Oleksandr Andrushchenko wrote:
On 04/23/2018 09:53 PM, Dmitry Torokhov wrote:
On Thu, Apr 19, 2018 at 02:44:19PM +0300, Oleksandr Andrushchenko wrote:
On 04/19/2018 02:25 PM, Juergen Gross wrote:
On 18/04
On Tue, Apr 24, 2018 at 08:55:19AM +0300, Oleksandr Andrushchenko wrote:
> On 04/23/2018 09:53 PM, Dmitry Torokhov wrote:
> > On Thu, Apr 19, 2018 at 02:44:19PM +0300, Oleksandr Andrushchenko wrote:
> > > On 04/19/2018 02:25 PM, Juergen Gross wrote:
> > > > On 18/04/18 17:04, Oleksandr Andrushchenk
flight 122404 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122404/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail like 122344
test-armhf-armhf-libvirt 14 saveresto
> From: Ian Jackson
> Sent: Thursday, April 26, 2018 1:44 PM
> Subject: Re: [PATCH] tools: prepend to PKG_CONFIG_PATH when
> configuring qemu
>
> Stewart Hildebrand writes ("[PATCH] tools: prepend to PKG_CONFIG_PATH
> when configuring qemu"):
> > A user may choose to set his/her own PKG_CONFIG_PAT
The following changes since commit b8846a4d6352b2a1d2012f8b3b9115640524aeda:
vl.c: new function serial_max_hds() (2018-04-26 13:58:29 +0100)
are available in the git repository at:
https://xenbits.xen.org/git-http/people/iwj/qemu.git
tags/for-upstream.depriv-2
for you to fetch changes up t
Peter Maydell writes ("Re: [PULL v9 00/16] xen: xen-domid-restrict
improvements"):
> On 26 April 2018 at 18:36, Ian Jackson wrote:
> > I can do that. Alternatively you could manually verify the signature
> > on my email and observe that it mentions the correct commit hash.
>
> I could, but I ho
Stewart Hildebrand writes ("[PATCH] tools: prepend to PKG_CONFIG_PATH when
configuring qemu"):
> A user may choose to set his/her own PKG_CONFIG_PATH, which is useful in the
> case of cross-compiling. We don't want to completely override the
> PKG_CONFIG_PATH, just add to it.
Acked-by: Ian Jacks
On 26 April 2018 at 18:36, Ian Jackson wrote:
> Peter Maydell writes ("Re: [PULL v9 00/16] xen: xen-domid-restrict
> improvements"):
>> Hi -- my apply-pullreq script thinks this isn't a signed tag:
>>
>> error: remotes/iwj/for-upstream.depriv-2: cannot verify a non-tag object of
>> type commit. D
A user may choose to set his/her own PKG_CONFIG_PATH, which is useful in the
case of cross-compiling. We don't want to completely override the
PKG_CONFIG_PATH, just add to it.
Signed-off-by: Stewart Hildebrand
---
tools/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Peter Maydell writes ("Re: [PULL v9 00/16] xen: xen-domid-restrict
improvements"):
> Hi -- my apply-pullreq script thinks this isn't a signed tag:
>
> error: remotes/iwj/for-upstream.depriv-2: cannot verify a non-tag object of
> type commit. Does not appear to be a signed tag
It isn't. It's not
On 04/26/2018 11:55 AM, Jan Beulich wrote:
On 26.04.18 at 17:20, wrote:
>> On 04/26/2018 09:33 AM, Jan Beulich wrote:
> -static void svm_sync_vmcb(struct vcpu *v)
> +static void svm_sync_vmcb(struct vcpu *v, enum vmcb_sync_state new_state)
> {
> struct arch_svm_struct *a
On 26 April 2018 at 16:56, Ian Jackson wrote:
> From: Ian Jackson
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The following changes since commit b8846a4d6352b2a1d2012f8b3b9115640524aeda:
>
> vl.c: new function serial_max_hds() (2018-04-26 13:58:29 +0100)
>
> are available in the g
On 26/04/18 17:12, Konrad Rzeszutek Wilk wrote:
> On Tue, Apr 24, 2018 at 08:44:57AM +0200, Juergen Gross wrote:
>> "make -C docs all" fails due to incorrect markdown syntax in
>> livepatch.markdown. Correct it.
>>
>> Signed-off-by: Juergen Gross
>> ---
>> docs/misc/livepatch.markdown | 589
>> +
On 26/04/18 17:00, Jan Beulich wrote:
On 24.04.18 at 08:44, wrote:
>> Many of the architecture specific boot parameters are not qualified
>> as such. Correct that.
>
> I think we want to distinguish between ones really only be meaningful for
> some architecture vs ones which are currently on
xc_interface_open etc. is not going to work if we have dropped
privilege, but xendevicemodel_shutdown will if everything is new
enough.
xendevicemodel_shutdown is only availabe in Xen 4.10 and later, so
provide a stub for earlier versions.
Signed-off-by: Ian Jackson
Reviewed-by: Anthony PERARD
And insist that it works.
Drop individual use of xendevicemodel_restrict and
xenforeignmemory_restrict. These are not actually effective in this
version of qemu, because qemu has a large number of fds open onto
various Xen control devices.
The restriction arrangements are still not right, becaus
Signed-off-by: Ian Jackson
CC: Paolo Bonzini
CC: Markus Armbruster
CC: Daniel P. Berrange
CC: Michael Tokarev
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Thomas Huth
---
os-posix.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/os-posix.c b/os-posix.c
index 0f5
This is called just before os_setup_post. Currently none of the
accelerators provide this hook, but the Xen one is going to provide
one in a moment.
Signed-off-by: Ian Jackson
Reviewed-by: Eduardo Habkost
---
accel/accel.c | 9 +
include/sysemu/accel.h | 3 +++
vl.c
From: Ross Lagerwall
Xen unstable (to be in 4.11) has two new dmops, relocate_memory and
pin_memory_cacheattr. Use these to set up the VGA memory, replacing the
previous calls to libxc. This allows the VGA console to work properly
when QEMU is running restricted (-xen-domid-restrict).
Wrapper fu
We are going to want to use the dummy xendevicemodel_handle type in
new stub functions in the CONFIG_XEN_CTRL_INTERFACE_VERSION < 41000
section. So we need to provide that definition, or (as applicable)
include the appropriate header, earlier in the file.
(Ideally the newer compatibility layers w
This allows the caller to specify a uid and gid to use, even if there
is no corresponding password entry. This will be useful in certain
Xen configurations.
We don't support just -runas because: (i) deprivileging without
calling setgroups would be ineffective (ii) given only a uid we don't
know
This makes it much easier to find a particular thing in config.log.
We have to use the ${BASH_LINENO[*]} syntax which is a syntax error in
other shells, so test what shell we are running and use eval.
The extra output is only printed if configure is run with bash. On
systems where /bin/sh is not
We need to restrict *all* the control fds that qemu opens. Looking in
/proc/PID/fd shows there are many; their allocation seems scattered
throughout Xen support code in qemu.
We must postpone the restrict call until roughly the same time as qemu
changes its uid, chroots (if applicable), and so on
This avoids checkpatch misparsing (as statements) long function
definitions or declarations, which sometimes start with constructs
like this:
static inline int xendevicemodel_relocate_memory(
xendevicemodel_handle *dmod, domid_t domid, ...
The type xendevicemodel_handle does not conform t
From: Ian Jackson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following changes since commit b8846a4d6352b2a1d2012f8b3b9115640524aeda:
vl.c: new function serial_max_hds() (2018-04-26 13:58:29 +0100)
are available in the git repository at:
https://xenbits.xen.org/git-http/people/iw
I'm going to be editing this function and it makes sense to clean up
this style problem in advance.
Signed-off-by: Ian Jackson
CC: Paolo Bonzini
CC: Markus Armbruster
CC: Daniel P. Berrange
CC: Michael Tokarev
Reviewed-by: Peter Maydell
Reviewed-by: Thomas Huth
---
os-posix.c | 10 +---
We are going to want to reuse this.
No functional change.
Signed-off-by: Ian Jackson
Reviewed-by: Anthony PERARD
Acked-by: Stefano Stabellini
---
hw/i386/xen/xen-hvm.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/i386/xen/xen-hvm.c b/hw/i386/xen/xen-hvm.c
index
The last user was just removed; remove this function, accordingly.
Signed-off-by: Ian Jackson
Acked-by: Anthony PERARD
---
include/hw/xen/xen_common.h | 22 --
1 file changed, 22 deletions(-)
diff --git a/include/hw/xen/xen_common.h b/include/hw/xen/xen_common.h
index 2eed6
perror() is defined to fprintf(stderr,...). HACKING says
fprintf(stderr,...) is wrong. So perror() is too.
Signed-off-by: Ian Jackson
CC: Paolo Bonzini
CC: Markus Armbruster
CC: Daniel P. Berrange
CC: Michael Tokarev
CC: Alistair Francis
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Al
From: Ross Lagerwall
Saving the current state to xenstore may fail when running restricted
(in particular, after a migration). Therefore, don't report the error or
exit when running restricted. Toolstacks that want to allow running
QEMU restricted should instead make use of QMP events to listen
From: Anthony PERARD
Xen libraries in 4.10 include a new xentoolcore library. This
contains the xentoolcore_restrict_all function which we are about to
want to use.
Signed-off-by: Ian Jackson
Acked-by: Stefano Stabellini
---
configure | 9 +++--
1 file changed, 7 insertions(+), 2 deletio
>>> On 26.04.18 at 17:20, wrote:
> On 04/26/2018 09:33 AM, Jan Beulich wrote:
-static void svm_sync_vmcb(struct vcpu *v)
+static void svm_sync_vmcb(struct vcpu *v, enum vmcb_sync_state new_state)
{
struct arch_svm_struct *arch_svm = &v->arch.hvm_svm;
-if (
On 26/04/18 16:32, Natarajan, Janakarajan wrote:
> On 4/16/2018 10:55 AM, Jan Beulich wrote:
> On 04.04.18 at 01:01, wrote:
>>>
>>> +int svm_avic_dom_init(struct domain *d)
>>> +{
>>> + int ret = 0;
>>> + struct page_info *pg;
>>> +
>>> + if ( !svm_avic || !has_vlapic(d) )
>>> +
On 4/16/2018 10:55 AM, Jan Beulich wrote:
On 04.04.18 at 01:01, wrote:
From: Suravee Suthikulpanit
Introduce AVIC base initialization code. This includes:
* Setting up per-VM data structures.
* Setting up per-vCPU data structure.
* Initializing AVIC-related VMCB bit fields.
Th
On 04/26/2018 09:33 AM, Jan Beulich wrote:
>>> -static void svm_sync_vmcb(struct vcpu *v)
>>> +static void svm_sync_vmcb(struct vcpu *v, enum vmcb_sync_state new_state)
>>> {
>>> struct arch_svm_struct *arch_svm = &v->arch.hvm_svm;
>>>
>>> -if ( arch_svm->vmcb_in_sync )
>>> -ret
flight 122399 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122399/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-examine11 examine-serial/bootloader fail REGR. vs. 122343
test-armhf-armhf-e
On Tue, Apr 24, 2018 at 08:44:57AM +0200, Juergen Gross wrote:
> "make -C docs all" fails due to incorrect markdown syntax in
> livepatch.markdown. Correct it.
>
> Signed-off-by: Juergen Gross
> ---
> docs/misc/livepatch.markdown | 589
> ---
> 1 file cha
>>> On 24.04.18 at 08:44, wrote:
> Some underscores are not escaped in xen-command-line.markdown.
> Correct that.
>
> Signed-off-by: Juergen Gross
Acked-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenpro
>>> On 24.04.18 at 08:44, wrote:
> Many of the architecture specific boot parameters are not qualified
> as such. Correct that.
I think we want to distinguish between ones really only be meaningful for
some architecture vs ones which are currently only implemented for just
one. For example ...
>
>>> On 24.04.18 at 08:44, wrote:
> Some of the boot parameters in docs/misc/xen-command-line.markdown are
> not in the correct alphabetically order. Correct that.
>
> Signed-off-by: Juergen Gross
Reviewed-by: Jan Beulich
___
Xen-devel mailing list
Osstest flight 122363, having hit an NMI watchdog timeout, shows CPU1 at
Xen call trace:
[] _spin_lock+0x30/0x57
[] update_last_cx_stat+0x29/0x42
[] cpu_idle.c#acpi_processor_idle+0x2ff/0x596
[] domain.c#idle_loop+0xa8/0xc3
and CPU0 at
Xen call trace:
[] on_selected_cpus+0xb7/0xde
These have been broken since the xen-staging list was withdrawn. I
have now made them work again by redirecting them to the xen-changelog
list. They can be distinguished from mails about stable branches by
the subject line tags.
Thanks for your attention.
Ian.
_
> If no one has commented on what seems pretty trivial (especially since
> checkpatch.pl has no official maintainer, but is more of a
> "whoever-touched-it-last" file at the moment), then including the patch
> in your pull request is perfectly acceptable. As a maintainer, it is
> also perfectly ac
DSA keys ("dss") are 1024-bit and not really considered good practice
any more. By default in Debian's openssh-server, they are now
disabled.
We are going to disable these soon. Can you please make sure that the
ssh keys you use to access xenbits are not DSA keys ? DSA keys start
with
ssh-dss
At 11:08 +0100 on 26 Apr (1524740921), Julien Grall wrote:
> On 20/04/18 13:25, Mirela Simonovic wrote:
> >> This looks a bit weird. AFAIU, if you disable the CPU interface, then you
> >> should never receive interrupt after. So why would you re-enable them?
> >>
> >> I realize the code in __c
On 04/26/2018 06:06 AM, Ian Jackson wrote:
> (expanding the CC to include everyone that get_maintainer suggests)
>
> Ian Jackson writes ("[PATCH 01/16] checkpatch: Add xendevicemodel_handle to
> the list of types"):
>> This avoids checkpatch misparsing (as statements) long function
>> definitions
Hi,
At 13:33 +0200 on 26 Apr (1524749590), Juergen Gross wrote:
> 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 whil
flight 122446 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122446/
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 1
>>> On 26.04.18 at 14:43, wrote:
> FWIW, In my not-yet-complete patch for the issue, I'd gone with
>
> @@ -90,7 +91,14 @@ UNLIKELY_END(svm_trace)
> pop %r13
> pop %r12
> pop %rbp
> +
> mov VCPU_svm_vmcb_pa(%rbx),%rax
> +cmpb $0, VCPU_svm_vmload_need
>>> On 15.01.18 at 19:12, wrote:
> --- a/xen/arch/x86/cpu/intel_pt.c
> +++ b/xen/arch/x86/cpu/intel_pt.c
> @@ -28,6 +28,107 @@
> bool_t __read_mostly opt_intel_pt = 1;
> boolean_param("intel_pt", opt_intel_pt);
>
> +
> +static void intel_pt_disable_intercept_for_msr(u32 addr_num)
> +{
> +s
>>> On 15.01.18 at 19:12, wrote:
> --- a/xen/arch/x86/cpu/intel_pt.c
> +++ b/xen/arch/x86/cpu/intel_pt.c
> @@ -21,7 +21,76 @@
> #include
> #include
> #include
> +#include
> +#include
>
> /* intel_pt: Flag to enable Intel Processor Trace (default on). */
> bool_t __read_mostly opt_intel
flight 122439 xen-4.10-testing running [real]
http://logs.test-lab.xenproject.org/osstest/logs/122439/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-pair queued
test-amd64-i386-
>>> On 15.01.18 at 19:12, wrote:
> --- a/xen/include/asm-x86/hvm/vmx/vmcs.h
> +++ b/xen/include/asm-x86/hvm/vmx/vmcs.h
> @@ -20,6 +20,7 @@
>
> #include
> #include
> +#include
>
> extern void vmcs_dump_vcpu(struct vcpu *v);
> extern void setup_vmcs_dump(void);
> @@ -171,6 +172,8 @@ struc
On 26/04/18 13:01, Jan Beulich wrote:
> While the main problem to be addressed here is the issue of what so far
> was named "vmcb_in_sync" starting out with the wrong value (should have
> been true instead of false, to prevent performing a VMSAVE without ever
> having VMLOADed the vCPU's state), go
On Thu, Apr 26, 2018 at 03:41:20AM -0600, Jan Beulich wrote:
> Commit df8234fd2c ("replace vCPU's dirty CPU mask by numeric ID") was
> too lax in two respects: First of all it didn't consider the case of a
> vCPU not having a valid dirty CPU in the descriptor table TLB flush
> case. This is the iss
>>> On 15.01.18 at 19:12, wrote:
> This patch configure VMCS to make Intel PT output address can be
> treat as guest physical address and translated by EPT when
> intel_pt option is true.
> There have some constraint condition on VMCS configuration,
> otherwise will cause VM entry failed.
>
> 1.
>>> On 15.01.18 at 19:12, wrote:
> --- a/docs/misc/xen-command-line.markdown
> +++ b/docs/misc/xen-command-line.markdown
> @@ -1009,6 +1009,13 @@ debug hypervisor only).
> ### idle\_latency\_factor
> > `= `
>
> +### intel\_pt
> +> `= `
> +
> +> Default: `true`
> +
> +Flag to enable Intel Proce
On Tue, Jan 16, 2018 at 02:12:31AM +0800, Luwei Kang wrote:
> Load/Store Intel processor trace register in context switch.
> MSR IA32_RTIT_CTL is loaded/stored automatically from VMCS.
> When Intel PT is supported in guest, we need load/restore
> PT MSRs only when PT is enabled in guest.
>
> Signe
On Tue, Jan 16, 2018 at 02:12:30AM +0800, Luwei Kang wrote:
>
> +#include
> +
> +struct pt_ctx {
> +u64 ctl;
> +u64 status;
> +u64 output_base;
> +u64 output_mask;
> +u64 cr3_match;
> +u64 addr[NUM_MSR_IA32_RTIT_ADDR];
uint64_t please.
> +};
> +
> +struct pt_desc {
> +
On Tue, Jan 16, 2018 at 02:12:26AM +0800, Luwei Kang wrote:
> Hi All,
>
> Here is a patch-series which adding Processor Trace enabling in XEN guest.
> You can get It's software developer manuals from:
> https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-exte
On Tue, Jan 16, 2018 at 02:12:27AM +0800, Luwei Kang wrote:
> This patch add a flag to enable Intel PT (Intel processor trace).
> Default value is 1 (enabled).
>
> Signed-off-by: Luwei Kang
> ---
> docs/misc/xen-command-line.markdown | 7 +++
> xen/arch/x86/cpu/Makefile | 1 +
>
While the main problem to be addressed here is the issue of what so far
was named "vmcb_in_sync" starting out with the wrong value (should have
been true instead of false, to prevent performing a VMSAVE without ever
having VMLOADed the vCPU's state), go a step further and make the
sync-ed state a t
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 no
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 "invpcid" for controlling the use of
INVPCID (d
Instead of having multiple places with more or less identical asm
statements just have one function doing a write to cr3.
As this function should be named write_cr3() rename the current
write_cr3() function to switch_cr3().
Suggested-by: Andrew Copper
Signed-off-by: Juergen Gross
Reviewed-by: J
This patch series aims at reducing the overhead of the XPTI Meltdown
mitigation.
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 the L4 page table each time the guest is
be
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
- hypervis
pv_guest_cr4_to_real_cr4() is becoming more and more complex. Convert
it from a macro to an ordinary function.
Signed-off-by: Juergen Gross
Reviewed-by: Jan Beulich
---
V6:
- new patch, split off from (old) patch 7 (Andrew Cooper)
---
xen/arch/x86/mm.c| 14 ++
xen/includ
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 states
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 %cr3
Add some helper macros to access the address and pcid parts of cr3.
Use those helpers where appropriate.
Signed-off-by: Juergen Gross
Reviewed-by: Jan Beulich
---
V6:
- new patch (Andrew Cooper)
---
xen/arch/x86/debug.c| 2 +-
xen/arch/x86/domain_page.c | 2 +-
xen/include/a
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=no-dom0" as boot
parameter will achieve that.
Move the xpti boot parameter handling to xen/arch/x86/p
>>> On 26.04.18 at 12:59, wrote:
> Dates are from Wei:
>
> Supported-Until:
>
> $ date --date '2017-12-13 + 18 months' +%F
> 2019-06-13
>
> Security-Support-Until:
>
> $ date --date '2019-06-13 + 18 months' +%F
> 2020-12-13
>
> CC: Lars Kurth
> CC: Juergen Gross
> CC: Jan Beulic
(expanding the CC to include everyone that get_maintainer suggests)
Ian Jackson writes ("[PATCH 01/16] checkpatch: Add xendevicemodel_handle to the
list of types"):
> This avoids checkpatch misparsing (as statements) long function
> definitions or declarations, which sometimes start with construc
Dates are from Wei:
Supported-Until:
$ date --date '2017-12-13 + 18 months' +%F
2019-06-13
Security-Support-Until:
$ date --date '2019-06-13 + 18 months' +%F
2020-12-13
CC: Lars Kurth
CC: Juergen Gross
CC: Jan Beulich
CC: Wei Liu
Signed-off-by: Ian Jackson
Reviewed-by: George
On 26/04/18 12:52, Ian Jackson wrote:
> Clarify what is expected of the release technician for SUPPORT.md: fix
> the version number field. The support dates will be set by the
> release manageer.
>
> Signed-off-by: Ian Jackson
> CC: Juergen Gross
Release-acked-by: Juergen Gross
Juergen
___
On 26/04/18 12:52, Ian Jackson wrote:
> This contains instructions and shell runes for the Release Technician,
> who is the person doing the technical admin to construct the release,
> fork branches, make tags and tarballs, etc.
>
> Rename it to make this clearer.
>
> Signed-off-by: Ian Jackson
>>> On 26.04.18 at 11:51, wrote:
> On 26/04/18 10:41, Jan Beulich wrote:
>> --- a/xen/arch/x86/mm.c
>> +++ b/xen/arch/x86/mm.c
>> @@ -1202,11 +1202,23 @@ void put_page_from_l1e(l1_pgentry_t l1e,
>> unlikely(((page->u.inuse.type_info & PGT_count_mask) != 0)) &&
>> (l1e_o
This contains instructions and shell runes for the Release Technician,
who is the person doing the technical admin to construct the release,
fork branches, make tags and tarballs, etc.
Rename it to make this clearer.
Signed-off-by: Ian Jackson
CC: Juergen Gross
---
docs/process/release-checkli
Clarify what is expected of the release technician for SUPPORT.md: fix
the version number field. The support dates will be set by the
release manageer.
Signed-off-by: Ian Jackson
CC: Juergen Gross
---
docs/process/release-technician-checklist.txt | 3 ++-
1 file changed, 2 insertions(+), 1 del
On Thu, Apr 26, 2018 at 12:48:44PM +0200, Juergen Gross wrote:
> Signed-off-by: Juergen Gross
Acked-by: Wei Liu
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Signed-off-by: Juergen Gross
---
docs/process/xen-release-management.pandoc | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/docs/process/xen-release-management.pandoc
b/docs/process/xen-release-management.pandoc
index 2ff0665b99..ac324981fd 100644
--- a/docs
flight 122398 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122398/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 122289
test-amd64-amd64-xl-qemut-win7-amd64 17
>>> On 26.04.18 at 12:05, wrote:
> Dates are from Lars.
>
> CC: Lars Kurth
> CC: Juergen Gross
> CC: Jan Beulich
> CC: George Dunlap
> CC: Wei Liu
> Signed-off-by: Ian Jackson
> ---
> SUPPORT.md | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/SUPPORT.md b/SUPP
On Thu, Apr 26, 2018 at 11:05:33AM +0100, Ian Jackson wrote:
> Dates are from Lars.
>
> CC: Lars Kurth
> CC: Juergen Gross
> CC: Jan Beulich
> CC: George Dunlap
> CC: Wei Liu
> Signed-off-by: Ian Jackson
> ---
> SUPPORT.md | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> dif
On 25/04/18 16:13, Mirela Simonovic wrote:
Hi Julien,
Hi Mirela,
On Mon, Apr 23, 2018 at 1:46 PM, Julien Grall wrote:
Hi,
On 20/04/18 13:25, Mirela Simonovic wrote:
Checking CPU errata should be done only when a CPU is initially booted.
It is assumed that the CPU which is hotplugged af
On 04/26/2018 11:05 AM, Ian Jackson wrote:
> Dates are from Lars.
>
> CC: Lars Kurth
> CC: Juergen Gross
> CC: Jan Beulich
> CC: George Dunlap
> CC: Wei Liu
> Signed-off-by: Ian Jackson
Reviewed-by: George Dunlap
___
Xen-devel mailing list
Xen-d
(+ Andre and Tim)
On 25/04/18 15:28, Mirela Simonovic wrote:
Hi Julien,
Hi,
On Wed, Apr 25, 2018 at 3:23 PM, Julien Grall wrote:
On 25/04/18 14:09, Mirela Simonovic wrote:
On Mon, Apr 23, 2018 at 1:33 PM, Julien Grall
wrote:
On 20/04/18 13:25, Mirela Simonovic wrote:
This looks a bit
Dates are from Lars.
CC: Lars Kurth
CC: Juergen Gross
CC: Jan Beulich
CC: George Dunlap
CC: Wei Liu
Signed-off-by: Ian Jackson
---
SUPPORT.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/SUPPORT.md b/SUPPORT.md
index 96002ea..3268270 100644
--- a/SUPPORT.md
+++ b/
On 26/04/18 10:41, Jan Beulich wrote:
> --- a/xen/arch/x86/mm.c
> +++ b/xen/arch/x86/mm.c
> @@ -1202,11 +1202,23 @@ void put_page_from_l1e(l1_pgentry_t l1e,
> unlikely(((page->u.inuse.type_info & PGT_count_mask) != 0)) &&
> (l1e_owner == pg_owner) )
> {
> +
Commit df8234fd2c ("replace vCPU's dirty CPU mask by numeric ID") was
too lax in two respects: First of all it didn't consider the case of a
vCPU not having a valid dirty CPU in the descriptor table TLB flush
case. This is the issue Manual has run into with NetBSD.
Additionally reads of ->dirty_cp
On 20/04/18 10:25, Jan Beulich wrote:
> HVM's MMIO cache only has a capacity of three entries. Once running out
> of entries, hvmemul_linear_mmio_access() will return
> X86EMUL_UNHANDLEABLE. Since gathers are an iterative process anyway,
> simply commit the portion of work done in this and hypothet
1 - 100 of 106 matches
Mail list logo