From: Jason Gunthorpe <jgg@nvidia.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Cornelia Huck <cohuck@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Kirti Wankhede <kwankhede@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>,
"Zengtao (B)" <prime.zeng@hisilicon.com>,
liulongfang <liulongfang@huawei.com>
Subject: Re: [PATCH RFC v2] vfio: Documentation for the migration region
Date: Wed, 1 Dec 2021 09:49:18 -0400 [thread overview]
Message-ID: <20211201134918.GI4670@nvidia.com> (raw)
In-Reply-To: <90226a3c13a2404086dc555e4aced7cb@huawei.com>
On Wed, Dec 01, 2021 at 09:54:27AM +0000, Shameerali Kolothum Thodi wrote:
> So just to make it clear , if a device declares that it doesn't support NDMA
> and P2P, is the v1 version of the spec good enough or we still need to take
> care the case that a malicious user might try MMIO access in !RUNNING
> state and should have kernel infrastructure in place to safe guard that?
My thinking is so long as the hostile user space cannot compromise the
kernel it is OK. A corrupted migration is acceptable if userspace is
not following the rules.
From a qemu perspective it should prevent a hostile VM from corrupting
the migration, as that is allowing the VM to attack the infrastructure
even if it hopefully only harms itself.
> (Just a note to clarify that these are not HNS devices per se. HNS actually
> stands for HiSilicon Network Subsystem and doesn't currently have live
> migration capability. The devices capable of live migration are HiSilicon
> Accelerator devices).
Sorry, I mostly talk to the hns team ;)
Jason
next prev parent reply other threads:[~2021-12-01 13:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 14:45 [PATCH RFC v2] vfio: Documentation for the migration region Jason Gunthorpe
2021-11-30 17:26 ` Alex Williamson
2021-11-30 18:59 ` Jason Gunthorpe
2021-11-30 22:35 ` Alex Williamson
2021-12-01 3:14 ` Jason Gunthorpe
2021-12-01 9:54 ` Shameerali Kolothum Thodi
2021-12-01 13:49 ` Jason Gunthorpe [this message]
2021-12-01 20:03 ` Alex Williamson
2021-12-01 23:25 ` Jason Gunthorpe
2021-12-02 17:05 ` Cornelia Huck
2021-12-02 17:41 ` Jason Gunthorpe
2021-12-02 17:46 ` Cornelia Huck
2021-12-03 18:06 ` Alex Williamson
2021-12-06 16:03 ` Cornelia Huck
2021-12-06 17:34 ` Jason Gunthorpe
2021-12-06 18:06 ` Cornelia Huck
2021-12-06 19:19 ` Jason Gunthorpe
2021-12-07 11:16 ` Cornelia Huck
2021-12-07 15:51 ` Jason Gunthorpe
2021-12-07 16:30 ` Cornelia Huck
2021-12-07 17:00 ` Jason Gunthorpe
2021-12-08 16:06 ` Alex Williamson
2021-12-08 20:27 ` Jason Gunthorpe
2021-12-06 19:15 ` Jason Gunthorpe
2021-12-07 10:50 ` Cornelia Huck
2021-12-07 15:37 ` Jason Gunthorpe
2021-12-07 15:56 ` Cornelia Huck
2021-12-07 16:13 ` Jason Gunthorpe
2021-12-07 16:22 ` Alex Williamson
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=20211201134918.GI4670@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=mgurtovoy@nvidia.com \
--cc=prime.zeng@hisilicon.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yishaih@nvidia.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;
as well as URLs for NNTP newsgroup(s).