# HG changeset patch
# User [EMAIL PROTECTED]
# Date 1185762640 -32400
# Node ID fb5043d15cae94f0686f5ad009d67ff97d0a1c3c
# Parent 4492a0285bae734ee18f6acbb6b3f9c80f153be7
remove xencomm page size limit.
Currently xencomm has page size limit so that a domain with many memory
(e.g. 100GB+) can't
# HG changeset patch
# User [EMAIL PROTECTED]
# Date 1185763112 -32400
# Node ID 9536c4366949dcd4a163d2129e18e319bf6d1ac2
# Parent b0bf9ba32bfe341af07da97d57572659c920fd30
remove xencomm page size limit.
Currently xencomm has page size limit so that a domain with many memory
(e.g. 100GB~) can't
Hi,
Currently dom0 cannot call panic_notifier_list in panic().
This is caused by PAL_HALT called from smp_send_stop().
When dom0 call PAL_HALT, Hypervisor reset system.
So if dom0 panic, we cannot use panic_notifier_list.
Current PAL_HALT of xen is different from ia64 specification.
This patch
Best Regards
Liuqing
From: Yang, Liuqing
Sent: 2007年7月27日 9:28
To: Xu, Anthony; Zhang, Xing Z; You, Yongkang; Yang, Fred
Subject: stress test report for the open guest firmware
Hi,
The stress test of crashme and helltest running parallel for 48 hours
Hi all,
We have done a nightly test and a 48 hours stress test for the new open
guest firmware, only one case failed: SMPWin_SMPVTI_SMPxenU_Co case
failed due to Linux VTI created fail with xenu and windows vti created
at the same time. Error information printed to the Screen is Exit
status: Load
Hi Isaku,
This looks like a good idea, a few questions:
* Is there still a need to keep the CONFIG_XEN_IA64_VDSO_PARAVIRT
sub config option? Would we actually support this not set, or
should we merge it into CONFIG_XEN?
* If I understand correctly, instead of
Hi Isaku,
Should we make the same changes to the common xencomm files?
(xen-ppc-devel CC'd) I don't see why we wouldn't, at least for this
first one. How much memory have you been able to assign to a domain
with theses patches? My only nit on this patch is that the
from/to_ulong variables
On Tue, 2007-07-31 at 17:33 +0900, Akio Takebe wrote:
Hi,
Currently dom0 cannot call panic_notifier_list in panic().
This is caused by PAL_HALT called from smp_send_stop().
When dom0 call PAL_HALT, Hypervisor reset system.
So if dom0 panic, we cannot use panic_notifier_list.
Current
On Tue, Jul 31, 2007 at 09:41:10AM -0600, Alex Williamson wrote:
On Mon, 2007-07-30 at 14:59 +0900, Isaku Yamahata wrote:
This patch introduce set rr0 to rr4 hyperprivop to reduce context switch
overhead.
Linux/ia64 changes region registers from rr0 to rr4 when context switch
so that
Hi there folks,
First posting to this list, so be gentle... The following is a summary
of something I've been poking at for Red Hat Enterprise Linux 5.x (for
some as yet uncertain value of x, but hopefully 1), and I've ported the
changes forward to the xen-ia64-unstable tree. On with the
On Tue, Jul 31, 2007 at 10:25:47AM -0600, Alex Williamson wrote:
This looks like a good idea, a few questions:
* Is there still a need to keep the CONFIG_XEN_IA64_VDSO_PARAVIRT
sub config option? Would we actually support this not set, or
should we merge it into
On Tue, Jul 31, 2007 at 10:43:44PM -0600, Alex Williamson wrote:
+ /* maximum available memory for dom0 */
+ max_dom0_pages = avail_domheap_pages() -
+min(avail_domheap_pages() /
+16UL, 512UL (20 - PAGE_SHIFT)) ;
I assume
12 matches
Mail list logo
