[Xen-ia64-devel][PATCH] Enable SMP on VTI domain.
This patch enables SMP on VTI domain. I can boot VTI domain with 8 vcpus on my box. There are only 2 slots (2 core 2 thread each) on my box. :-) Signed-off-by: Anthony Xu [EMAIL PROTECTED] Thanks, -Anthony vti_smp_0607.patch Description: vti_smp_0607.patch ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] [PATCH] VP model doesn't pass the whole ACPI table to dom0
Hi Alex, Please take a look at attached log messages of PRIMEQUEST. (I slightly changed the output format (MB-KB) in [EMAIL PROTECTED]) The following line looks bizarre. (XEN) domain mem: type= 6, attr=0x8009, range=[0x7fcbe000-0x7fcbe000) (0KB) type=6 means EFI_RUNTIME_SERVICES_DATA. ACPI tables start at 0x7fcbe000 and it is correct. But its size is 0! Though PRIMEQUEST might violate the EFI spec, I wish that dom0 can read the same physical memory as the linux do. Anyway, could you apply 10250.patch? It solves a obvious bug. I attached it again. FYI. As for linux, the system which has broken EFI memory map seems to be rescued by acpi_os_map_memory function in drivers/acpi/osl.c. Thanks, Kouya Alex Williamson writes: On Tue, 2006-06-06 at 21:09 +0900, Kouya SHIMURA wrote: Hi Alex, I looked into the code about reference of ACPI table. Single instance seems to be OK but I can't guarantee it. So I wrote ACPI tables walking code. The code isn't a big deal. How about this? Attached patch is work around and not fully tested yet. (It works on Tiger and PRIMEQUEST) Hi Kouya, Let's back up one step. Why doesn't the PRIMEQUEST report these tables as type EFI_ACPI_RECLAIM_MEMORY? Section 2.3.3 of the EFI spec (v1.10) indicates that ACPI tables loaded at boot time must be declared as this type in the MDT. If it did, then dom_fw_dom0_passthrough() would do this for us much more cleanly. In fact, the ASSIGN_DOMAIN_MACH_PAGE calls this patch removes should already be redundant because of the passthrough setup. Could you post the relevant section of the MDT for this system and describe the mapping that we're not setting up? Thanks, Alex -- Alex Williamson HP Open Source Linux Org. PRIMEQUEST.dmesg Description: Binary data 10250.patch Description: Binary data ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel][PATCH] Put guest physical translation into VHPT
Signed-off-by: Anthony Xu [EMAIL PROTECTED] Thanks, -Anthony physical_vhpt.patch Description: physical_vhpt.patch ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Problems booting domU
I`m trying to boot my domU and occurrs the error below: debian-ia64:~# xm create -c /etc/xen/vm01-config.sxp ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) Using config file /etc/xen/vm01-config.sxp. Error: (2, 'No such file or directory') My domU configuration: name=vm01 kernel=/boot/efi/efi/debian/vmlinux-2.6.16.13-xenU root=/dev/sda7 memory=128 disk=['file:/vserver/images/vm01.img,sda7,w','file:/vserver/images/vm01-swap.img,sda5,w'] vif=[''] dhcp=off ip=192.168.0.101 netmask=255.255.255.0 gateway=192.168.0.1 hostname=vm01.example.com extra=3 ps: debian-ia64:/home/peso/xen-ia64-unstable.hg/linux-2.6.16.13-xenU# cp vmlinux /boot/efi/efi/debian/vmlinux-2.6.16.13-xenU (I copied vmlinux (of xen-ia64-unstable.hg/linux-2.6.16.13-xenU to my EFI) Thanks! ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] [PATCH] sparse tree cleanups
On Wed, 2006-06-07 at 15:08 +0900, Akio Takebe wrote: Hi, Alex I agree your suggestion. But your patch use ifdef CONFIG_XEN. You say we use simple is_running_on_xen() checks, aren't you? Is this mistake? or do I mis-understand? I want to clean up mm/memory.c. (This work is for cleanup fedora-xen's warning.) I should use is_running_on_xen() in mm/memory.c, shouldn't I? Hi Akio, Without seeing the changes, it's hard to say. What I mean by simple checks are that it cannot call functions or declare variables that are only defined in CONFIG_XEN code. It's minor cleanup that you may not be able to use. Thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel][PATCH] Put guest physical translation into VHPT
On Wed, 2006-06-07 at 16:34 +0800, Xu, Anthony wrote:
diff -r 4da439f89524 xen/arch/ia64/vmx/vmx_phy_mode.c
--- a/xen/arch/ia64/vmx/vmx_phy_mode.c Wed Jun 07 15:25:31 2006 +0800
+++ b/xen/arch/ia64/vmx/vmx_phy_mode.c Wed Jun 07 16:03:12 2006 +0800
@@ -132,6 +132,7 @@ physical_itlb_miss(VCPU *vcpu, u64 vadr)
* vec=1, itlb miss
* vec=2, dtlb miss
*/
+ /*
void
physical_tlb_miss(VCPU *vcpu, u64 vadr, u64 vec)
{
Hi Anthony,
Please don't comment out code like this to disable it. It's easy to
miss when reading the code and easy to break by adding a comment to the
function. I would prefer that we delete dead code when it's replaced
(that's what revision control is for), but if you must keep it, at least
#if it out. If you could include removal of the commented out function
right above this addition in your next patch, I'd appreciate it.
Thanks,
Alex
--
Alex Williamson HP Open Source Linux Org.
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] Problems booting domU
Hi, Rodrigo Please try the below. # xm create -c -f /etc/xen/vm01-config.sxp Best Regards, Akio Takebe I`m trying to boot my domU and occurrs the error below: debian-ia64:~# xm create -c /etc/xen/vm01-config.sxp ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) Using config file /etc/xen/vm01-config.sxp. Error: (2, 'No such file or directory') ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] Problems booting domU
Hi, Rodrigo Please try it as root user. And you may need to confirm that there is /etc/xen/vm01-config.sxp. Best Regards, Akio Takebe Hi, Rodrigo Please try the below. # xm create -c -f /etc/xen/vm01-config.sxp Best Regards, Akio Takebe I`m trying to boot my domU and occurrs the error below: debian-ia64:~# xm create -c /etc/xen/vm01-config.sxp ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) Using config file /etc/xen/vm01-config.sxp. Error: (2, 'No such file or directory') ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] [PATCH] VP model doesn't pass the whole ACPI table to dom0
On Wed, 2006-06-07 at 09:05 -0600, Alex Williamson wrote:
Hi Kouya,
Yes, I do too. Does the PRIMEQUEST have a memmap command from the
EFI shell that reports the original MDT as reported by firmware? I
notice this range reports both WB and UC attributes. I wonder if the
zero size is a result of the efi trim_top/trim_bottom calls zero-ing out
that range to prevent attribute aliasing. On my system the ACPI reclaim
memory is only reported with the UC attribute and therefore does not get
trimmed. If this is the case, the solution might be to have the
trimming functions remove the WB attribute instead of reducing the range
to zero. I'd certainly prefer to add that kind of special case than to
walk the ACPI tables by hand. Thanks,
Hi Kouya,
Here's a patch that will remove the WB attribute instead of trimming
ranges that support both WB UC. It's untested, but let me know if
this solves the problem on PRIMEQUEST. Thanks,
Alex
--
Alex Williamson HP Open Source Linux Org.
diff -r 4e78528e3480 xen/arch/ia64/linux-xen/efi.c
--- a/xen/arch/ia64/linux-xen/efi.c Tue Jun 06 09:11:25 2006 -0600
+++ b/xen/arch/ia64/linux-xen/efi.c Wed Jun 07 09:36:51 2006 -0600
@@ -273,8 +273,13 @@ trim_bottom (efi_memory_desc_t *md, u64
* descriptor list to become unsorted. In such a case, md-num_pages will be
* zero, so the Right Thing will happen.
*/
- md-phys_addr += num_skipped_pages EFI_PAGE_SHIFT;
- md-num_pages -= num_skipped_pages;
+ if (!(md-attribute EFI_MEMORY_UC)) {
+ md-phys_addr += num_skipped_pages EFI_PAGE_SHIFT;
+ md-num_pages -= num_skipped_pages;
+ } else {
+ /* If range supports multiple attributes, turn off WB */
+ md-attribute = ~EFI_MEMORY_WB;
+ }
}
static void
@@ -296,7 +301,10 @@ trim_top (efi_memory_desc_t *md, u64 end
at 0x%lx\n, __FUNCTION__,
(num_dropped_pages EFI_PAGE_SHIFT) 10,
md-phys_addr, end_addr);
- md-num_pages -= num_dropped_pages;
+ if (!(md-attribute EFI_MEMORY_UC))
+ md-num_pages -= num_dropped_pages;
+ else
+ md-attribute = ~EFI_MEMORY_WB;
}
/*
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
