Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joao Martins <joao.m.martins@oracle.com>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: suravee.suthikulpanit@amd.com, iommu@lists.linux.dev, joro@8bytes.org
Subject: Re: [PATCH 1/2] iommu/amd: Generalize log overflow handling
Date: Tue, 20 Jun 2023 15:51:43 +0100	[thread overview]
Message-ID: <f0b4d748-9c13-7214-e578-a9cb27ba6e4c@oracle.com> (raw)
In-Reply-To: <20230609101746.6412-2-vasant.hegde@amd.com>



On 09/06/2023 11:17, Vasant Hegde wrote:
> IOMMU has three different logs (Event, GA and PPR log) and each uses
> different buffer for logging. Once buffer becomes full IOMMU generates
> overflow interrupt and we have to restart the logs. Log restart procedure
> is same for all three logs except it uses different bits in 'MMIO Offset
> 2020h IOMMU Status Register'. Hence lets move common code to generic
> function and individual log overflow handler will call generic function
> with appropriate parameters.
> 
> Also rename MMIO_STATUS_EVT_OVERFLOW_INT_MASK as
> MMIO_STATUS_EVT_OVERFLOW_MASK.
> 
> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>

Really nice rework, fwiw:

	Reviewed-by: Joao Martins <joao.m.martins@oracle.com>

Just a though below (you don't need to address it, just an idea)

> ---
>  drivers/iommu/amd/amd_iommu_types.h |  3 +-
>  drivers/iommu/amd/init.c            | 51 ++++++++++++++++++-----------
>  drivers/iommu/amd/iommu.c           |  4 +--
>  3 files changed, 36 insertions(+), 22 deletions(-)
> 
> diff --git a/drivers/iommu/amd/amd_iommu_types.h b/drivers/iommu/amd/amd_iommu_types.h
> index 364fdaa52e74..318b84cf47f6 100644
> --- a/drivers/iommu/amd/amd_iommu_types.h
> +++ b/drivers/iommu/amd/amd_iommu_types.h
> @@ -120,9 +120,10 @@
>  #define PASID_MASK		0x0000ffff
>  
>  /* MMIO status bits */
> -#define MMIO_STATUS_EVT_OVERFLOW_INT_MASK	BIT(0)
> +#define MMIO_STATUS_EVT_OVERFLOW_MASK		BIT(0)
>  #define MMIO_STATUS_EVT_INT_MASK		BIT(1)
>  #define MMIO_STATUS_COM_WAIT_INT_MASK		BIT(2)
> +#define MMIO_STATUS_EVT_RUN_MASK		BIT(3)
>  #define MMIO_STATUS_PPR_INT_MASK		BIT(6)
>  #define MMIO_STATUS_GALOG_RUN_MASK		BIT(8)
>  #define MMIO_STATUS_GALOG_OVERFLOW_MASK		BIT(9)
> diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c
> index c2d80a4e5fb0..3c21e9333899 100644
> --- a/drivers/iommu/amd/init.c
> +++ b/drivers/iommu/amd/init.c
> @@ -748,38 +748,51 @@ static int __init alloc_command_buffer(struct amd_iommu *iommu)
>  	return iommu->cmd_buf ? 0 : -ENOMEM;
>  }
>  
> +/*
> + * Interrupt handler has processed all pending events and adjusted head
> + * and tail pointer. Reset overflow mask and restart logging again.
> + */
> +static void amd_iommu_restart_log(struct amd_iommu *iommu, const char *evt_type,
> +				  u8 cntrl_intr, u8 cntrl_log,
> +				  u32 status_run_mask, u32 status_overflow_mask)
> +{
> +	u32 status;
> +
> +	status = readl(iommu->mmio_base + MMIO_STATUS_OFFSET);
> +	if (status & status_run_mask)
> +		return;
> +
> +	pr_info_ratelimited("IOMMU %s log restarting\n", evt_type);
> +
> +	iommu_feature_disable(iommu, cntrl_log);
> +	iommu_feature_disable(iommu, cntrl_intr);
> +
> +	writel(status_overflow_mask, iommu->mmio_base + MMIO_STATUS_OFFSET);
> +
> +	iommu_feature_enable(iommu, cntrl_intr);
> +	iommu_feature_enable(iommu, cntrl_log);
> +}
> +
>  /*
>   * This function restarts event logging in case the IOMMU experienced
>   * an event log buffer overflow.
>   */
>  void amd_iommu_restart_event_logging(struct amd_iommu *iommu)
>  {
> -	iommu_feature_disable(iommu, CONTROL_EVT_LOG_EN);
> -	iommu_feature_enable(iommu, CONTROL_EVT_LOG_EN);
> +	amd_iommu_restart_log(iommu, "Event", CONTROL_EVT_INT_EN,
> +			      CONTROL_EVT_LOG_EN, MMIO_STATUS_EVT_RUN_MASK,
> +			      MMIO_STATUS_EVT_OVERFLOW_MASK);
>  }
>  

If CONTROL_EVT_{INT,LOG} was instead EVT{INT,LOG} (like it's PPR and GA
counterparts), I do wonder if a macro is better placed here considering that the
only think that changes is the string name and whether it's EVT, PPR or GA is
used. But perhaps that might be too obscure.

>  /*
>   * This function restarts event logging in case the IOMMU experienced
> - * an GA log overflow.
> + * GA log overflow.
>   */
>  void amd_iommu_restart_ga_log(struct amd_iommu *iommu)
>  {
> -	u32 status;
> -
> -	status = readl(iommu->mmio_base + MMIO_STATUS_OFFSET);
> -	if (status & MMIO_STATUS_GALOG_RUN_MASK)
> -		return;
> -
> -	pr_info_ratelimited("IOMMU GA Log restarting\n");
> -
> -	iommu_feature_disable(iommu, CONTROL_GALOG_EN);
> -	iommu_feature_disable(iommu, CONTROL_GAINT_EN);
> -
> -	writel(MMIO_STATUS_GALOG_OVERFLOW_MASK,
> -	       iommu->mmio_base + MMIO_STATUS_OFFSET);
> -
> -	iommu_feature_enable(iommu, CONTROL_GAINT_EN);
> -	iommu_feature_enable(iommu, CONTROL_GALOG_EN);
> +	amd_iommu_restart_log(iommu, "GA", CONTROL_GAINT_EN,
> +			      CONTROL_GALOG_EN, MMIO_STATUS_GALOG_RUN_MASK,
> +			      MMIO_STATUS_GALOG_OVERFLOW_MASK);
>  }
>  
>  /*
> diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
> index ad501944d77c..a29548d98b6a 100644
> --- a/drivers/iommu/amd/iommu.c
> +++ b/drivers/iommu/amd/iommu.c
> @@ -842,7 +842,7 @@ amd_iommu_set_pci_msi_domain(struct device *dev, struct amd_iommu *iommu) { }
>  #endif /* !CONFIG_IRQ_REMAP */
>  
>  #define AMD_IOMMU_INT_MASK	\
> -	(MMIO_STATUS_EVT_OVERFLOW_INT_MASK | \
> +	(MMIO_STATUS_EVT_OVERFLOW_MASK | \
>  	 MMIO_STATUS_EVT_INT_MASK | \
>  	 MMIO_STATUS_PPR_INT_MASK | \
>  	 MMIO_STATUS_GALOG_OVERFLOW_MASK | \
> @@ -881,7 +881,7 @@ irqreturn_t amd_iommu_int_thread(int irq, void *data)
>  		}
>  #endif
>  
> -		if (status & MMIO_STATUS_EVT_OVERFLOW_INT_MASK) {
> +		if (status & MMIO_STATUS_EVT_OVERFLOW_MASK) {
>  			pr_info_ratelimited("IOMMU event log overflow\n");
>  			amd_iommu_restart_event_logging(iommu);
>  		}

  parent reply	other threads:[~2023-06-20 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 10:17 [PATCH 0/2] iommu/amd: Add PPR overflow support Vasant Hegde
2023-06-09 10:17 ` [PATCH 1/2] iommu/amd: Generalize log overflow handling Vasant Hegde
2023-06-13 20:22   ` Jerry Snitselaar
2023-06-20 14:51   ` Joao Martins [this message]
2023-06-20 16:01     ` Vasant Hegde
2023-06-09 10:17 ` [PATCH 2/2] iommu/amd: Handle PPR log overflow Vasant Hegde
2023-06-13 20:29   ` Jerry Snitselaar
2023-06-14  7:28     ` Vasant Hegde
2023-06-20 14:53   ` Joao Martins

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=f0b4d748-9c13-7214-e578-a9cb27ba6e4c@oracle.com \
    --to=joao.m.martins@oracle.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.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