Quoting Dong, Eddie [EMAIL PROTECTED]:
Yes, we met this too yesterday, current Xen/IA64 doesn't check supported
VA address bits # in architecture safe way, it just assume it is 61
bits.
See
http://lists.xensource.com/archives/html/xen-ia64-devel/2006-10/msg00227.html
for a patch. This one
Hi Tristan,
Current EFI memmap doesn't have a entry of ACPI 2.0 Table.
This patch fixes it as follows:
Shell memmap -b
Type StartEnd # Pages Attributes
...
available 000E-000EBFFF 0020 000F
ACPI_recl
Hi, Tristan
Quoting Kouya Shimura [EMAIL PROTECTED]:
Hi Tristan,
Current EFI memmap doesn't have a entry of ACPI 2.0 Table.
{...}
Akio, This is a reason why /proc/acpi/dsdt can't be seen.
Ok. The code you have removed is indeed junk. I so can apply your patch
without Akio's one ?
Yes, I
Quoting Akio Takebe [EMAIL PROTECTED]:
Yes, I also confirmed the memory is not clear at booting EFI.
The memory was cleared by linux kernel
because the region set conventional memory.
Ok, I now understand the issue. Thanks.
Can you apply also the new patch?
Sure.
Tristan.
Hi, Tristan
I cannot make dsdt.c in edk2-sparse/EdkXenPkg/Dxe/XenAcpi.
The patch fix it.
Signed-off-by: Akio Takebe [EMAIL PROTECTED]
Best Regards,
Akio Takebe
fix_make_dsdt_C.patch
Description: Binary data
___
Xen-ia64-devel mailing list
Hi, Tristan
Quoting Akio Takebe [EMAIL PROTECTED]:
Hi, Tristan
I cannot make dsdt.c in edk2-sparse/EdkXenPkg/Dxe/XenAcpi.
The patch fix it.
Well, I am not a big fan of this approach. I'd really prefer each developer
installs its own version of iasl. Maybe the documentation should be
Quoting Akio Takebe [EMAIL PROTECTED]:
Hi, Tristan
I cannot make dsdt.c in edk2-sparse/EdkXenPkg/Dxe/XenAcpi.
The patch fix it.
Well, I am not a big fan of this approach. I'd really prefer each developer
installs its own version of iasl. Maybe the documentation should be improved.
(there
On Wed, Jan 23, 2008 at 05:54:40PM +, Keir Fraser wrote:
On 23/1/08 16:38, Samuel Thibault [EMAIL PROTECTED] wrote:
Keir Fraser, le Wed 23 Jan 2008 16:30:27 +, a écrit :
I don't really want the memory-size parameter back. What if we support
memory hotplug in future (e.g., we could
In addition, It seems that PV domain can use an unimplemented VA address
except xen area.
Ideally xen should check it and reflect the unimplemented address fault
to the guest. But it sounds overkill.
--
Kouya
Isaku Yamahata writes:
On Thu, Jan 24, 2008 at 09:28:39AM +0800, Dong, Eddie wrote:
