On 06/05/2014 09:18 AM, Kalle Valo wrote:
>> +struct ath10k_tlv_dump_data {
>> + u32 type; /* see ath10k_fw_error_dump_type above */
>> + u32 tlv_len; /* in bytes */
>> + u8 tlv_data[]; /* Pad to 32-bit boundaries as needed. */
>> +} __packed;
>> +
>> +struct ath10k_dump_file_data {
>> + /* Dump file information */
>> + u32 len;
>> + u32 magic; /* 0x01020304, tells us byte-order of host if we care */
>> + u32 version; /* File dump version, 1 for now. */
>
> Actually I would prefer to have magic first and have ASCII string as
> string, for example "ATH10K-FW-DUMP".
I'd like magic number to stay, was planning to use it to detect byte
ordering (ie, dumps might come from various different platforms, to
be decoded on some different platform).
I will add the string, however.
>> + /* Some info we can get from ath10k struct that might help. */
>> + u32 chip_id;
>> + u32 target_version;
>
> bus_type or something like that would be good to add already now.
Can you be more specific on what info you want here? I don't see
any mention of bus_type in the ath10k dir.
>> + u32 fw_version_minor;
>> + u16 fw_version_release;
>> + u16 fw_version_build;
>> + u32 phy_capability;
>> + u32 hw_min_tx_power;
>> + u32 hw_max_tx_power;
>> + u32 ht_cap_info;
>> + u32 vht_cap_info;
>> + u32 num_rf_chains;
>> + char fw_ver[64]; /* Firmware version string */
>
> Can we reuse ETHTOOL_FWVERS_LEN? cfg80211 already uses that.
>
> #define ETHTOOL_FWVERS_LEN 32
I prefer not to..that way, firmware format will remain the same even if
the kernel changes the fwvers-len some day.
>> + /* Kernel related information */
>> + u32 kernel_ver_code; /* LINUX_VERSION_CODE */
>> + char kernel_ver[64]; /* VERMAGIC_STRING */
>> +
>> + u8 unused[64]; /* Room for growth w/out changing binary format */
>
> Maybe 128 bytes, just so that we don't need to change it for some time?
certainly.
>> @@ -488,6 +555,12 @@ struct ath10k {
>>
>> struct dfs_pattern_detector *dfs_detector;
>>
>> + /* Used for crash-dump storage */
>> + /* Don't over-write dump info until someone reads the data. */
>> + bool crashed_since_read;
>> + struct ath10k_dbglog_entry_storage dbglog_entry_data;
>> + u32 reg_dump_values[REG_DUMP_COUNT_QCA988X];
>
> I think these should be in struct ath10k_debug.
I did not do this because I figure we will want ethtool support w/out
forcing debugfs to be enabled someday soon.
>> +void ath10k_dbg_save_fw_dbg_buffer(struct ath10k *ar, u8 *buffer, int len)
>> +{
>> + int i;
>> + int z = ar->dbglog_entry_data.next_idx;
>> +
>> + /* Don't save any new logs until user-space reads this. */
>> + if (ar->crashed_since_read)
>> + return;
>
> Locking? If this functions depends on something, please document that
> with lockdep_assert_held().
To be honest, I was going to ignore locking and assume that firmware
will not crash that often. Worst case would be a garbled crash dump
as there is no memory allocation involved in gathering the crash,
and the length of the crash dump will not change based on anything in
the crash logic.
I'm a bit leery of adding spin-locks in the dump routine just for
this, but I can add and use a new spin-lock if you prefer. If so,
any idea if we can do the reads of the target's memory while holding
a spin-lock, or would I need some temporary buffers and only lock
while copying that in to the storage in the 'ar'?
>> + ar->dbglog_entry_data.next_idx = z;
>> +}
>> +EXPORT_SYMBOL(ath10k_dbg_save_fw_dbg_buffer);
>> +
>> +static struct ath10k_dump_file_data *ath10k_build_dump_file(struct ath10k *ar)
>> +{
>> + unsigned int len = (sizeof(ar->dbglog_entry_data)
>
> Unneeded parenthesis.
Makes things line up nicely in xemacs auto-indent, but will fix.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
