From: fenghua.yu@intel.com
To: Ingo Molnar <mingo@elte.hu>,
David Woodhouse <dwmw2@infradead.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Andrew Lutomirski <amluto@gmail.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Kyle McMartin <kyle@redhat.com>, Yinghai Lu <yinghai@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
IOMMU <iommu@lists.linux-foundation.org>
Subject: Re: [patch 0/4] Intel IOMMU Supspend/Resume Support
Date: Mon, 30 Mar 2009 21:22:08 -0700 [thread overview]
Message-ID: <20090331042208.063501000@intel.com> (raw)
>>
>> The attached patch set implements the suspend and resume feature for
>Intel
>> IOMMU. It hooks to kernel suspend and resume interface. When suspend
>happens, itsaves necessary hardware registers. When resume happens, it
>restores the
>> registers and restarts IOMMU.
>>
>> This patch set can be applied on the tip tree.
>
>Looks good to me, apart from the fact that your #4 patch actually needs
>to come before #1. Shall I apply it to my iommu-2.6.git tree or let Ingo
>take it? If the latter,
>
>Acked-by: David Woodhouse <David.Woodhouse@intel.com>
>Acked-by: David Woodhouse <David.Woodhouse@intel.com>
>Acked-by: David Woodhouse <David.Woodhouse@intel.com>
>Acked-by: David Woodhouse <David.Woodhouse@intel.com>
>
>(if you look carefully, you'll see those are in order 4, 1, 2, 3)
>
>Have we tested this on IA64?
Since ia64 platforms don't support suspend/resume, the code won't take action onia64. But it still installs unused sys device interface.
I'll clean up the code for ia64 and re-send the patch set.
Thanks.
-Fenghua
--
next reply other threads:[~2009-03-31 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 4:22 fenghua.yu [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-02 20:34 [patch 0/4] Intel IOMMU Supspend/Resume Support fenghua.yu
[not found] <20090327212241.234500000@intel.com>
2009-03-28 14:24 ` Andrew Lutomirski
2009-03-30 23:01 ` David Woodhouse
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=20090331042208.063501000@intel.com \
--to=fenghua.yu@intel.com \
--cc=amluto@gmail.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kyle@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.