Hi Alex.
If CONFIG_FLATMEM=y is enabled(xenLinux default is so),
it seems sane that the total is about 5GB.
Do disabling CONFIG_FLATMEM=n and enabling CONFIG_DISCONTIGMEM=y
(or CONFIG_SPARSEMEM=y) make difference?
And I also noticed that xenLinux default config disables
CONFIG_VIRTUAL_MEM_MAP=n.
tlbflush_clock
This patch introduces xen compile time option, xen_ia64_tlbflush_clock=y.
--
yamahata
# HG changeset patch
# User [EMAIL PROTECTED]
# Date 1160981399 -32400
# Node ID 0b16566e129874f29708d8b5c40c8542649a7bcb
# Parent fcd746cf4647e06b8e88e620c29610ba43e3ad7c
tlbflush_clock
This
micro optimize __domain_flush_vtlb_track_entry.
try to use local purge instead of global purge when possible.
--
yamahata
# HG changeset patch
# User [EMAIL PROTECTED]
# Date 1160981797 -32400
# Node ID a8882084d080692b970edb835af909cbe8aa5f96
# Parent 0b16566e129874f29708d8b5c40c8542649a7bcb
Hi, Tristan
Thank you for your comments.
I am wondering the code of arch/i386/pci/pcifront.c and irq-xen.c for x86.
(IA64 does not have it)
The [EMAIL PROTECTED]/i386/pci/irq-xen.c is pci_sal_read/write for IA64.
(DomU/VTI cannot access PCI configuration)
Thanks
Atsushi SAKAI
Le Vendredi
Le Lundi 16 Octobre 2006 11:57, Atsushi SAKAI a écrit :
Hi, Tristan
Thank you for your comments.
I am wondering the code of arch/i386/pci/pcifront.c and irq-xen.c for x86.
(IA64 does not have it)
The [EMAIL PROTECTED]/i386/pci/irq-xen.c is pci_sal_read/write
for IA64. (DomU/VTI cannot
Hi Alex,
Could you apply an attached patch?
There is no difference between Anthony's patch and my old one
because all vcpus are stopped completely.
Thanks,
Kouya
Signed-off-by: Kouya SHIMURA [EMAIL PROTECTED]
Signed-off-by: Anthony Xu [EMAIL PROTECTED]
diff -r fcd746cf4647
Hi all,
We've ported PV-on-HVM drivers for IPF. But I think that
only few tries it. Thus, I try to describe to use it.
And I attach several patches about PV-on-HVM.
+ fix-warning.patch
- warning fix for HVM PV driver
+ notsafe-comment.patch
- add not-SMP-safe comment
On Mon, 2006-10-16 at 15:06 +0900, Isaku Yamahata wrote:
Hi Alex.
If CONFIG_FLATMEM=y is enabled(xenLinux default is so),
it seems sane that the total is about 5GB.
Do disabling CONFIG_FLATMEM=n and enabling CONFIG_DISCONTIGMEM=y
(or CONFIG_SPARSEMEM=y) make difference?
And I also noticed
On Tue, 2006-10-10 at 20:02 +0900, SUZUKI Kazuhiro wrote:
+#ifdef XEN
+ // 5. VHPT
+#if VHPT_ENABLED
+ mov r24=VHPT_SIZE_LOG22
+ movl r22=VHPT_ADDR
+ mov r21=IA64_TR_VHPT
...
+#ifdef XEN
+ // 5. VHPT
+#if VHPT_ENABLED
+ mov r24=VHPT_SIZE_LOG22
+ movl
This patch adds buffer IO mechanism for Xen/VTi domain. It catches up
with Xen/IA32 side. Current implementation can accelerate Windows
geust's dense IO operations @ boot time.
I divided it into two parts. One is only related to Qemu, and the other
one is main body.
Signed-off-by : Zhang xiantao
Main part.
Signed-off-by: Zhang xiantao [EMAIL PROTECTED]
Thanks Best Regards
-Xiantao
OTC,Intel Corporation
buffer_io.patch
Description: buffer_io.patch
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
Hi all,
When I tried to create VTI in kernel-xen-2.6.18-1.2784.fc6, I met another
strange issue.
It would report disk image does not exist. If I not giving disk option, it
will report guest firmware does not exist (kernel). But they are all in the
path. :(
Did you meet it? My xen is
Sorry to send to the wrong mailling list. :(
I should send it to fedora-ia64-xen.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
Sent: 2006年10月17日 11:40
To: xen-ia64-devel@lists.xensource.com
Subject:
13 matches
Mail list logo