From: Ingo Molnar <mingo@elte.hu>
To: fenghua.yu@intel.com
Cc: dwmw2@infradead.org, amluto@gmail.com, kyle@redhat.com,
mgross@linux.intel.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org
Subject: Re: [patch 2/2] Intel IOMMU Suspend/Resume Support for Queued Invalidation.
Date: Wed, 25 Mar 2009 21:28:30 +0100 [thread overview]
Message-ID: <20090325202830.GB26204@elte.hu> (raw)
In-Reply-To: <20090325184635.523469000@intel.com>
(only small style nits.)
* fenghua.yu@intel.com <fenghua.yu@intel.com> wrote:
> /*
> + * Enable queued invalidation.
> + */
> +static void __dmar_enable_qi(struct intel_iommu *iommu)
nice helper function.
> +{
> + u32 cmd, sts;
> + unsigned long flags;
> + struct q_inval *qi = iommu->qi;
> +
> + qi->free_head = qi->free_tail = 0;
> + qi->free_cnt = QI_LENGTH;
> +
> + spin_lock_irqsave(&iommu->register_lock, flags);
> + /* write zero to the tail reg */
> + writel(0, iommu->reg + DMAR_IQT_REG);
( small nit: critical sections are important to see at a glance, and
they are easier to recognize if there's a newline before and after
the spin_lock_irqsave() call. That will also make the comment
after that stand out more. )
> +
> + dmar_writeq(iommu->reg + DMAR_IQA_REG, virt_to_phys(qi->desc));
> +
> + cmd = iommu->gcmd | DMA_GCMD_QIE;
> + iommu->gcmd |= DMA_GCMD_QIE;
> + writel(cmd, iommu->reg + DMAR_GCMD_REG);
> +
> + /* Make sure hardware complete it */
> + IOMMU_WAIT_OP(iommu, DMAR_GSTS_REG, readl, (sts & DMA_GSTS_QIES), sts);
> + spin_unlock_irqrestore(&iommu->register_lock, flags);
(ditto.)
> +}
> +
> +/*
> * Enable Queued Invalidation interface. This is a must to support
> * interrupt-remapping. Also used by DMA-remapping, which replaces
> * register based IOTLB invalidation.
> */
> int dmar_enable_qi(struct intel_iommu *iommu)
> {
> - u32 cmd, sts;
> - unsigned long flags;
> struct q_inval *qi;
>
> if (!ecap_qis(iommu->ecap))
> @@ -835,19 +860,7 @@ int dmar_enable_qi(struct intel_iommu *iommu)
>
> spin_lock_init(&qi->q_lock);
>
> - spin_lock_irqsave(&iommu->register_lock, flags);
> - /* write zero to the tail reg */
> - writel(0, iommu->reg + DMAR_IQT_REG);
> -
> - dmar_writeq(iommu->reg + DMAR_IQA_REG, virt_to_phys(qi->desc));
> -
> - cmd = iommu->gcmd | DMA_GCMD_QIE;
> - iommu->gcmd |= DMA_GCMD_QIE;
> - writel(cmd, iommu->reg + DMAR_GCMD_REG);
> -
> - /* Make sure hardware complete it */
> - IOMMU_WAIT_OP(iommu, DMAR_GSTS_REG, readl, (sts & DMA_GSTS_QIES), sts);
> - spin_unlock_irqrestore(&iommu->register_lock, flags);
> + __dmar_enable_qi(iommu);
>
> return 0;
> }
> @@ -1102,3 +1115,27 @@ int __init enable_drhd_fault_handling(void)
>
> return 0;
> }
> +
> +/*
> + * Re-enable Queued Invalidation interface.
> + */
> +int dmar_reenable_qi(struct intel_iommu *iommu)
> +{
> + if (!ecap_qis(iommu->ecap))
> + return -ENOENT;
> +
> + if (!iommu->qi)
> + return -ENOENT;
> +
> + /*
> + * First disable queued invalidation.
> + */
> + dmar_disable_qi(iommu);
> + /* Then enable queued invalidation again. Since there is no pending
> + * invalidation requests now, it's safe to re-enable queued
> + * invalidation.
> + */
> + __dmar_enable_qi(iommu);
the comment style looks a bit inconsistent here - the second
one should be full winged comments as well, i.e.:
> + /*
> + * First disable queued invalidation.
> + */
> + dmar_disable_qi(iommu);
> +
> + /*
> + * Then enable queued invalidation again. Since there is no pending
> + * invalidation requests now, it's safe to re-enable queued
> + * invalidation.
> + */
> + __dmar_enable_qi(iommu);
Thanks,
Ingo
next prev parent reply other threads:[~2009-03-25 20:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 18:45 [patch 0/2] Intel IOMMU Suspend/Resume Support fenghua.yu
2009-03-25 18:45 ` [patch 1/2] Intel IOMMU Suspend/Resume Support for DMAR fenghua.yu
2009-03-25 20:12 ` Ingo Molnar
2009-03-25 23:47 ` David Woodhouse
2009-03-26 9:58 ` Ingo Molnar
2009-03-25 18:45 ` [patch 2/2] Intel IOMMU Suspend/Resume Support for Queued Invalidation fenghua.yu
2009-03-25 20:28 ` Ingo Molnar [this message]
2009-03-25 20:53 ` [patch 0/2] Intel IOMMU Suspend/Resume Support Andrew Lutomirski
2009-03-25 20:57 ` Yu, Fenghua
2009-03-25 21:21 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-03-24 19:58 2.6.29: can't resume from suspend with DMAR (intel iommu) enabled Andrew Lutomirski
2009-03-24 20:32 ` Ingo Molnar
2009-03-24 22:37 ` [PATCH 2/2] Intel IOMMU Suspend/Resume Support for Queued Invalidation Fenghua Yu
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=20090325202830.GB26204@elte.hu \
--to=mingo@elte.hu \
--cc=amluto@gmail.com \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kyle@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.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
all inboxes | Powered by JetHome®