From: Luca Coelho <luca@coelho.fi>
To: Michal Hocko <mhocko@kernel.org>
Cc: kvalo@codeaurora.org, johannes@sipsolutions.net,
emmanuel.grumbach@intel.com, linuxwifi@intel.com,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
Shahar S Matityahu <shahar.s.matityahu@intel.com>
Subject: Re: [PATCH] iwlwifi: don't panic in error path on non-msix systems
Date: Wed, 17 Apr 2019 13:17:10 +0300 [thread overview]
Message-ID: <3c1cb224613ac2cc3b20bfcf0c47e0df584c4e31.camel@coelho.fi> (raw)
In-Reply-To: <20190417101102.GA5878@dhcp22.suse.cz>
On Wed, 2019-04-17 at 12:11 +0200, Michal Hocko wrote:
> Hi,
> which tree is this supposed to be applied on? It doesn't do apply on
> top
> of v5.1-rc4-3-gfd008d1a7a20. iwl_trans_pcie_sync_nmi doesn't exist in
> drivers/net/wireless/intel/iwlwifi/pcie/trans.c. iwl_trans_sync_nmi
> looks pretty similar. My patch massaging ended up with this. Please
> double check. It compiles and even boots.
Ah, sorry, I didn't mention that that patch was supposed to apply on
top of wireless-drivers-next, which is on its way to v5.2. We have
other patches touching this function there, thus the conflict.
> diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
> b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
> index fe8269d023de..1f3969e2bcac 100644
> --- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
> +++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
> @@ -3639,20 +3639,27 @@ struct iwl_trans *iwl_trans_pcie_alloc(struct
> pci_dev *pdev,
>
> void iwl_trans_sync_nmi(struct iwl_trans *trans)
> {
> + struct iwl_trans_pcie *trans_pcie =
> IWL_TRANS_GET_PCIE_TRANS(trans);
> unsigned long timeout = jiffies + IWL_TRANS_NMI_TIMEOUT;
> + u32 inta_addr, sw_err_bit;
> +
> + if (trans_pcie->msix_enabled) {
> + inta_addr = CSR_MSIX_HW_INT_CAUSES_AD;
> + sw_err_bit = MSIX_HW_INT_CAUSES_REG_SW_ERR;
> + } else {
> + inta_addr = CSR_INT;
> + sw_err_bit = CSR_INT_BIT_SW_ERR;
> + }
>
> iwl_disable_interrupts(trans);
> iwl_force_nmi(trans);
> while (time_after(timeout, jiffies)) {
> - u32 inta_hw = iwl_read32(trans,
> - CSR_MSIX_HW_INT_CAUSES_AD);
> + u32 inta_hw = iwl_read32(trans, inta_addr);
>
> /* Error detected by uCode */
> - if (inta_hw & MSIX_HW_INT_CAUSES_REG_SW_ERR) {
> + if (inta_hw & sw_err_bit) {
> /* Clear causes register */
> - iwl_write32(trans, CSR_MSIX_HW_INT_CAUSES_AD,
> - inta_hw &
> - MSIX_HW_INT_CAUSES_REG_SW_ERR);
> + iwl_write32(trans, inta_addr, inta_hw &
> sw_err_bit);
> break;
> }
This looks good! So it fixed the problem you were having now?
--
Cheers,
Luca.
next prev parent reply other threads:[~2019-04-17 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 21:07 iwlwifi: BUG: unable to handle kernel paging request at ffffc90000e1c808 Michal Hocko
2019-04-12 9:49 ` Michal Hocko
2019-04-16 18:36 ` Michal Hocko
2019-04-17 7:33 ` Luca Coelho
2019-04-17 7:35 ` [PATCH] iwlwifi: don't panic in error path on non-msix systems Luca Coelho
2019-04-17 10:11 ` Michal Hocko
2019-04-17 10:17 ` Luca Coelho [this message]
2019-04-17 10:53 ` Luca Coelho
2019-04-17 10:59 ` Michal Hocko
2019-04-22 18:07 ` Michal Hocko
2019-04-22 23:56 ` Kirtika Ruchandani
2019-04-23 2:34 ` Kirtika Ruchandani
2019-04-23 13:27 ` Luca Coelho
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=3c1cb224613ac2cc3b20bfcf0c47e0df584c4e31.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=mhocko@kernel.org \
--cc=shahar.s.matityahu@intel.com \
/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