From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
linux-kernel@vger.kernel.org, pasic@linux.ibm.com,
frankja@linux.ibm.com, mst@redhat.com, jasowang@redhat.com,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v2 1/1] s390: virtio: let arch accept devices without IOMMU feature
Date: Tue, 16 Jun 2020 14:21:12 +0200 [thread overview]
Message-ID: <20200616142112.2d08ff7d.cohuck@redhat.com> (raw)
In-Reply-To: <a93bf169-55ca-2a77-f9a5-b27bf18176e2@linux.ibm.com>
On Tue, 16 Jun 2020 09:35:19 +0200
Pierre Morel <pmorel@linux.ibm.com> wrote:
> On 2020-06-16 08:55, Christian Borntraeger wrote:
> >
> >
> > On 15.06.20 14:39, Pierre Morel wrote:
> >> An architecture protecting the guest memory against unauthorized host
> >> access may want to enforce VIRTIO I/O device protection through the
> >> use of VIRTIO_F_IOMMU_PLATFORM.
> >>
> >> Let's give a chance to the architecture to accept or not devices
> >> without VIRTIO_F_IOMMU_PLATFORM.
> >>
> >> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> >
> >
> > Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> Thanks,
>
> >
> > Shouldnt we maybe add a pr_warn if that happens to help the admins to understand what is going on?
> >
> >
>
> Yes, Connie asked for it too, good that you remind it to me, I add it.
Yes, please :)
next prev parent reply other threads:[~2020-06-16 12:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 12:39 [PATCH v2 0/1] s390: virtio: let's arch choose to accept devices without IOMMU feature Pierre Morel
2020-06-15 12:39 ` [PATCH v2 1/1] s390: virtio: let arch " Pierre Morel
2020-06-16 6:22 ` Jason Wang
2020-06-16 7:33 ` Pierre Morel
2020-06-16 6:55 ` Christian Borntraeger
2020-06-16 7:35 ` Pierre Morel
2020-06-16 12:21 ` Cornelia Huck [this message]
2020-06-16 9:52 ` Halil Pasic
2020-06-16 10:52 ` Pierre Morel
2020-06-16 11:57 ` Halil Pasic
2020-06-16 12:17 ` Cornelia Huck
2020-06-16 13:41 ` Pierre Morel
2020-06-16 13:50 ` Cornelia Huck
2020-06-16 12:20 ` Cornelia Huck
2020-06-16 13:36 ` Pierre Morel
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=20200616142112.2d08ff7d.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=virtualization@lists.linux-foundation.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).