From: "Zeng, Jason" <jason.zeng@intel.com>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"Zeng, Jason" <jason.zeng@intel.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: RE: [PATCH] intel-iommu: Turn off translations at shutdown
Date: Mon, 11 Nov 2019 00:39:15 +0000 [thread overview]
Message-ID: <8D8B600C3EC1B64FAD4503F0B66C61F23BC0DC@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CABeXuvoiX639HchLbgTHLiXPh=Yr2dJHUp2Yqc6pNJ3As1OJ8A@mail.gmail.com>
> -----Original Message-----
> > > > For VMM live update case, we should be able to detect and bypass
> > > > the shutdown that Deepa introduced here, so keep IOMMU still
> operating?
> > >
> > > Is that a 'yes' to Deepa's "if someone wants to make it conditional,
> > > we can do that" ?
> >
> > Yes, I think so. Thanks!
>
> Are these changes already part of the kernel like avoiding shutdown of the
> passthrough devices? device_shutdown() doesn't seem to be doing anything
> selectively as of now.
>
No, it is not in upstream yet. It is an on-going effort, which tries to kexec reboot
the host while keeping IOMMU still working.
Thanks,
Jason
> Thanks,
> Deepa
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2019-11-11 0:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 20:59 [PATCH] intel-iommu: Turn off translations at shutdown Deepa Dinamani
2019-11-07 21:27 ` Deepa Dinamani
2019-11-08 3:07 ` Lu Baolu
2019-11-08 3:06 ` Lu Baolu
2019-11-08 22:28 ` Deepa Dinamani
2019-11-09 0:35 ` Lu Baolu
2019-11-08 7:54 ` David Woodhouse
2019-11-08 8:47 ` Zeng, Jason
2019-11-08 8:57 ` David Woodhouse
2019-11-08 9:11 ` Zeng, Jason
2019-11-08 22:48 ` Deepa Dinamani
2019-11-10 18:24 ` Deepa Dinamani
2019-11-10 20:36 ` Deepa Dinamani
2019-11-11 2:35 ` Zeng, Jason
2019-11-11 0:39 ` Zeng, Jason [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=8D8B600C3EC1B64FAD4503F0B66C61F23BC0DC@SHSMSX103.ccr.corp.intel.com \
--to=jason.zeng@intel.com \
--cc=deepa.kernel@gmail.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.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 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).