Hi Stefano,
On 24/05/18 00:47, Stefano Stabellini wrote:
On Tue, 22 May 2018, Julien Grall wrote:
Using current is fairly expensive, so save up into a variable.
Signed-off-by: Julien Grall
Good idea. I am curious to know actually how much this patch would save
but I
>>> On 24.05.18 at 12:13, wrote:
> On 24/05/18 09:13, Jan Beulich wrote:
> On 24.05.18 at 00:09, wrote:
>>> It is, as documented, not completely strictly true (according to the
>>> latest revision of the spec), but is there deliberately
On 24/05/18 09:13, Jan Beulich wrote:
On 24.05.18 at 00:09, wrote:
>> It is, as documented, not completely strictly true (according to the
>> latest revision of the spec), but is there deliberately to simply so we
>> don't give the guest implausible configurations.
Hi Stefano,
On 24/05/18 01:40, Stefano Stabellini wrote:
On Wed, 23 May 2018, Stefano Stabellini wrote:
On Tue, 22 May 2018, Julien Grall wrote:
In order to offer ARCH_WORKAROUND_2 support to guests, we need to track the
state of the workaround per-vCPU. The field 'pad' in cpu_info is now
Hi Stefano,
On 24/05/18 00:23, Stefano Stabellini wrote:
On Tue, 22 May 2018, Julien Grall wrote:
+extern enum ssbd_state ssbd_state;
+
+static inline enum ssbd_state get_ssbd_state(void)
+{
+return ssbd_state;
+}
+
DECLARE_PER_CPU(register_t, ssbd_callback_required);
static inline
On 23/05/18 21:54, Thomas Garnier wrote:
> Change the assembly code to use the new _ASM_MOVABS macro which get a
> symbol reference while being PIE compatible. Adapt the relocation tool
> to ignore 32-bit Xen code.
>
> Position Independent Executable (PIE) support will allow to extended the
>
>>> On 24.05.18 at 02:46, wrote:
> Port WARN_ON_ONCE macro from Linux.
In such a case you should justify adjustments you've made:
> --- a/xen/include/xen/lib.h
> +++ b/xen/include/xen/lib.h
> @@ -11,6 +11,19 @@
> #define BUG_ON(p) do { if (unlikely(p)) BUG(); } while
>>> On 24.05.18 at 00:09, wrote:
> It is, as documented, not completely strictly true (according to the
> latest revision of the spec), but is there deliberately to simply so we
> don't give the guest implausible configurations. There is not a
> processor with STIBP
Hello Stefano,
On 23.05.18 22:16, Stefano Stabellini wrote:
I meant "default y" because I am only trying to introduce the options
in this patch series, I am not trying to change the defaults (yet).
In any case, even with "default y" it works as intended if you start
from tiny.config.
1) cp
>>> On 24.05.18 at 02:46, wrote:
> --- a/xen/drivers/passthrough/arm/Makefile
> +++ b/xen/drivers/passthrough/arm/Makefile
> @@ -1,3 +1,3 @@
> obj-y += iommu.o
> -obj-y += smmu.o
> +obj-$(CONFIG_ARM_SMMU) += smmu.o
> obj-$(CONFIG_ARM_SMMU_v3) += smmu-v3.o
Same question
>>> On 24.05.18 at 02:46, wrote:
> Pull common defines for SMMU drives in a local header.
>
> Signed-off-by: Sameer Goel
> ---
> xen/drivers/passthrough/arm/arm_smmu.h | 125 +
This being a local header - why the arm_
>>> On 23.05.18 at 20:21, wrote:
> On Wed, 23 May 2018, Jan Beulich wrote:
>> >>> On 22.05.18 at 22:08, wrote:
>> > On Tue, 22 May 2018, Jan Beulich wrote:
>> >> >>> On 22.05.18 at 02:53, wrote:
>> >> > + $(eval
flight 123058 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/123058/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 16 guest-localmigrate/x10 fail
REGR. vs. 122804
>>> On 23.05.18 at 16:24, wrote:
> Now that we have a per-domain flag we can and should control sync-ing in
> a more fine grained manner: Only domains having XPTI enabled need the
> sync to occur.
>
> Signed-off-by: Jan Beulich
>
> --- a/xen/arch/x86/mm.c
101 - 114 of 114 matches
Mail list logo