mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
	Joerg Roedel <joro@8bytes.org>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Ashok Raj <ashok.raj@intel.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Gayatri Kammela <gayatri.kammela@intel.com>,
	Ravi V Shankar <ravi.v.shankar@intel.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH v4 5/5] iommu/vt-d: Add debugfs support for Interrupt remapping
Date: Tue, 19 Dec 2017 23:30:20 +0200	[thread overview]
Message-ID: <1513719020.7000.234.camel@linux.intel.com> (raw)
In-Reply-To: <1513717687-82420-6-git-send-email-sohil.mehta@intel.com>

On Tue, 2017-12-19 at 13:08 -0800, Sohil Mehta wrote:
> Debugfs extension for Intel IOMMU to dump Interrupt remapping table
> entries for Interrupt remapping and Interrupt posting.
> 
> The file /sys/kernel/debug/intel_iommu/ir_translation_struct provides
> detailed information, such as Index, Source Id, Destination Id, Vector
> and the raw values for entries with the present bit set, in the format
> shown.
> 
> Remapped Interrupt supported on IOMMU: dmar5
>  IR table address:ffff93e09d54c310
> -----------------------------------------------------------
>  Index  SID  Dest_ID  Vct Raw_value_high   Raw_value_low
>  1      3a00 00000600 2c  0000000000043a00 00000600002c0009
>  111    4301 00000900 a2  0000000000044301 0000090000a20009
> 
> Posted Interrupt supported on IOMMU: dmar5
>  IR table address:ffff93e09d54c310
> --------------------------------------------------------------------
>  Index  SID  PDA_high PDA_low  Vct Raw_value_high   Raw_value_low
>  4      4300 00000010 40c7c880 41  0000001000044300 40c7c88000418001
>  5      4300 00000010 40c7c880 51  0000001000044300 40c7c88000518001
> 
> 

> +		seq_printf(m, "\nRemapped Interrupt supported on
> IOMMU: %s\n"

Please, avoid leading \n.

> +			   " IR table address:%p\n", iommu->name,
> +			   iommu->ir_table);
> +
> +		seq_puts(m, "--------------------------------------
> ---------"
> +			 "------------\n");

It's okay to use long string literal on one line. So, don't split (or
for multi-line string literals, split by \n like you do above).

> +	seq_puts(m,
> "\n****\t****\t****\t****\t****\t****\t****\t****\n");

Leading \n.

> +		seq_printf(m, "\nPosted Interrupt supported on IOMMU:
> %s\n"

Ditto.

> +			   " IR table address:%p\n", iommu->name,
> +			   iommu->ir_table);
> +
> +		seq_puts(m, "--------------------------------------
> ----------"
> +			 "--------------------\n");

Join back.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-12-19 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 21:08 [PATCH v4 0/5] Add Intel IOMMU debugfs support Sohil Mehta
2017-12-19 21:08 ` [PATCH v4 1/5] iommu/vt-d: Add debugfs support for Intel IOMMU internals Sohil Mehta
2017-12-19 21:08 ` [PATCH v4 2/5] iommu/vt-d: Add debugfs support to show context internals Sohil Mehta
2017-12-19 21:08 ` [PATCH v4 3/5] iommu/vt-d: Add debugfs support to show register contents Sohil Mehta
2017-12-19 21:08 ` [PATCH v4 4/5] iommu/vt-d: Add debugfs support to show Pasid table contents Sohil Mehta
2017-12-19 21:08 ` [PATCH v4 5/5] iommu/vt-d: Add debugfs support for Interrupt remapping Sohil Mehta
2017-12-19 21:30   ` Andy Shevchenko [this message]
2017-12-20  0:42     ` Mehta, Sohil
2017-12-19 21:25 ` [PATCH v4 0/5] Add Intel IOMMU debugfs support Andy Shevchenko
2017-12-20  1:47   ` Mehta, Sohil

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=1513719020.7000.234.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=fenghua.yu@intel.com \
    --cc=gayatri.kammela@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ravi.v.shankar@intel.com \
    --cc=sohil.mehta@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

Powered by JetHome