From: Alex Williamson <alex.williamson@hp.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
Keir Fraser <keir@xensource.com>
Subject: [PATCH] Enable _OSI(Linux) for Xen HVM domains
Date: Tue, 06 Nov 2007 12:05:06 -0700 [thread overview]
Message-ID: <1194375906.31834.211.camel@bling> (raw)
I'd like to enable _OSI(Linux) for Xen HVM domains. As I understand
it, the main reason for disabling _OSI(Linux) by default is to avoid
dealing with a myriad of systems with broken Linux code paths in their
BIOS (while we know the Windows code path is functional). With fully
virtualized Xen domains, the "BIOS" code is provided from the Xen
project (or separate open source tree in the case on ia64). We can
therefore verify the Linux code path works and we can take advantage of
the _OSI call to make optimization in the hypervisor based on the
guest's response. The patch below enables this feature on both x86 and
ia64 Xen via the existing DMI hook. Thanks,
Alex
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Acked-by: Keir Fraser <keir@xensource.com>
--
diff -r c7f1be4e5832 drivers/acpi/osl.c
--- a/drivers/acpi/osl.c Thu Nov 01 12:09:33 2007 -0700
+++ b/drivers/acpi/osl.c Fri Nov 02 15:30:23 2007 -0700
@@ -1225,6 +1225,14 @@ static struct dmi_system_id acpi_osl_dmi
DMI_MATCH(DMI_BOARD_NAME, "MPAD-MSAE Customer Reference Boards"),
},
},
+ {
+ .callback = dmi_osi_linux,
+ .ident = "Xen HVM domU",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Xen"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "HVM domU"),
+ },
+ },
{}
};
#endif /* CONFIG_DMI */
next reply other threads:[~2007-11-06 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 19:05 Alex Williamson [this message]
2008-01-17 0:44 ` [PATCH] Enable _OSI(Linux) for Xen HVM domains Len Brown
2008-01-17 22:15 ` Alex Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1194375906.31834.211.camel@bling \
--to=alex.williamson@hp.com \
--cc=keir@xensource.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).