From: Don Dutile <ddutile-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Chris Wright <chrisw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [PATCH v2] intel_iommu,dmar: reserve mmio of IOMMU registers
Date: Thu, 05 Apr 2012 18:21:38 -0400 [thread overview]
Message-ID: <4F7E1AF2.5010603@redhat.com> (raw)
In-Reply-To: <20120405205806.GV10418-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
On 04/05/2012 04:58 PM, Chris Wright wrote:
> * Donald Dutile (ddutile-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org) wrote:
>> --- a/drivers/iommu/dmar.c
>> +++ b/drivers/iommu/dmar.c
>> @@ -581,7 +581,7 @@ int __init detect_intel_iommu(void)
>> int alloc_iommu(struct dmar_drhd_unit *drhd)
>> {
>> struct intel_iommu *iommu;
>> - int map_size;
>> + resource_size_t map_size;
>> u32 ver;
>> static int iommu_allocated = 0;
>> int agaw = 0;
>> @@ -599,10 +599,17 @@ int alloc_iommu(struct dmar_drhd_unit *drhd)
>> iommu->seq_id = iommu_allocated++;
>> sprintf (iommu->name, "dmar%d", iommu->seq_id);
>>
>> - iommu->reg = ioremap(drhd->reg_base_addr, VTD_PAGE_SIZE);
>
> I think it'd be nice to create a helper function that does the request
> and map. This should include the map, read cap/ecap, calculate size and
> possbily remap. Would probably simplify the error cleanup too.
>
>> + iommu->reg_phys = drhd->reg_base_addr;
>> + iommu->reg_size = VTD_PAGE_SIZE;
>> + if (!request_mem_region(iommu->reg_phys, iommu->reg_size, iommu->name)) {
>> + printk(KERN_ERR "IOMMU: can't reserve memory\n");
>> + goto error;
>> + }
>> +
>> + iommu->reg = ioremap(iommu->reg_phys, iommu->reg_size);
>> if (!iommu->reg) {
>> printk(KERN_ERR "IOMMU: can't map the region\n");
>> - goto error;
>> + goto err_release;
>> }
>> iommu->cap = dmar_readq(iommu->reg + DMAR_CAP_REG);
>> iommu->ecap = dmar_readq(iommu->reg + DMAR_ECAP_REG);
>> @@ -635,19 +642,26 @@ int alloc_iommu(struct dmar_drhd_unit *drhd)
>> map_size = max_t(int, ecap_max_iotlb_offset(iommu->ecap),
>> cap_max_fault_reg_offset(iommu->cap));
>> map_size = VTD_PAGE_ALIGN(map_size);
>> - if (map_size> VTD_PAGE_SIZE) {
>> + if (map_size> iommu->reg_size) {
>> iounmap(iommu->reg);
>> - iommu->reg = ioremap(drhd->reg_base_addr, map_size);
>> + release_mem_region(iommu->reg_phys, iommu->reg_size);
>> + iommu->reg_size = map_size;
>> + if (!request_mem_region(iommu->reg_phys, iommu->reg_size,
>> + iommu->name)) {
>> + printk(KERN_ERR "IOMMU: can't reserve memory\n");
>> + goto error;
>> + }
>> + iommu->reg = ioremap(iommu->reg_phys, iommu->reg_size);
>> if (!iommu->reg) {
>> printk(KERN_ERR "IOMMU: can't map the region\n");
>> - goto error;
>> + goto err_release;
>> }
>> }
>>
>> ver = readl(iommu->reg + DMAR_VER_REG);
>> pr_info("IOMMU %d: reg_base_addr %llx ver %d:%d cap %llx ecap %llx\n",
>> iommu->seq_id,
>> - (unsigned long long)drhd->reg_base_addr,
>> + (unsigned long long)iommu->reg_phys,
>> DMAR_VER_MAJOR(ver), DMAR_VER_MINOR(ver),
>> (unsigned long long)iommu->cap,
>> (unsigned long long)iommu->ecap);
>> @@ -659,6 +673,8 @@ int alloc_iommu(struct dmar_drhd_unit *drhd)
>>
>> err_unmap:
>> iounmap(iommu->reg);
>> + err_release:
>> + release_mem_region(iommu->reg_phys, iommu->reg_size);
>> error:
>> kfree(iommu);
>> return -1;
>> @@ -671,8 +687,11 @@ void free_iommu(struct intel_iommu *iommu)
>>
>> free_dmar_iommu(iommu);
>>
>> - if (iommu->reg)
>> + if (iommu->reg) {
>> iounmap(iommu->reg);
>> + release_mem_region(iommu->reg_phys, iommu->reg_size);
>> + }
>> +
>> kfree(iommu);
>> }
>>
>> diff --git a/include/linux/intel-iommu.h b/include/linux/intel-iommu.h
>> index e6ca56d..c6d132b 100644
>> --- a/include/linux/intel-iommu.h
>> +++ b/include/linux/intel-iommu.h
>> @@ -308,6 +308,8 @@ enum {
>>
>> struct intel_iommu {
>> void __iomem *reg; /* Pointer to hardware regs, virtual addr */
>> + resource_size_t reg_phys;
>> + resource_size_t reg_size;
>
> I'd make these u64
ok, will work up v3 tomorrow..
thanks for feedback!
prev parent reply other threads:[~2012-04-05 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 22:38 [PATCH v2] intel_iommu,dmar: reserve mmio of IOMMU registers Donald Dutile
[not found] ` <1331332723-19522-1-git-send-email-ddutile-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-04-05 20:58 ` Chris Wright
[not found] ` <20120405205806.GV10418-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
2012-04-05 22:21 ` Don Dutile [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=4F7E1AF2.5010603@redhat.com \
--to=ddutile-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=chrisw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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).