Same code is already in allocate_and_map_msi_pirq()
-v2: remove unnecessory comment (Suggested by Jan and Roger)
added 'x86/physdev:' tag to commit subject (Suggested by Konrad)
Signed-off-by: Zhenzhong Duan <zhenzhong.d...@oracle.com>
Reviewed-by: Joe Jin <joe@oracle.com&
Same code is already in allocate_and_map_msi_pirq()
Signed-off-by: Zhenzhong Duan <zhenzhong.d...@oracle.com>
---
xen/arch/x86/physdev.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/xen/arch/x86/physdev.c b/xen/arch/x86/physdev.c
index 0eb4097..aa02d18
As xen_cpuhp_setup is called by PV and PVHVM, the name of "x86/xen/hvm_guest"
is confusing.
Signed-off-by: Zhenzhong Duan <zhenzhong.d...@oracle.com>
---
arch/x86/xen/enlighten.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/xen/enlighten.
() in DEBUG mode is also removed.
-v2: add comment about XEN alignment from Juergen.
References: https://lists.xen.org/archives/html/xen-devel/2012-07/msg01562.html
Signed-off-by: Zhenzhong Duan <zhenzhong.d...@oracle.com>
---
arch/x86/xen/mmu_pv.c | 13 -
1 files chan
() in DEBUG mode is also removed.
References: https://lists.xen.org/archives/html/xen-devel/2012-07/msg01562.html
Signed-off-by: Zhenzhong Duan <zhenzhong.d...@oracle.com>
---
arch/x86/xen/mmu_pv.c | 12 +++-
1 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/arch/x
sn't necessarily mean that I object to changing the behaviour
of the python xc module in still-supported Xen releases. But I'm not
sure the reasoning behind the behaviour of the libxl bitmap functions
applies to the Python interface.
Zhenzhong Duan, are you using an out-of-tree copy of xm and xen
On 2016/4/12 11:35, Zhenzhong Duan wrote:
On 2016/4/11 19:27, Wei Liu wrote:
On Mon, Apr 11, 2016 at 09:42:57AM +0800, Zhenzhong Duan wrote:
It's tool's duty to pass a correct cpumap to XEN. On a host with
less than
64
CPUS, it just shows below error.
[root@localhost /]# xm vcpu-pin 3 all
在 2016/4/11 19:27, Wei Liu 写道:
On Mon, Apr 11, 2016 at 09:42:57AM +0800, Zhenzhong Duan wrote:
It's tool's duty to pass a correct cpumap to XEN. On a host with less than
64
CPUS, it just shows below error.
[root@localhost /]# xm vcpu-pin 3 all all
Error: Cannot pin vcpu: 0 to cpu: [0, 1, 2, 3
, 29, 30, 31,
32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50,
51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63] - (22, 'Invalid
argument')
The fix make it same as in xl code.
Signed-off-by: Zhenzhong Duan <zhenzhong.d...@oracle.com>
---
tools/python/xen/lowlevel/x
在 2015/1/16 0:16, Don Slutz 写道:
On 01/15/15 05:20, Ian Campbell wrote:
On Thu, 2015-01-15 at 11:31 +0800, Zhenzhong Duan wrote:
Hi Maintainers,
We are facing issue collecting coredump using the xm dump mechanism
in Dom0.
We face couple of such issues daily, where the VMs panic s and the SA
Hi Maintainers,
We are facing issue collecting coredump using the xm dump mechanism in
Dom0.
We face couple of such issues daily, where the VMs panic s and the SA
team is supposed to collect the core.
The actual problem is that where the VMs are having huge RAM like 32+ GB
RAMs dumping the
11 matches
Mail list logo
