[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-ia64-devel][PATCH] optimization for windows
- To: "Alex Williamson" <alex.williamson@xxxxxx>
- From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
- Date: Tue, 8 May 2007 10:55:16 +0800
- Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Mon, 07 May 2007 19:53:37 -0700
- List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
- Thread-index: AceP51ZMjGRpu1juQi6Me9HYYJceCABNAEBw
- Thread-topic: [Xen-ia64-devel][PATCH] optimization for windows
>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>Sent: 2007å5æ6æ 22:03
>To: Xu, Anthony
>Cc: JÃrgen GroÃ; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel][PATCH] optimization for windows
> I've been thinking about ways to detect which OS is running. Having
>Xen guess based on page sizes of regions seems fairly error prone and
>hard to debug if it goes wrong. A configuration option in the domain
>config file is a more manual processes, but should provide a cleaner
>interface into Xen to set guest specific optimizations. At some point
>we might be able to make this automatic if we can hook into the ACPI
>_OSI method in the GFW. I don't know if that would be possible.
>There's also the _OS method, but nearly every OS reports some flavor of
>Windows for that method because it's often the only path through ACPI
>that gets tested. Hopefully the same won't happen to the _OSI
>interface. We'll need to see if upstream is in favor of a guest
>specific optimization flag in the config file or has other suggestions
>about how to accomplish this. Thanks,
That's a good suggestion.
Just talked with ACPI expert near my cubicle :-)
Both __OSI(linux) and __OSI(windows) return true.
__OSI(linux) return false,
__OSI(windows) return true.
So if guest FW checks linux first then checks windows.
Guest FW can tell which OS is running on top of it.
Then Guest FW can tell XEN which OS is running.
I'll try this.
Xen-ia64-devel mailing list