From: Pierre Morel <pmorel@linux.ibm.com>
To: Jason Wang <jasowang@redhat.com>, linux-kernel@vger.kernel.org
Cc: pasic@linux.ibm.com, borntraeger@de.ibm.com,
frankja@linux.ibm.com, mst@redhat.com, cohuck@redhat.com,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] s390: protvirt: virtio: Refuse device without IOMMU
Date: Fri, 12 Jun 2020 11:21:08 +0200 [thread overview]
Message-ID: <f7eb1154-0f52-0f12-129f-2b511f5a4685@linux.ibm.com> (raw)
In-Reply-To: <467d5b58-b70c-1c45-4130-76b6e18c05af@redhat.com>
On 2020-06-11 05:10, Jason Wang wrote:
>
> On 2020/6/10 下午9:11, Pierre Morel wrote:
>> Protected Virtualisation protects the memory of the guest and
>> do not allow a the host to access all of its memory.
>>
>> Let's refuse a VIRTIO device which does not use IOMMU
>> protected access.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
>> drivers/s390/virtio/virtio_ccw.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/s390/virtio/virtio_ccw.c
>> b/drivers/s390/virtio/virtio_ccw.c
>> index 5730572b52cd..06ffbc96587a 100644
>> --- a/drivers/s390/virtio/virtio_ccw.c
>> +++ b/drivers/s390/virtio/virtio_ccw.c
>> @@ -986,6 +986,11 @@ static void virtio_ccw_set_status(struct
>> virtio_device *vdev, u8 status)
>> if (!ccw)
>> return;
>> + /* Protected Virtualisation guest needs IOMMU */
>> + if (is_prot_virt_guest() &&
>> + !__virtio_test_bit(vdev, VIRTIO_F_IOMMU_PLATFORM))
>> + status &= ~VIRTIO_CONFIG_S_FEATURES_OK;
>> +
>> /* Write the status to the host. */
>> vcdev->dma_area->status = status;
>> ccw->cmd_code = CCW_CMD_WRITE_STATUS;
>
>
> I wonder whether we need move it to virtio core instead of ccw.
>
> I think the other memory protection technologies may suffer from this as
> well.
>
> Thanks
>
What would you think of the following, also taking into account Connie's
comment on where the test should be done:
- declare a weak function in virtio.c code, returning that memory
protection is not in use.
- overwrite the function in the arch code
- call this function inside core virtio_finalize_features() and if
required fail if the device don't have VIRTIO_F_IOMMU_PLATFORM.
Alternative could be to test a global variable that the architecture
would overwrite if needed but I find the weak function solution more
flexible.
With a function, we also have the possibility to provide the device as
argument and take actions depending it, this may answer Halil's concern.
Regards,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2020-06-12 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 13:11 [PATCH] s390: protvirt: virtio: Refuse device without IOMMU Pierre Morel
2020-06-10 13:24 ` Cornelia Huck
2020-06-10 14:37 ` Pierre Morel
2020-06-10 14:53 ` Cornelia Huck
2020-06-10 15:27 ` Pierre Morel
2020-06-10 17:24 ` Halil Pasic
2020-06-11 3:10 ` Jason Wang
2020-06-12 9:21 ` Pierre Morel [this message]
2020-06-12 11:38 ` Pierre Morel
2020-06-15 3:01 ` Jason Wang
2020-06-15 10:37 ` Halil Pasic
2020-06-15 11:49 ` Pierre Morel
2020-06-15 11:50 ` Pierre Morel
2020-06-12 13:45 ` Mauricio Tavares
2020-06-12 15:15 ` 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=f7eb1154-0f52-0f12-129f-2b511f5a4685@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.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=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