From: minyard@acm.org
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Cc: Corey Minyard <cminyard@mvista.com>
Subject: [Qemu-devel] [PATCH v5 16/16] ipmi: Add a force off function
Date: Thu, 17 Dec 2015 12:50:19 -0600 [thread overview]
Message-ID: <1450378219-25799-17-git-send-email-minyard@acm.org> (raw)
In-Reply-To: <1450378219-25799-1-git-send-email-minyard@acm.org>
From: Corey Minyard <cminyard@mvista.com>
Allow the IPMI interface to request a forced power off.
Signed-off-by: Corey Minyard <cminyard@mvista.com>
---
hw/ipmi/ipmi_bmc_extern.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/hw/ipmi/ipmi_bmc_extern.c b/hw/ipmi/ipmi_bmc_extern.c
index 05b9121..56073b3 100644
--- a/hw/ipmi/ipmi_bmc_extern.c
+++ b/hw/ipmi/ipmi_bmc_extern.c
@@ -30,6 +30,7 @@
#include <stdint.h>
#include "qemu/timer.h"
#include "sysemu/char.h"
+#include "sysemu/sysemu.h"
#include "hw/ipmi/ipmi.h"
#define VM_MSG_CHAR 0xA0 /* Marks end of message */
@@ -52,6 +53,7 @@
#define VM_CAPABILITIES_IRQ 0x04
#define VM_CAPABILITIES_NMI 0x08
#define VM_CAPABILITIES_ATTN 0x10
+#define VM_CMD_FORCEOFF 0x09
#define TYPE_IPMI_BMC_EXTERN "ipmi-bmc-extern"
#define IPMI_BMC_EXTERN(obj) OBJECT_CHECK(IPMIBmcExtern, (obj), \
@@ -268,6 +270,10 @@ static void handle_hw_op(IPMIBmcExtern *ibe, unsigned char hw_op)
case VM_CMD_SEND_NMI:
k->do_hw_op(s, IPMI_SEND_NMI, 0);
break;
+
+ case VM_CMD_FORCEOFF:
+ qemu_system_shutdown_request();
+ break;
}
}
--
2.5.0
prev parent reply other threads:[~2015-12-17 18:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 18:50 [Qemu-devel] [PATCH v5 0/16] Add an IPMI device to QEMU minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 01/16] Add a base IPMI interface minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 02/16] ipmi: Add a local BMC simulation minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 03/16] ipmi: Add an external connection simulation interface minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 04/16] ipmi: Add an ISA KCS low-level interface minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 05/16] ipmi: Add a BT " minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 06/16] ipmi: Add tests minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 07/16] ipmi: Add documentation minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 08/16] ipmi: Add migration capability to the IPMI devices minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 09/16] ipmi: Add a firmware configuration repository minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 10/16] ipmi: Add firmware registration to the ISA interface minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 11/16] smbios: Move table build tools into an include file minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 12/16] pc: Postpone SMBIOS table installation to post machine init minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 13/16] ipmi: Add SMBIOS table entry minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 14/16] acpi: Add IPMI table entries minyard
2015-12-17 18:50 ` [Qemu-devel] [PATCH v5 15/16] bios: Add tests for the IPMI ACPI and SMBIOS entries minyard
2015-12-17 18:50 ` minyard [this message]
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=1450378219-25799-17-git-send-email-minyard@acm.org \
--to=minyard@acm.org \
--cc=cminyard@mvista.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).