From: Donald Dutile <ddutile@redhat.com>
To: dwmw2@infradead.org
Cc: iommu@lists.linux-foundation.org, mingo@elte.hu,
linux-kernel@vger.kernel.org, chrisw@redhat.com,
suresh.b.siddha@intel.com
Subject: [PATCH 0/2]intel-iommu: reserve IOMMU register space
Date: Mon, 4 Jun 2012 17:29:00 -0400 [thread overview]
Message-ID: <1338845342-12464-1-git-send-email-ddutile@redhat.com> (raw)
Reserve the memory space that Intel IOMMUs use so
they aren't dynamically allocated by hot-plug operations.
Seem on some systems when BIOS doesn't place IOMMU registers
in a safe, non-hotplug location. ... until BIOS quickly changed.
Since modifying dmar.c, and information prints in the code,
cleanup the info/warning prints in the first patch to use
more std pr_*() functions and formatting.
Second patch is core of the iomem space reservation.
Bjorn had posted a similar patch a couple weeks back,
and I informed him in a side note I had this patch set
in my queue, just needed couple minor edits to complete.
So, if you are having deja-vu, now you know why...
Signed-off-by: Donald Dutile <ddutile@redhat.com>
next reply other threads:[~2012-06-04 21:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 21:29 Donald Dutile [this message]
2012-06-04 21:29 ` [PATCH 1/2] iommu: dmar: replace printks with appropriate pr_*() Donald Dutile
2012-06-04 22:15 ` Joe Perches
2012-06-04 22:28 ` Don Dutile
2012-06-08 14:55 ` [tip:core/iommu] iommu/dmar: Replace printks with appropriate pr_* () tip-bot for Donald Dutile
2012-06-04 21:29 ` [PATCH 2/2] iommu: dmar -- reserve mmio space used by IOMMU Donald Dutile
2012-06-04 22:37 ` David Woodhouse
2012-06-04 23:09 ` Don Dutile
2012-06-04 23:23 ` David Woodhouse
2012-06-04 23:52 ` Don Dutile
2012-06-06 8:16 ` Ingo Molnar
2012-06-06 8:26 ` David Woodhouse
2012-06-06 8:29 ` Ingo Molnar
2012-06-06 8:45 ` David Woodhouse
2012-06-06 23:56 ` Chris Wright
2012-06-06 23:58 ` Chris Wright
2012-06-08 14:56 ` [tip:core/iommu] iommu/dmar: Reserve mmio space used by the IOMMU, if the BIOS forgets to tip-bot for Donald Dutile
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=1338845342-12464-1-git-send-email-ddutile@redhat.com \
--to=ddutile@redhat.com \
--cc=chrisw@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@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