lkml.org 
[lkml]   [2017]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v3] NTB: Add IDT 89HPESxNTx PCIe-switches support
Date
From: Serge Semin 
> IDT 89HPESxNTx device series is PCIe-switches, which support
...
> Signed-off-by: Serge Semin <fancer.lancer@gmail.com>

Acked-by: Allen Hubbe <Allen.Hubbe@dell.com>

With minor comments. Please include my Ack if you send v4.


> +static u32 idt_nt_read(struct idt_ntb_dev *ndev, const unsigned int reg)
> +{
> + /*
> + * It's obvious bug to request a register exceeding the maximum possible
> + * value as well as to have it unaligned.
> + */
> + WARN_ON(reg > IDT_REG_PCI_MAX || !IS_ALIGNED(reg, IDT_REG_ALIGN));

if (WARN) return ~0?


> +/*
> + * idt_sw_write() - Global registers read method

Doc does not match fn:

> +static u32 idt_sw_read(struct idt_ntb_dev *ndev, const unsigned int reg)
> +{
> + unsigned long irqflags;
> + u32 data;
> +
> + /*
> + * It's obvious bug to request a register exceeding the maximum possible
> + * value as well as to have it unaligned.
> + */
> + WARN_ON(reg > IDT_REG_SW_MAX || !IS_ALIGNED(reg, IDT_REG_ALIGN));

if (WARN) return ~0?

> +
> + /* Lock GASA registers operations */
> + spin_lock_irqsave(&ndev->gasa_lock, irqflags);
> + /* Set the global register address */
> + writel((u32)reg, ndev->cfgspc + (ptrdiff_t)IDT_NT_GASAADDR);

I wonder how that HW will behave if we instruct it to do the general-purpose read out-of-bounds. Better not.

> + /* Get the data of the register */
> + data = readl(ndev->cfgspc + (ptrdiff_t)IDT_NT_GASADATA);
> + /* Unlock GASA registers operations */
> + spin_unlock_irqrestore(&ndev->gasa_lock, irqflags);
> +
> + return data;
> +}


> +static inline int idt_reg_clear_bits(struct idt_ntb_dev *ndev,
> + unsigned int reg, spinlock_t *reg_lock,
> + u64 valid_mask, u64 clear_bits)
> +{
> + unsigned long irqflags;
> + u32 data;
> +
> + if (clear_bits & ~(u64)valid_mask)
> + return -EINVAL;

This check also exists in the Intel driver (blame me).

I've wondered: what if we just pretend any non-valid bits are always "cleared." If they are cleared again, just silently allow it (they stay cleared). Only have this check against attempting to "set" invalid bits.

In Logan's ntb self-test with ntb_tool, it is convenient at the start of the test to "clear all the bits" of the doorbell registers. This would be more simple if the script would just say "clear the bits ~0" instead of "tell me the valid bits and clear those." Currently ntb_tool doesn't report the valid bits, so the valid bitset is a runtime parameter passed to the script (yuck).

Set the bits: are they valid? ok.
Clear the bits: ok!


> + /* It's useless to have this driver loaded if there is no any peer */
> + if (ndev->peer_cnt == 0) {
> + dev_err_pci(ndev, "No active peer found\n");
> + return -EINVAL;
> + }

Maybe it would be useful for development or debugging purposes?


> +static bool idt_ntb_local_link_is_up(struct idt_ntb_dev *ndev)
> +{
...
> + if (!(data & IDT_NTMTBLDATA_VALID))
> + return false;
> +
> + /* Local NTB link is enabled if got here */
> + return true;

Unnecessary branching logic. Just:

return !!(data & IDT_NTMTBLDATA_VALID);

> +static bool idt_ntb_peer_link_is_up(struct idt_ntb_dev *ndev, int pidx)
> +{
...
> + if (!(data & IDT_NTMTBLDATA_VALID))
> + return false;
> +
> + /* Peer NTB link is enabled if got here */
> + return true;

return !!(data & IDT_NTMTBLDATA_VALID);


\
 
 \ /
  Last update: 2017-02-24 17:14    [W:0.106 / U:34.408 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site