From: Wei Yang <richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Wei Yang <richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V4 0/4] Code refine for Intel IOMMU
Date: Sun, 8 May 2016 13:22:53 +0000 [thread overview]
Message-ID: <20160508132253.GA2708@vultr.guest> (raw)
In-Reply-To: <1460645710-22656-1-git-send-email-richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Ping~
On Thu, Apr 14, 2016 at 02:55:06PM +0000, Wei Yang wrote:
>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
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2016-05-08 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 14:55 [PATCH V4 0/4] Code refine for Intel IOMMU Wei Yang
[not found] ` <1460645710-22656-1-git-send-email-richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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 ` Wei Yang [this message]
[not found] ` <20160508132253.GA2708-yrDqe6+Pica9sAcnBtTtJQ@public.gmane.org>
2016-05-09 11:24 ` [PATCH V4 0/4] Code refine for Intel IOMMU Joerg Roedel
[not found] ` <20160509112401.GC13275-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
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=20160508132253.GA2708@vultr.guest \
--to=richard.weiyang-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).