From: Ingo Molnar <mingo@kernel.org>
To: Qiaowei Ren <qiaowei.ren@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Gang Wei <gang.wei@intel.com>
Subject: Re: [PATCH v3] x86, tboot: iomem fixes
Date: Thu, 18 Jul 2013 12:42:23 +0200 [thread overview]
Message-ID: <20130718104223.GD23558@gmail.com> (raw)
In-Reply-To: <1374134874-8161-1-git-send-email-qiaowei.ren@intel.com>
* Qiaowei Ren <qiaowei.ren@intel.com> wrote:
> Current code doesn't use specific interface to access I/O space.
> So some potential bugs can be caused. We can fix this by using
> specific API.
This is still very vague.
>
> Signed-off-by: Qiaowei Ren <qiaowei.ren@intel.com>
> ---
> arch/x86/kernel/tboot.c | 21 ++++++++++++---------
> 1 file changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/kernel/tboot.c b/arch/x86/kernel/tboot.c
> index 3ff42d2..afe8cf8 100644
> --- a/arch/x86/kernel/tboot.c
> +++ b/arch/x86/kernel/tboot.c
> @@ -466,9 +466,12 @@ struct sinit_mle_data {
> u32 vtd_dmars_off;
> } __packed;
>
> +#define SINIT_MLE_DATA_VTD_DMAR_OFF 140
> +
> struct acpi_table_header *tboot_get_dmar_table(struct acpi_table_header *dmar_tbl)
> {
> - void *heap_base, *heap_ptr, *config;
> + void __iomem *heap_base, *heap_ptr, *config;
> + u32 dmar_tbl_off;
>
> if (!tboot_enabled())
> return dmar_tbl;
> @@ -485,25 +488,25 @@ struct acpi_table_header *tboot_get_dmar_table(struct acpi_table_header *dmar_tb
> return NULL;
>
> /* now map TXT heap */
> - heap_base = ioremap(*(u64 *)(config + TXTCR_HEAP_BASE),
> - *(u64 *)(config + TXTCR_HEAP_SIZE));
> + heap_base = ioremap(readl(config + TXTCR_HEAP_BASE),
> + readl(config + TXTCR_HEAP_SIZE));
> iounmap(config);
> if (!heap_base)
> return NULL;
>
> /* walk heap to SinitMleData */
> /* skip BiosData */
> - heap_ptr = heap_base + *(u64 *)heap_base;
> + heap_ptr = heap_base + readq(heap_base);
> /* skip OsMleData */
> - heap_ptr += *(u64 *)heap_ptr;
> + heap_ptr += readq(heap_ptr);
> /* skip OsSinitData */
> - heap_ptr += *(u64 *)heap_ptr;
> + heap_ptr += readq(heap_ptr);
> /* now points to SinitMleDataSize; set to SinitMleData */
> heap_ptr += sizeof(u64);
> /* get addr of DMAR table */
> - dmar_tbl = (struct acpi_table_header *)(heap_ptr +
> - ((struct sinit_mle_data *)heap_ptr)->vtd_dmars_off -
> - sizeof(u64));
> + dmar_tbl_off = readl(heap_ptr + SINIT_MLE_DATA_VTD_DMAR_OFF);
> + memcpy_fromio(dmar_tbl, heap_ptr + dmar_tbl_off - sizeof(u64),
> + sizeof(struct acpi_table_header));
That memcpy (or an equivalent of it) was not in the code before, AFAICS.
How can this be an 'interface fix'? It adds in new code...
Thanks,
Ingo
next prev parent reply other threads:[~2013-07-18 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 8:07 [PATCH v3] x86, tboot: iomem fixes Qiaowei Ren
2013-07-18 10:42 ` Ingo Molnar [this message]
2013-07-18 12:42 ` Ren, Qiaowei
2013-07-19 7:59 ` Ingo Molnar
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=20130718104223.GD23558@gmail.com \
--to=mingo@kernel.org \
--cc=gang.wei@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qiaowei.ren@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).