mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lutomirski <amluto@gmail.com>
To: fenghua.yu@intel.com
Cc: mingo@elte.hu, dwmw2@infradead.org, kyle@redhat.com,
	mgross@linux.intel.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org
Subject: Re: [patch 0/2] Intel IOMMU Suspend/Resume Support
Date: Wed, 25 Mar 2009 16:53:22 -0400	[thread overview]
Message-ID: <cb0375e10903251353r367294d1ra00226e030594a32@mail.gmail.com> (raw)
In-Reply-To: <20090325184548.012018000@intel.com>

It looks like patch 1 calls dmar_reenable_qi but patch 2 defines it.

In 2.6.29, there's no dmar_disable_qi that I can see.  Can you respin
these against something a little less scary than -tip during a merge
window?  (Especially since -stable will need this soon.)

Thanks,
Andy

On Wed, Mar 25, 2009 at 2:45 PM,  <fenghua.yu@intel.com> wrote:
> Current Intel IOMMU does not support suspend and resume. In S3 event, kernel
> crashes when IOMMU is enabled. The attached patch set implements the suspend and
> resume feature for Intel IOMMU. It hooks to kernel suspend and resume interface.
> When suspend happens, it saves necessary hardware registers. When resume happens
> it restores the registers and restarts IOMMU.
>
> This patch set is applied to the tip tree.
>
> --
>
>

  parent reply	other threads:[~2009-03-25 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 18:45 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
2009-03-25 20:53 ` Andrew Lutomirski [this message]
2009-03-25 20:57   ` [patch 0/2] Intel IOMMU Suspend/Resume Support Yu, Fenghua
2009-03-25 21:21     ` 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=cb0375e10903251353r367294d1ra00226e030594a32@mail.gmail.com \
    --to=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 \
    --cc=mingo@elte.hu \
    /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®