aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStewart Smith <stewart@linux.vnet.ibm.com>2016-04-27 07:49:05 +1000
committerStewart Smith <stewart@linux.vnet.ibm.com>2016-04-27 07:49:05 +1000
commitd729ddbfd8cb7b5dc60f336bf7208214c96a3233 (patch)
tree2985145a2d7cf359f8e9d4cb6d0aa2cebc4eeca8
parentd597168a0ea6958955a2a2fc845354059fd057c2 (diff)
parentc8bea6e01608f77550ef686bb7359094311de810 (diff)
downloadskiboot-d729ddbfd8cb7b5dc60f336bf7208214c96a3233.zip
skiboot-d729ddbfd8cb7b5dc60f336bf7208214c96a3233.tar.gz
skiboot-d729ddbfd8cb7b5dc60f336bf7208214c96a3233.tar.bz2
Merge branch 'skiboot-5.1.x' into skiboot-5.2.x
Merge PHB3 race fix
-rw-r--r--hw/fsp/fsp-ipmi.c16
-rw-r--r--hw/phb3.c66
-rw-r--r--include/errorlog.h2
3 files changed, 70 insertions, 14 deletions
diff --git a/hw/fsp/fsp-ipmi.c b/hw/fsp/fsp-ipmi.c
index 750d144..f803f17 100644
--- a/hw/fsp/fsp-ipmi.c
+++ b/hw/fsp/fsp-ipmi.c
@@ -50,6 +50,10 @@ DEFINE_LOG_ENTRY(OPAL_RC_IPMI_RESP, OPAL_PLATFORM_ERR_EVT, OPAL_IPMI,
OPAL_PLATFORM_FIRMWARE, OPAL_PREDICTIVE_ERR_GENERAL,
OPAL_NA);
+DEFINE_LOG_ENTRY(OPAL_RC_IPMI_DMA_ERROR_RESP, OPAL_PLATFORM_ERR_EVT, OPAL_IPMI,
+ OPAL_PLATFORM_FIRMWARE, OPAL_INFO,
+ OPAL_NA);
+
struct fsp_ipmi_msg {
struct list_node link;
struct ipmi_msg ipmi_msg;
@@ -281,13 +285,19 @@ static bool fsp_ipmi_read_response(struct fsp_msg *msg)
assert(msg->data.words[1] == PSI_DMA_PLAT_RESP_BUF);
if (status != FSP_STATUS_SUCCESS) {
- log_simple_error(&e_info(OPAL_RC_IPMI_RESP), "IPMI: Response "
- "with bad status:0x%02x\n", status);
+ if(status == FSP_STATUS_DMA_ERROR)
+ log_simple_error(&e_info(OPAL_RC_IPMI_DMA_ERROR_RESP), "IPMI: Received "
+ "DMA ERROR response from FSP, this may be due to FSP "
+ "is in termination state:0x%02x\n", status);
+ else
+ log_simple_error(&e_info(OPAL_RC_IPMI_RESP), "IPMI: FSP response "
+ "received with bad status:0x%02x\n", status);
+
fsp_ipmi_cmd_done(ipmi_msg->cmd,
IPMI_NETFN_RETURN_CODE(ipmi_msg->netfn),
IPMI_ERR_UNSPECIFIED);
return fsp_ipmi_send_response(FSP_RSP_PLAT_DATA |
- FSP_STATUS_GENERIC_ERROR);
+ FSP_STATUS_SUCCESS);
}
/* KCS response message format */
diff --git a/hw/phb3.c b/hw/phb3.c
index adff5bc..c5c6fe3 100644
--- a/hw/phb3.c
+++ b/hw/phb3.c
@@ -1185,7 +1185,7 @@ static int64_t phb3_pci_msi_eoi(struct phb *phb,
struct phb3 *p = phb_to_phb3(phb);
uint32_t ive_num = PHB3_IRQ_NUM(hwirq);
uint64_t ive, ivc;
- uint8_t *p_byte, gp, gen;
+ uint8_t *p_byte, gp, gen, newgen;
/* OS might not configure IVT yet */
if (!p->tbl_ivt)
@@ -1197,16 +1197,40 @@ static int64_t phb3_pci_msi_eoi(struct phb *phb,
/* Read generation and P */
gp = *p_byte;
- gen = gp >> 1;
+ gen = (gp >> 1) & 3;
+ newgen = (gen + 1) & 3;
/* Increment generation count and clear P */
- *p_byte = ((gen + 1) << 1) & 0x7;
+ *p_byte = newgen << 1;
+
+ /* If at this point:
+ * - the IVC is invalid (due to high IRQ load) and
+ * - we get a new interrupt on this hwirq.
+ * Due to the new interrupt, the IVC will fetch from the IVT.
+ * This IVC reload will result in P set and gen=n+1. This
+ * interrupt may not actually be delievered at this point
+ * though.
+ *
+ * Software will then try to clear P in the IVC (out_be64
+ * below). This could cause an interrupt to be lost because P
+ * is cleared in the IVC without the new interrupt being
+ * delivered.
+ *
+ * To avoid this race, we increment the generation count in
+ * the IVT when we clear P. When software writes the IVC with
+ * P cleared but with gen=n, the IVC won't actually clear P
+ * becuase gen doesn't match what it just cached from the IVT.
+ * Hence we don't lose P being set.
+ */
- /* Update the IVC with a match against the old gen count */
+ /* Update the P bit in the IVC is gen count matches */
ivc = SETFIELD(PHB_IVC_UPDATE_SID, 0ul, ive_num) |
PHB_IVC_UPDATE_ENABLE_P |
PHB_IVC_UPDATE_ENABLE_GEN |
- SETFIELD(PHB_IVC_UPDATE_GEN_MATCH, 0ul, gen);
+ PHB_IVC_UPDATE_ENABLE_CON |
+ SETFIELD(PHB_IVC_UPDATE_GEN_MATCH, 0ul, gen) |
+ SETFIELD(PHB_IVC_UPDATE_GEN, 0ul, newgen);
+ /* out_be64 has a sync to order with the IVT update above */
out_be64(p->regs + PHB_IVC_UPDATE, ivc);
/* Handle Q bit */
@@ -1674,7 +1698,7 @@ static int64_t phb3_msi_set_xive(void *data,
{
struct phb3 *p = data;
uint32_t chip, index;
- uint64_t *cache, ive_num, data64, m_server, m_prio;
+ uint64_t *cache, ive_num, data64, m_server, m_prio, ivc;
uint32_t *ive;
chip = p8_irq_to_chip(isn);
@@ -1719,14 +1743,34 @@ static int64_t phb3_msi_set_xive(void *data,
*ive = (m_server << 8) | m_prio;
out_be64(p->regs + PHB_IVC_UPDATE, data64);
- /*
- * Handle Q bit if we're going to enable the interrupt.
- * The OS should make sure the interrupt handler has
- * been installed already.
- */
if (prio != 0xff) {
+ /*
+ * Handle Q bit if we're going to enable the
+ * interrupt. The OS should make sure the interrupt
+ * handler has been installed already.
+ */
if (phb3_pci_msi_check_q(p, ive_num))
phb3_pci_msi_flush_ive(p, ive_num);
+ } else {
+ /* Read from random PHB reg to force flush */
+ in_be64(p->regs + PHB_IVC_UPDATE);
+
+ /* Order with subsequent read of Q */
+ sync();
+
+ /* Clear P, Q and Gen, preserve PE# */
+ ive[1] &= 0x0000ffff;
+
+ /*
+ * Update the IVC with a match against the old gen
+ * count. No need to worry about racing with P being
+ * set in the cache since IRQ is masked at this point.
+ */
+ ivc = SETFIELD(PHB_IVC_UPDATE_SID, 0ul, ive_num) |
+ PHB_IVC_UPDATE_ENABLE_P |
+ PHB_IVC_UPDATE_ENABLE_Q |
+ PHB_IVC_UPDATE_ENABLE_GEN;
+ out_be64(p->regs + PHB_IVC_UPDATE, ivc);
}
return OPAL_SUCCESS;
diff --git a/include/errorlog.h b/include/errorlog.h
index 33d2de2..ed90dab 100644
--- a/include/errorlog.h
+++ b/include/errorlog.h
@@ -322,6 +322,8 @@ enum opal_reasoncode {
/* IPMI */
OPAL_RC_IPMI_REQ = OPAL_IP | 0x10,
OPAL_RC_IPMI_RESP = OPAL_IP | 0x11,
+ OPAL_RC_IPMI_DMA_ERROR_RESP
+ = OPAL_IP | 0x12,
/* Platform error */
OPAL_RC_ABNORMAL_REBOOT = OPAL_CE | 0x10,