he
p2m list before they can be added.
Suggested-by: David Vrabel
Signed-off-by: Juergen Gross
---
drivers/xen/balloon.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/xen/balloon.c b/drivers/xen/balloon.c
index 0b52d92..52e331f 100644
--- a/drivers/x
ged memory above that size will not be usable by the domain.
Correct this by using a configurable size for the p2m list in case of
memory hotplug enabled (default supported memory size is 512 GB for
64 bit domains and 4 GB for 32 bit domains).
Signed-off-by: Juergen Gross
---
arch/x86/xen/p
Fix some regressions introduced in 3.16 and 3.19.
Juergen Gross (2):
xen: prepare p2m list for memory hotplug
xen: before ballooning hotplugged memory, set frames to invalid
arch/x86/xen/p2m.c| 13 -
drivers/xen/Kconfig | 13 +
drivers/xen/balloon.c | 13
On 03/19/2015 04:53 PM, Boris Ostrovsky wrote:
On 03/19/2015 10:31 AM, Juergen Gross wrote:
Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear
virtual mapped sparse p2m list") introduced a regression regarding to
memory hotplug for a pv-domain: as the virtual spa
On 03/19/2015 05:18 PM, David Vrabel wrote:
On 19/03/15 14:31, Juergen Gross wrote:
Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear
virtual mapped sparse p2m list") introduced a regression regarding to
memory hotplug for a pv-domain: as the virtual space for th
On 03/19/2015 05:18 PM, David Vrabel wrote:
On 19/03/15 14:31, Juergen Gross wrote:
Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
regions above the end of RAM as 1:1") introduced a regression.
To be able to add memory pages which were added via memory hotplug to
a
On 03/19/2015 05:14 PM, Daniel Kiper wrote:
On Thu, Mar 19, 2015 at 03:31:01PM +0100, Juergen Gross wrote:
Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to linear
virtual mapped sparse p2m list") introduced a regression regarding to
memory hotplug for a pv-domain: as t
On 03/19/2015 05:21 PM, Daniel Kiper wrote:
On Thu, Mar 19, 2015 at 03:31:02PM +0100, Juergen Gross wrote:
Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
regions above the end of RAM as 1:1") introduced a regression.
To be able to add memory pages which were added
failure of set_phys_to_machine() in patch 2 as requested
by David Vrabel and Daniel Kiper
- only call set_phys_to_machine() for pv domains as requested by Daniel Kiper
Juergen Gross (2):
xen: prepare p2m list for memory hotplug
xen: before ballooning hotplugged memory, set frames to invalid
arch/x86/xen/p2m
he
p2m list before they can be added.
Suggested-by: David Vrabel
Signed-off-by: Juergen Gross
---
drivers/xen/balloon.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/xen/balloon.c b/drivers/xen/balloon.c
index 0b52d92..65fedb8 100644
--- a/drivers/xen/balloon.c
+++ b/d
ged memory above that size will not be usable by the domain.
Correct this by using a configurable size for the p2m list in case of
memory hotplug enabled (default supported memory size is 512 GB for
64 bit domains and 4 GB for 32 bit domains).
Signed-off-by: Juergen Gross
---
arch/x86/xen/p
On 03/20/2015 02:46 PM, Daniel Kiper wrote:
On Fri, Mar 20, 2015 at 01:55:39PM +0100, Juergen Gross wrote:
Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
regions above the end of RAM as 1:1") introduced a regression.
To be able to add memory pages which were added
On 03/20/2015 02:44 PM, Boris Ostrovsky wrote:
On 03/20/2015 08:55 AM, Juergen Gross wrote:
Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
regions above the end of RAM as 1:1") introduced a regression.
To be able to add memory pages which were added via memory hotpl
On 02/25/2015 05:00 PM, Juergen Gross wrote:
On 02/25/2015 03:24 PM, David Vrabel wrote:
On 24/02/15 06:27, Juergen Gross wrote:
On 02/19/2015 07:07 PM, David Vrabel wrote:
On 18/02/2015 06:51, Juergen Gross wrote:
+{
+unsigned long pfn;
+unsigned long area_start, area_end
On 03/31/2015 02:15 PM, Bob Liu wrote:
From: Wei Liu
Originally Xen PV drivers only use single-page ring to pass along
information. This might limit the throughput between frontend and
backend.
The patch extends Xenbus driver to support multi-page ring, which in
general should improve throughp
On 03/31/2015 03:13 PM, Wei Liu wrote:
On Tue, Mar 31, 2015 at 02:36:43PM +0200, Juergen Gross wrote:
On 03/31/2015 02:15 PM, Bob Liu wrote:
From: Wei Liu
Originally Xen PV drivers only use single-page ring to pass along
information. This might limit the throughput between frontend and
r
being able to boot a Dom0 on a system with more than 512 GB memory.
Signed-off-by: Juergen Gross
Based-on-patch-by: Jan Beulich
---
arch/x86/xen/mmu.c | 126
arch/x86/xen/setup.c| 67 ++---
arch/x86/xen/xen-head.S |
On 04/09/2015 02:47 PM, David Vrabel wrote:
On 09/04/2015 07:55, Juergen Gross wrote:
Check whether the page tables built by the domain builder are at
memory addresses which are in conflict with the target memory map.
If this is the case just panic instead of running into problems
later
Check whether the page tables built by the domain builder are at
memory addresses which are in conflict with the target memory map.
If this is the case just panic instead of running into problems
later.
Signed-off-by: Juergen Gross
---
arch/x86/xen/mmu.c | 19 ---
arch/x86
Provide a service routine to check a physical memory area against the
E820 map. The routine will return false if the complete area is RAM
according to the E820 map and true otherwise.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 23 +++
arch/x86/xen/xen-ops.h
to be done in any case.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 34 ++
arch/x86/xen/xen-ops.h | 1 +
2 files changed, 35 insertions(+)
diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index 4666adf..606ac2b 100644
--- a/arch/x86/xen/se
Checks whether the pre-allocated memory of the loaded kernel is in
conflict with the target memory map. If this is the case, just panic
instead of run into problems later, as there is nothing we can do
to repair this situation.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 12
the domain limit is returned to the hypervisor instead of
being identity mapped, which was wrong anyway.
The kernel configuration parameter to specify the maximum size of a
domain can be deleted, as it is not relevant any more.
Signed-off-by: Juergen Gross
---
Documentation/kernel-parameter
This requires to memblock_reserve() the
start_info page on it's own.
Signed-off-by: Juergen Gross
---
arch/x86/xen/mmu.c | 232 ++---
arch/x86/xen/setup.c | 51 +--
arch/x86/xen/xen-ops.h | 3 +
3 files changed, 247 insertions(+), 39
In case the Xen tools indicate they don't need the p2m 3 level tree
as they support the virtual mapped linear p2m list, just omit building
the tree.
Signed-off-by: Juergen Gross
---
arch/x86/xen/p2m.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x8
sed at all, just delete it.
The only define left is P2M_PER_PAGE which is moved to page.h as well.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/xen/page.h | 6 --
arch/x86/xen/p2m.c | 6 +-
arch/x86/xen/p2m.h | 15 ---
arch/x86/x
For paravirtualized spinlocks setting the "slowpath" flag in
__ticket_enter_slowpath() is done via setting bit "0" in
lock->tickets.head instead of using a macro.
Change this by defining an appropriate macro.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/spinloc
With the paravirtualized spinlock unlock function being a pvops
function paravirt_ticketlocks_enabled is no longer needed. Remove it.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/spinlock.h | 3 ---
arch/x86/kernel/kvm.c| 14 --
arch/x86/kernel
.
Correct patching verified by disassembly of active kernel.
Juergen Gross (6):
x86: use macro instead of "0" for setting TICKET_SLOWPATH_FLAG
x86: move decision about clearing slowpath flag into arch_spin_lock()
x86: introduce new pvops function clear_slowpath
x86: introduce new pvop
s function pointer in order
to avoid spreading the knowledge which function to use.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/paravirt.h | 7 +++
arch/x86/include/asm/paravirt_types.h | 1 +
arch/x86/include/asm/spinlock.h | 18 --
arch/x86/ke
There is no need any more for a special treatment of _raw_spin_unlock()
regarding inlining compared to the other spinlock functions. Just treat
it like all the other spinlock functions.
Remove selecting UNINLINE_SPIN_UNLOCK in case of PARAVIRT_SPINLOCKS.
Signed-off-by: Juergen Gross
---
arch
__ticket_check_and_clear_slowpath() and the slowpath flag isn't
set.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/spinlock.h | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/arch/x86/include/asm/spinlock.h b/arch/x86/include/asm/spinlock.h
We even are not dependant on the order of lock prefix and
paravirtualization patching as the sample instruction is subject to
lock prefix patching as well.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/paravirt.h | 6 ++
arch/x86/include/asm/paravirt_types.h | 11 +++
arch/
ve old patch 08 (detect pre-allocated memory interfering with e820 map)
Juergen Gross (15):
xen: sync with xen headers
xen: save linear p2m list address in shared info structure
xen: don't build mfn tree if tools don't need it
xen: eliminate scalability issues from initial mapping
Use the newest headers from the xen tree to get some new structure
layouts.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/xen/interface.h | 96
include/xen/interface/xen.h | 10 ++--
2 files changed, 93 insertions(+), 13 deletions(-)
diff
before the memory might be clobbered by
xen_set_identity_and_remap(). This requires to not destroy the Xen
E820 map when the one for the system is being constructed.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 98 +++-
1 file changed, 58
Instead of using a function local static e820 map in xen_memory_setup()
and calling various functions in the same source with the map as a
parameter use a map directly accessible by all functions in the source.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/setup.c
Check whether the initrd is placed at a location which is conflicting
with the target E820 map. If this is the case relocate it to a new
area unused up to now and compliant to the E820 map.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 51
early_memremap_ro() to provide this read only
mapping.
Signed-off-by: Juergen Gross
---
include/asm-generic/early_ioremap.h | 2 ++
include/asm-generic/fixmap.h| 3 +++
mm/early_ioremap.c | 11 +++
3 files changed, 16 insertions(+)
diff --git a/include/asm-generic
of the p2m list. Reading the
generation count the Xen tools can detect changes of the mappings
and re-read the p2m list eventually.
Signed-off-by: Juergen Gross
---
arch/x86/xen/p2m.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/x86/xen/p2m.c b/arch/x86/xen/p2m.c
Add myself as maintainer for the Xen pvUSB stuff.
Signed-off-by: Juergen Gross
Acked-by: Konrad Rzeszutek Wilk
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d8afd29..5f54a0d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10965,6
Add the definition of pvUSB protocol used between the pvUSB frontend in
a Xen domU and the pvUSB backend in a Xen driver domain (usually Dom0).
This header was originally provided by Fujitsu for Xen based on Linux
2.6.18.
Changes are:
- adapt to Linux style guide
Signed-off-by: Juergen Gross
- adapted frontend to newer kernel version and use new pvUSB
interface macros
- set port status in one chunk as suggested by Oliver Neukum
Juergen Gross (3):
usb: Add Xen pvUSB protocol description
usb: Introduce Xen pvUSB frontend
xen: add Xen pvUSB maintainer
MAINTAINERS
Signed-off-by: Juergen Gross
---
drivers/usb/Kconfig|2 +
drivers/usb/Makefile |2 +
drivers/usb/xen/Kconfig| 10 +
drivers/usb/xen/Makefile |5 +
drivers/usb/xen/xen-usbfront.c | 1647
5 files changed, 1666
On 06/12/2015 06:23 PM, Greg KH wrote:
On Fri, Jun 12, 2015 at 04:09:59PM +0200, Juergen Gross wrote:
+enum usb_spec_version {
+ USB_VER_UNKNOWN = 0,
+ USB_VER_USB11,
+ USB_VER_USB20,
+ USB_VER_USB30, /* not supported yet */
+};
+
You are defining a bunch of things in
On 06/12/2015 06:20 PM, Greg KH wrote:
On Fri, Jun 12, 2015 at 04:10:00PM +0200, Juergen Gross wrote:
Introduces the Xen pvUSB frontend. With pvUSB it is possible for a Xen
domU to communicate with a USB device assigned to that domU. The
communication is all done via the pvUSB backend in a
Add myself as maintainer for the Xen pvUSB stuff.
Signed-off-by: Juergen Gross
Acked-by: Konrad Rzeszutek Wilk
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d8afd29..8ef4e83 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10965,6
new pvUSB
interface macros
- set port status in one chunk as suggested by Oliver Neukum
Juergen Gross (3):
usb: Add Xen pvUSB protocol description
usb: Introduce Xen pvUSB frontend (xen hcd)
xen: add Xen pvUSB maintainer
MAINTAINERS |8 +
drivers/usb/host/Kconfig
Linux style guide
- minor code modifications to increase readability
Signed-off-by: Juergen Gross
---
drivers/usb/host/Kconfig | 11 +
drivers/usb/host/Makefile |1 +
drivers/usb/host/xen-hcd.c | 1638
3 files changed, 1650 insertions(+)
create
Add the definition of pvUSB protocol used between the pvUSB frontend in
a Xen domU and the pvUSB backend in a Xen driver domain (usually Dom0).
This header was originally provided by Fujitsu for Xen based on Linux
2.6.18.
Changes are:
- adapt to Linux style guide
Signed-off-by: Juergen Gross
AFAIK there are no outstanding questions for more than one month now.
I'd appreciate some feedback or accepting these patches.
Juergen
On 04/30/2015 12:53 PM, Juergen Gross wrote:
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reaso
On 06/16/2015 04:45 PM, Greg KH wrote:
On Tue, Jun 16, 2015 at 04:32:34PM +0200, Juergen Gross wrote:
Introduces the Xen pvUSB frontend. With pvUSB it is possible for a Xen
domU to communicate with a USB device assigned to that domU. The
communication is all done via the pvUSB backend in a
Add myself as maintainer for the Xen pvUSB stuff.
Signed-off-by: Juergen Gross
Acked-by: Konrad Rzeszutek Wilk
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d8afd29..8ef4e83 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10965,6
Add the definition of pvUSB protocol used between the pvUSB frontend in
a Xen domU and the pvUSB backend in a Xen driver domain (usually Dom0).
This header was originally provided by Fujitsu for Xen based on Linux
2.6.18.
Changes are:
- adapt to Linux style guide
Signed-off-by: Juergen Gross
ns to the pvUSB interface
description to make it independant from linux kernel USB internals
- adapted frontend to newer kernel version and use new pvUSB
interface macros
- set port status in one chunk as suggested by Oliver Neukum
Juergen Gross (3):
usb: Add Xen pvUSB protocol description
Linux style guide
- minor code modifications to increase readability
Signed-off-by: Juergen Gross
---
drivers/usb/host/Kconfig | 11 +
drivers/usb/host/Makefile |1 +
drivers/usb/host/xen-hcd.c | 1594
3 files changed, 1606 insertions(+)
create
Ping?
Anything missing from my side?
On 04/30/2015 12:53 PM, Juergen Gross wrote:
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reason are the more complex locking
and unlocking functions. Especially unlocking is no longer just one
On 05/27/2015 07:05 PM, David Vrabel wrote:
On 27/05/15 17:25, David Vrabel wrote:
On 20/04/15 06:23, Juergen Gross wrote:
64 bit pv-domains under Xen are limited to 512 GB of RAM today. The
main reason has been the 3 level p2m tree, which was replaced by the
virtual mapped linear p2m list
Use the newest headers from the xen tree to get some new structure
layouts.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/include/asm/xen/interface.h | 96
include/xen/interface/xen.h | 10 ++--
2 files changed, 93 insertions
riables)
- remove old patch 08 (detect pre-allocated memory interfering with e820 map)
Juergen Gross (16):
xen: sync with xen headers
xen: save linear p2m list address in shared info structure
xen: don't build mfn tree if tools don't need it
xen: eliminate scalability issues f
sed at all, just delete it.
The only define left is P2M_PER_PAGE which is moved to page.h as well.
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/xen/page.h | 6 --
arch/x86/xen/p2m.c | 6 +-
arch/x86/xen/p2m.h | 15 ---
arch/x86/x
: Juergen Gross
---
arch/x86/xen/enlighten.c | 1 +
arch/x86/xen/mmu.c | 11 +++
arch/x86/xen/xen-ops.h | 1 +
3 files changed, 13 insertions(+)
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 46957ea..a29bcdb 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch
Check whether the page tables built by the domain builder are at
memory addresses which are in conflict with the target memory map.
If this is the case just panic instead of running into problems
later.
Signed-off-by: Juergen Gross
---
arch/x86/xen/mmu.c | 19 ---
arch/x86
This requires to memblock_reserve() the
start_info page on it's own.
Signed-off-by: Juergen Gross
---
arch/x86/xen/mmu.c | 234 +
arch/x86/xen/setup.c | 51 +--
arch/x86/xen/xen-ops.h | 3 +
3 files changed, 247 insertions(+), 41
the domain limit is returned to the hypervisor instead of
being identity mapped, which was wrong anyway.
The kernel configuration parameter to specify the maximum size of a
domain can be deleted, as it is not relevant any more.
Signed-off-by: Juergen Gross
---
Documentation/kernel-parameter
Check whether the initrd is placed at a location which is conflicting
with the target E820 map. If this is the case relocate it to a new
area unused up to now and compliant to the E820 map.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/setup.c | 51
Checks whether the pre-allocated memory of the loaded kernel is in
conflict with the target memory map. If this is the case, just panic
instead of run into problems later, as there is nothing we can do
to repair this situation.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch
to be done in any case.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/setup.c | 34 ++
arch/x86/xen/xen-ops.h | 1 +
2 files changed, 35 insertions(+)
diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index 99ef82c..973d294 1
of the p2m list. Reading the
generation count the Xen tools can detect changes of the mappings
and re-read the p2m list eventually.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/p2m.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/x86/xen
early_memremap_ro() to provide this read only
mapping.
Signed-off-by: Juergen Gross
---
include/asm-generic/early_ioremap.h | 2 ++
include/asm-generic/fixmap.h| 3 +++
mm/early_ioremap.c | 11 +++
3 files changed, 16 insertions(+)
diff --git a/include/asm-generic
Provide a service routine to check a physical memory area against the
E820 map. The routine will return false if the complete area is RAM
according to the E820 map and true otherwise.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/setup.c | 23
r
being able to boot a Dom0 on a system with more than 512 GB memory.
Signed-off-by: Juergen Gross
Based-on-patch-by: Jan Beulich
---
arch/x86/xen/mmu.c | 126
arch/x86/xen/setup.c| 67 ++---
arch/x86/xen/xen-head.S |
before the memory might be clobbered by
xen_set_identity_and_remap(). This requires to not destroy the Xen
E820 map when the one for the system is being constructed.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 98 +++-
1 file changed, 58
In case the Xen tools indicate they don't need the p2m 3 level tree
as they support the virtual mapped linear p2m list, just omit building
the tree.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/p2m.c | 10 +++---
1 file changed, 7 insertions(+), 3 dele
Instead of using a function local static e820 map in xen_memory_setup()
and calling various functions in the same source with the map as a
parameter use a map directly accessible by all functions in the source.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/setup.c
On 06/08/2015 03:42 PM, David Vrabel wrote:
On 08/06/15 13:06, Juergen Gross wrote:
Support 64 bit pv-domains with more than 512GB of memory.
Tested with 64 bit dom0 on machines with 8GB and 1TB and 32 bit dom0 on a
8GB machine. Conflicts between E820 map and different hypervisor populated
On 05/31/2015 11:48 AM, Borislav Petkov wrote:
From: Borislav Petkov
This way we can pass pat MSR value directly.
No functionality change.
You are breaking the Xen build with that change. pat_init_cache_modes()
is called from arch/x86/xen/enlighten.c as well.
Juergen
Signed-off-by: Bori
please?
Acked-by: Juergen Gross
I'm reading xen's PAT config from MSR_IA32_CR_PAT and handing it down to
pat_init_cache_modes(). That shouldn't change current behavior AFAICT
because pat_init_cache_modes() did it itself before.
Right?
Thanks.
---
Author: Borislav Petkov
Dat
On 06/10/2015 05:25 PM, David Vrabel wrote:
On 08/06/15 13:06, Juergen Gross wrote:
Support 64 bit pv-domains with more than 512GB of memory.
Tested with 64 bit dom0 on machines with 8GB and 1TB and 32 bit dom0 on a
8GB machine. Conflicts between E820 map and different hypervisor populated
On 21/05/18 09:39, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Building for a 32-bit target results in warnings from casting
> between a 32-bit pointer and a 64-bit integer. Fix the warnings
> by casting those pointers to uintptr_t first.
>
> Signed-off-by: Oleksandr Andru
On 23/05/18 12:00, Oleksandr Andrushchenko wrote:
> On 05/23/2018 12:19 PM, Juergen Gross wrote:
>> On 21/05/18 09:39, Oleksandr Andrushchenko wrote:
>>> From: Oleksandr Andrushchenko
>>>
>>> Building for a 32-bit target results in warnings from casting
>&
ned-off-by: Oleksandr Andrushchenko
Reviewed-by: Juergen Gross
Juergen
On 22/05/18 05:54, Boris Ostrovsky wrote:
> We are making calls to C code (e.g. xen_prepare_pvh()) which may use
> stack canary (stored in GS segment).
>
> Signed-off-by: Boris Ostrovsky
With the clearing of EDX (instead using CDQ) you can add my
Reviewed-by: Juergen Gross
Juergen
xing improper
> reference to __KERNEL_CS)
>
> Signed-off-by: Boris Ostrovsky
Reviewed-by: Juergen Gross
Juergen
d support for MSI message
>>>>> groups")
>>>>> Reported-by: Hooman Mirhadi
>>>>> CC:
>>>>> CC: Roger Pau Monné
>>>>> CC: Boris Ostrovsky
>>>>> CC: Eduardo Valentin
>>>>> CC: Juergen Gross
On 28/02/18 13:23, Jason Andryuk wrote:
> A toolstack may delete the vif frontend and backend xenstore entries
> while xen-netfront is in the removal code path. In that case, the
> checks for xenbus_read_driver_state would return XenbusStateUnknown, and
> xennet_remove would hang indefinitely. Th
On 28/02/18 10:19, Roger Pau Monne wrote:
> Current cleanup in the error path of xen_bind_pirq_msi_to_irq is
> wrong. First of all there's an off-by-one in the cleanup loop, which
> can lead to unbinding wrong IRQs.
>
> Secondly IRQs not bound won't be freed, thus leaking IRQ numbers.
>
> Note th
On 28/02/18 22:07, Konrad Rzeszutek Wilk wrote:
> On Wed, Feb 28, 2018 at 10:27:57AM -0800, Maran Wilson wrote:
>> In order to pave the way for hypervisors other then Xen to use the PVH
>> entry point for VMs, we need to factor the PVH entry code into Xen specific
>> and hypervisor agnostic compone
On 28/02/18 22:35, Paolo Bonzini wrote:
> On 28/02/2018 22:08, Konrad Rzeszutek Wilk wrote:
>> +obj-$(CONFIG_XEN_PVH) += pvh.o
>> +obj-$(CONFIG_XEN_PVH) += pvh-head.o
>> +
>
> Probably a better place for these would be
> arch/x86/platform/pvh/{enlighten.c,head.S}. (Just because there are no
> .c
umentation/devicetree/bindings/jailhouse.txt | 8
> arch/x86/include/asm/jailhouse_para.h | 2 +-
> include/linux/hypervisor.h | 17 +++--
I'd appreciate if you'd Cc: the maintainers of the touched files...
Reviewed-by: Juergen Gross
Juergen
On 01/03/18 03:05, Stefano Stabellini wrote:
> We are using test_and_* operations on the status and flag fields of
> struct sock_mapping. However, these functions require the operand to be
> 64-bit aligned on arm64. Currently, only status is 64-bit aligned.
>
> Make status and flags explicitly 64-
g option for PVH entry that can be enabled
> independently from CONFIG_XEN.
>
> Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
Juergen
ff-by: Maran Wilson
Reviewed-by: Juergen Gross
Juergen
> Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
Juergen
On 28/02/18 19:28, 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
> would allow KVM guests to
ing KVM
> guests.
>
> Signed-off-by: Maran Wilson
Reviewed-by: Juergen Gross
Juergen
On 24/04/18 22:35, Dongwon Kim wrote:
> Had a meeting with Daniel and talked about bringing out generic
> part of hyper-dmabuf to the userspace, which means we most likely
> reuse IOCTLs defined in xen-zcopy for our use-case if we follow
> his suggestion.
>
> So assuming we use these IOCTLs as the
rash kexec image will never be actually used.
>
> Signed-off-by: Petr Tesarik
Reviewed-by: Juergen Gross
Juergen
On 25/04/2019 09:22, Thomas Gleixner wrote:
> On Thu, 25 Apr 2019, Ingo Molnar wrote:
>>> +# else
>>> + .irq_restore_fl = { 0x50, 0x9d }, // push %eax; popf
>>> + .mmu_write_cr3 = { 0x0f, 0x22, 0xd8 }, // mov %eax, %cr3
>>> + .cpu_iret = { 0xcf },
On 25/04/2019 12:57, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
>> On Thu, Apr 25, 2019 at 11:50:39AM +0200, Ingo Molnar wrote:
>>>
>>> * Peter Zijlstra wrote:
>>>
On Thu, Apr 25, 2019 at 11:17:17AM +0200, Ingo Molnar wrote:
> It basically means that we silently won't do any patc
301 - 400 of 2347 matches
Mail list logo
