mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: joro@8bytes.org, jiang.liu@linux.intel.com, tglx@linutronix.de
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH V4 0/4] Code refine for Intel IOMMU
Date: Thu, 14 Apr 2016 14:55:06 +0000	[thread overview]
Message-ID: <1460645710-22656-1-git-send-email-richard.weiyang@gmail.com> (raw)

These four patches try to refine the Intel IOMMU.                                                                                     
                                                                                                                                      
Patch 1/2 tries to make it more user friendly by add a zero-sized array in                                                            
some dmar data structure.                                                                                                             
Patch 3 move the ckeck of Register Base Address ahead to avoid cleanup when it                                                        
is NULL.                                                                                                                              
Patch 4 re-use dmar_walk_dmar_table() to make the code easy to understand.

V4:
  * add similar change for struct dmar_atsr_unit in patch 1
  * add similar change for rmrr and atsr in patch 2

V3:
  * change hdr to drhd from type acpi_dmar_header to acpi_dmar_hardware_unit 
  * add reason in changelog for the change in Patch 1

V2:
  * add patch 3 and 4

Wei Yang (4):
  iommu/vt-d: replace *hdr with {drhd/atsr}[0] in struct
    dmar_{drhd/atsr}_unit
  iommu/vt-d: use zero-sized array in DMAR related ACPI structures
  iommu/vt-d: check Register Base Address at the beginning of
    dmar_parse_one_drhd()
  iommu/vt-d: refine dmar_acpi_dev_scope_init() with
    dmar_walk_dmar_table()

 drivers/iommu/dmar.c                |  129 +++++++++++++++++------------------
 drivers/iommu/intel-iommu.c         |   26 +++----
 drivers/iommu/intel_irq_remapping.c |   10 ++-
 include/acpi/actbl2.h               |   33 +++++----
 include/linux/dmar.h                |    3 +-
 5 files changed, 102 insertions(+), 99 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2016-04-14 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 14:55 Wei Yang [this message]
2016-04-14 14:55 ` [PATCH V4 1/4] iommu/vt-d: replace *hdr with {drhd/atsr}[0] in struct dmar_{drhd/atsr}_unit Wei Yang
2016-04-14 14:55 ` [PATCH V4 2/4] iommu/vt-d: use zero-sized array in DMAR related ACPI structures Wei Yang
2016-04-14 14:55 ` [PATCH V4 3/4] iommu/vt-d: check Register Base Address at the beginning of dmar_parse_one_drhd() Wei Yang
2016-04-14 14:55 ` [PATCH V4 4/4] iommu/vt-d: refine dmar_acpi_dev_scope_init() with dmar_walk_dmar_table() Wei Yang
2016-05-08 13:22 ` [PATCH V4 0/4] Code refine for Intel IOMMU Wei Yang
2016-05-09 11:24   ` Joerg Roedel
2016-05-09 22:20     ` Wei Yang

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=1460645710-22656-1-git-send-email-richard.weiyang@gmail.com \
    --to=richard.weiyang@gmail.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jiang.liu@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®