public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: "Li, Zhen-Hua" <zhen-hual@hp.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Add new macros for invalidation event
Date: Tue, 19 Aug 2014 13:11:15 +0200	[thread overview]
Message-ID: <20140819111115.GB26492@8bytes.org> (raw)
In-Reply-To: <1408067751-30754-1-git-send-email-zhen-hual@hp.com>

On Fri, Aug 15, 2014 at 09:55:51AM +0800, Li, Zhen-Hua wrote:
> According to intel's spec
>         Intel® Virtualization Technology for Directed I/O,
>         Revision: 1.3 , February 2011,
>         Chaper 10.4.25 to 10.4.28
> 
> There are four registers
> 
>         IECTL_REG   0xa0    Invalidation event control register
>         IEDATA_REG  0xa4    Invalidation event data register
>         IEADDR_REG  0xa8    Invalidation event address register
>         IEUADDR_REG 0xac    Invalidation event upper address register
> 
> Through they are not used in kernel in the latest version, the defination
>  should be added to kernel as well as other registers.
> 
> Signed-off-by: Li, Zhen-Hua <zhen-hual@hp.com>
> ---
>  include/linux/intel-iommu.h | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/include/linux/intel-iommu.h b/include/linux/intel-iommu.h
> index a65208a..15fafd5 100644
> --- a/include/linux/intel-iommu.h
> +++ b/include/linux/intel-iommu.h
> @@ -56,6 +56,10 @@
>  #define DMAR_IQ_SHIFT	4	/* Invalidation queue head/tail shift */
>  #define DMAR_IQA_REG	0x90	/* Invalidation queue addr register */
>  #define DMAR_ICS_REG	0x9c	/* Invalidation complete status register */
> +#define DMAR_IECTL_REG	0xa0	/* Invalidation event control register */
> +#define DMAR_IEDATA_REG	0xa4	/* Invalidation event data register */
> +#define DMAR_IEADDR_REG	0xa8	/* Invalidation event address register */
> +#define DMAR_IEUADDR_REG 0xac	/* Invalidation event upper address register */
>  #define DMAR_IRTA_REG	0xb8    /* Interrupt remapping table addr register */
>  
>  #define OFFSET_STRIDE		(9)

There is no point in adding register defines that are not used anywhere.


	Joerg


      reply	other threads:[~2014-08-19 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15  1:55 [PATCH 1/1] iommu/vt-d: Add new macros for invalidation event Li, Zhen-Hua
2014-08-19 11:11 ` Joerg Roedel [this message]

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=20140819111115.GB26492@8bytes.org \
    --to=joro@8bytes.org \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhen-hual@hp.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