On Mon, Mar 02, 2020 at 03:28:55PM +0100, Jan Beulich wrote:
> On 11.02.2020 10:31, Juergen Gross wrote:
> > One of the main design goals of core scheduling is to avoid actions
> > which are not directly related to the domain currently running on a
> > given cpu or core. Live patching is one of
On 3/2/20 2:28 PM, Jan Beulich wrote:
> On 11.02.2020 10:31, Juergen Gross wrote:
>> One of the main design goals of core scheduling is to avoid actions
>> which are not directly related to the domain currently running on a
>> given cpu or core. Live patching is one of those actions which are
>>
On 11.02.2020 10:31, Juergen Gross wrote:
> One of the main design goals of core scheduling is to avoid actions
> which are not directly related to the domain currently running on a
> given cpu or core. Live patching is one of those actions which are
> allowed taking place on a cpu only when the
Hi Juergen,
On 26/02/2020 14:17, Jürgen Groß wrote:
On 24.02.20 23:25, Julien Grall wrote:
Hi Juergen,
On 11/02/2020 09:31, Juergen Gross wrote:
diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c
index 6f9bec22d3..30c4c1830b 100644
--- a/xen/arch/arm/traps.c
+++ b/xen/arch/arm/traps.c
On 24.02.20 23:25, Julien Grall wrote:
Hi Juergen,
On 11/02/2020 09:31, Juergen Gross wrote:
diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c
index 6f9bec22d3..30c4c1830b 100644
--- a/xen/arch/arm/traps.c
+++ b/xen/arch/arm/traps.c
@@ -23,7 +23,6 @@
#include
#include
#include
Hi Juergen,
On 11/02/2020 09:31, Juergen Gross wrote:
diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c
index 6f9bec22d3..30c4c1830b 100644
--- a/xen/arch/arm/traps.c
+++ b/xen/arch/arm/traps.c
@@ -23,7 +23,6 @@
#include
#include
#include
-#include
#include
#include
> From: Juergen Gross
> Sent: Tuesday, February 11, 2020 5:31 PM
>
> One of the main design goals of core scheduling is to avoid actions
> which are not directly related to the domain currently running on a
> given cpu or core. Live patching is one of those actions which are
> allowed taking
On 11.02.2020 10:31, Juergen Gross wrote:
> One of the main design goals of core scheduling is to avoid actions
> which are not directly related to the domain currently running on a
> given cpu or core. Live patching is one of those actions which are
> allowed taking place on a cpu only when the
One of the main design goals of core scheduling is to avoid actions
which are not directly related to the domain currently running on a
given cpu or core. Live patching is one of those actions which are
allowed taking place on a cpu only when the idle scheduling unit is
active on that cpu.
